Question Any way to eliminate unityplayer.dll and unitycrashhandler?

Hi all,
We currently going to start 2D project for mobile and I am learning different possibilities. One way doing it could be using unity, but I tried it and found out it creates UnityPlayer.dll and UnityCrashHandler.exe in game directory. I know - you have to buy professional version to remove unity splash screen, but what about above two? Is there any way not having them?
I do not know about you guys, but if we decide to pay our hard earn money we would not tolerate any Unity ad in game folder - even dll named after unity.

 

Who moved this topic to scripts section? There is difference between building solution and scripting!
You know what? forget it! I already know the answer - YOU CAN NOT. And besides, unity puts whole bunch of unity* named dlls into subfolders. And I am not going to use portable tools just to hide from people we used unity!
Good Day!

 

@babaramanamarama

UnityPlayer.dll

contains the Unity engine itself,

UnityCrashHandler.exe

is used for Cloud Diagnostics.

To be precise: Since Unity 2017.2, "the player executable (read: your game's .exe) has been split into two parts: a signed UnityPlayer.dll that has all the engine code, and a wrapper executable that merely calls into this DLL at startup".

At least the .dll is required - otherwise your game won't run. This also has nothing to do with what type of license (Personal, Plus, Pro) you have.

.

 

Mauri,
Thanks for answer. That makes it clear why we can not use unity.

 

You're welcome

Just a side note: I've edited my reply in the latter part. At least the UnityPlayer.dll file is required. It should be okay to remove the UnityCrashHandler.exe, though I wouldn't recommend it ^^
.

 

You may have your requirements, though it would be interesting what exactly those requirements are and why the UnityEngine.dll is an issue? All your other games files are placed in a subfolder and that whole folder is also required. It actually contains your code as well as all your assets. Are you looking for a single executable solution? Unity itself never supported this, so you would need to pack it yourself. Though most packers usually just unpack it somewhere in order to run it and / or have high false-positive rates on antivirus scans.

If you just want a quick way of sharing a prototype, creating a WebGL build is usually the easiest solution (if applicable for your case).

 

Mobile builds are packed by default, app stores will serve a package (ex. android apk) and install it in the device with no direct indication of install location. Most users will never venture in that location.

So calling this advertisment is a bit far fetched.

Then you can consider other options, any other engine will use their name in their files. It is standard practice afterall.

One can only wonder why you want to hide the fact that Unity was used.

 

I somehow completely missed that he mentioned "mobile". Though if it's really about a mobile build, i'm even more confused since of course a windows executable (*.exe) can only come from a windows build.

As for having the engine names somewhere in the project, what about early engines? In the beginning when the gold source engine was used by the first licensees, the executable file was still named "hl.exe" ^^. Same with idTech where the main dlls are named after the main classes "cgame" which you can find in almost all games made with that engine (RTCW, MOHAA, JK2JO, QL, ...).

It's almost like saying you want to create a windows application but you don't want to have any reference to the kernel32.dll file or any other windows API so nobody knows it's a windows application!? If you don't want to have any trace of Unity in your application, it might not be the best choice to use Unity then ^^.

 

Not wanting any files in your package making reference to the tools you used to make your game is a very bizarre requirement to me.

I don't know about you guys but a dll being named "UnityPlayer.dll" doesn't bother me even if I pay my hard earned money.

Especially considering how reasonably priced the engine is. You don't even have to pay for it until your company is making in excess of 100K a year.

But yeah, if you don't want this... well, you're going to have to look elsewhere. And I uh... I'd like to know when/where you'd find the engine that lets you do otherwise and does so for a reasonable price.

 

