How to organize game code?

#1 You 'might' be able to add scripts to your level file if you wrap the editor generated code with this

//--- OBJECT WRITE BEGIN ---
//--- OBJECT WRITE END ---

This is how you can add code to your .gui files also (note. some people prefer to make a separate .cs file with the same name as the .gui file for each gui to contain scripts specific to it). This works with mission files in TGE but youll just have to test it for level files with TGB

Usually script files go in game/gamescripts so, within there, you could have a separate script file for each level or even a separate folder of scripts for each level. The organization is really entirely up to you because the engine doesnt care, as long as the script file is executed first you can use its scripts from anywhere.

You can't define classes in script but you could make a scriptobject and give it functions like, for someone used to OOP that might be a good organization for you.

new ScriptObject(level1);
new ScriptObject(level2);
function level1::begin()
{}
function level2::begin()
{}

You can similarly add script functions to other types of torque objects, like a gui (which you would probably put in the .gui file after // object write end)

#2 James:

Thanks for so detailed answer! I'll try that immediately.

#3 James:

I've wrapped the generated code as you said, but my code was gone along with the marks when I've saved a slightly changed level :( Seems like the best idea is to keep the code separately.

#4 Kostya: How about this: Place invisible scene objects in your level and assign them a class / behaviour to load custom, level specific code. Make the objects delete themselves after that. That way, when you run your level, your scripts get loaded automatically.

Another possibility would be to name your level specific scripts like your level file and just load the same filename plus a different extension. You might also want to wrap your level specific code into packages and un-/load them on level transitions.

#5 Oliver:

Thanks for the great idea about behaviors! I have implemented this idea to make level loading more independent. And, by the way, I never realized how great the behaviors are! Just too perfect to be true :)