Building Unity 3D game (in Windows) as a single *.EXE file.

Unity 3D (in Windows) creates an *.exe file a data folder with many files and subdirectories.

Which SW tool you would recommend to combine all those files and folders into a single *.EXE file?

-Kaya

 

For me it would be molebox, or you could try free solution like enigma virtual box.

 

I've wrote a tutorial on enigma forum, you can check it out : http://enigmaprotector.com/forum/viewtopic.php?f=20&t=569 , the enigma virtual box is free but you can get more advanced version on their Enigma Protector product, i have tested both the virtual box and protection it works for unity project.

 

It appears that MoleBox is no longer in business. The link provided as of 5/12/2016 is a blog related to online dating. I also could not get the Enigma Virtual Box to work. The help section is terrible and I could not get both the exe file and data folders in the same place.

 

I am also trying to figure out how to do this. I have tried Inno Setup and Enigma Virtual Box. Inno Setup is good for creating a single installer file, but running that file just reproduces the whole set of files created by the Unity build process. Enigma Virtual Box creates a single .exe file, but I can't get that file to run-- it throws an error labeled "cannot load library UnityPlayer.dll".

Any help is appreciated. Thanks!

Edit: tried MoleBox as well. My antivirus flagged a file produced by the MoleBox build as a ransomware trojan. oops. Looks like that's a no-go as well.

 

I can't get that file to run-- it throws an error labeled "cannot load library UnityPlayer.dll".
Did you include the UnityPlayer.dll from Unity build? In order for it to work you should Include data, exe, mono and UnityPlayer.dll

 

May I ask why you want it all in one executable? Unless your game is very simple, won't that blow up the size of the exe?

If you want to be able to just send people a single file, you can use NSIS to create a self-extracting executable, but the end result will still include directories.

 

Makes it harder to decompile - 1 extra step. Also, makes it easier to port around.

 

also the default desktop output folder is quite messy,
multiple exe's (crashhandlers or so), some dll's in the root folder, "strange" bleedingedge-folder.. customers are confused. (installer could help, if user has rights to install apps, but rather would have quick n easy to run single file)

sadly those current all-in-one-packers seems to trigger antivirus too often..

 

That's the downside. Also, it turns a file binary -- which can be good and bad. This means on Steam, they'll have to download THE ENTIRE GAME each patch (instead of just updated files). On the bright side, this also hides diff updates from snoopers.

 

none of your busy busy busines

 

I'm looking for a cheap quick solution as well.

Couldn't the game be a .bat file, then you could just put all the unity stuff in a hidden subfolder. People will steal data and assets no matter what you do, for me it's just a matter of being neat.

A bat or sh file could extract an archive on the first time the game runs, then delete the archive (to save space), then the game could run from the bat or sh file.

Looking into Engima Virtual Box as well, but this is my cheap quick solution for the problem of it not being neater.