Build/Package project by hand?

#1 Just to add an additional question, what are the common causes of a built game to crash?

#2 To do a manual build you can follow these steps (just off the top of my head so I might be missing something)

Copy the following to a new folder

1) .exe
2) the .dlls
3) the common folder
4) the resources folder and the proper resources in it (only the ones you are using in that game)
5) main.cs

Then run the cleandso.bat to remove all the dsos.

you will want to go into main.cs and set the followin gvalues at the begging (before any functions)

$startupProject = "<MAINGAME>";
$defaultGame = "<MAINGAME>";
$defaultMods = "<MODS>";
$levelEditor::LastLevel[$startupProject] = "<CURRENTLEVEL>";
$runWithEditors = false;

Be sure to replace "" with the project folder name, "" with any additional mods (empty if you don't have any additional), and "" with the level you want to load at start.


I beleive that is the majority of what the packaging utility does.

#3 @Matt

I appreciate the help. But now I'm confused. I thought the built game wasn't supposed to have its CS files? What stops a person playing the game from opening up my files and learning how to code? I guess my assumption was to remove the CS files and leave only the DSO files...

#4 @Chris: That's old information, the EULA was changed with T2D was officially released, so you are allowed to distribute your torquescript source.

Gary (-;

#5 Okay, well that's fine for me sending a demo to my musician. But when it comes to release, can I substitute the .cs files with their .cs.dso files instead? I'd prefer not to give away my entire game code to whoever buys it, since it's entirely written in script...

#6

Quote:Okay, well that's fine for me sending a demo to my musician. But when it comes to release, can I substitute the .cs files with their .cs.dso files instead? I'd prefer not to give away my entire game code to whoever buys it, since it's entirely written in script...

Yes.

Gary (-;

#7 Total brain lapse on that one... you need to clear out the .cs files instead of the .dso files... you can edit the dso bat to do so just be careful to do it within your new packages folder only and don't delete the root main.cs. Sorry about that.

#8 @Matt

Not a problem.

@Matt/Gary

Thanks for the help. It worked! :D