So many Unity trolls! I asked simple question and instead answer they are bashing me!!! Why I want to hide fact I might use Unity? Because I would be ashamed to be called Unity developer! And I do not care you call it bizarre or whatever! And what is most important - nobody who posted in this topic (except Mauri) ever bothered to answer question. They came and judged me and said they think having unityplayer.dll seems ok to them etc. I DO NOT CARE what you think and what seems ok to you! I asked question and only one person answered it, the rest are unity trolls humiliating everybody who dares to not share their opinions!
That is my last message in this topic. You can continue without me and assure each other how great unity is.

 

I can't speak for the other people here, but I specifically commented because I had a suspicion your reason for wanting to remove all reference to Unity was because you feel Unity had a negative reputation in the wild.

And...

I guess I was right on the nose.

If you don't want to be a Unity developer... don't use Unity.

I'm not sure how we're the trolls if you were the one who came to this forum to basically tell us that being a Unity developer is an embarrassing thing to be.

It's not bizarre. It's just mean.

Mauri was the first response you got. So your question was immediately answered. Why would we answer the question twice if it was alread answered?

We were just wondering WHY you would want to?

If you're free to ask questions on the forum, why aren't we free to ask questions?

Us offering up our own opinions isn't being a "unity troll" that is "humiliating everybody". How is us asking you "why do you want to remove UnityPlayer.dll" humiliating to you? I think doth protest too much... I think you're projecting your own sense of humiliation brought on by your own opinion of Unity.

If you don't like Unity... don't use it. We're not humiliating you for using it.

Ok...

This reminds of this time I was at a bar with some friends. These 2 guys from a table nearby just sat down at our table where we were having a conversation to attempt to talk to just 2 of us (girls at the table). So I introduced myself.

Spoiler

Me: "Hola, name's lordofduct."

Stranger: "I'm not Spanish."

Me: "Ok..."

Stranger: "Why does everyone around here think I'm Spanish."

Me: "You're in Florida. And from the sound of your accent I'd guess Australia? New Zealand?"

Stranger: "Yeah, I'm Maori, New Zealand. I'm not Spanish. So why does everyone keeping saying hola to me?"

Me: "You're in Florida."

Stranger: "YEAH! So why do you all keep thinking I'm Spanish!?"

Me: "Spanish is a dominant language in Florida... if you went to Germany would you be confused why everyone kept saying 'guten tag' to you?"

What I mean is... you came to a Unity forum. Of course we like Unity... we use it.

If you came to a forum about pickles and said "I don't like pickles". And everyone else said "well... we do".

Would you be surprised?

Us saying we like a thing is not the same as us humiliating you, or telling you you're wrong. We just have different opinions.

No one called you any names or said anything you were saying was necessarily bad/wrong... that is until you got very annoyed at us and told us that Unity is an embarrassment. At which point I did say it was "mean" of you.

Because it was.

...

So yeah. If you're so embarrassed of this engine.

Go use another one.

We're not trying to keep you around.

I don't get why you'd use such an embarrassing engine and then try to hide it. That's like buying a Toyota Yaris, ripping all the emblems off, and then spray painting it to look like a different car. It's not Yaris fans faults (I like Yaris's) that you're embarrassed of it... you just kind of look goofy driving what is clearly a Yaris and trying to pretend it's something else.

Cause I assure you, even if you removed any reference to Unity in the filesystem... most people can recognize a poorly made Unity game. Cause that's the reputation issue with Unity... it's CGI in the 90's and aughts. It's not that CGI was bad back then, it's that people can notice all the bad CGI making them think all CGI is bad. The good one's go unnoticed.

Well with Unity... it has a bad reputation because there's a lot of bad developers using Unity (due to its low bar of entry). Unity can't save a bad developer. But as a result a reputation grows that Unity is for bad developers because so many bad developers have released bad games.

But the thing is... if you suck at making games, you're going to suck Unity or otherwise.

Only way to stop sucking at making games is to practice, and make more games!

 

I'm really confused by this thread. UnityPlayer.dll and UnityCrashHandler.exe are simply not in any mobile build, period. Android and iOS have no idea how to run exe and dll files, so they aren't going to be in there.