Please move sg scripts to common folder

#1 Yea this is a nightmare..
i dont even know for sure if its possible


most of your script side stuff is in starter.fps, the part of it is in common but makes hard references to the starter.fps stuff

and i dont know what an .sgo file is but it isnt ascii and i cant change it.. i dont know if there are more hardcoded references in there

is that some kind of precompiled script? why isnt it open source like everything else

i cant name my project folder starter.fps thats just retarded..
and id rather keep everything in common like i had before.. but the editor has no lights available

#2 Hi Jerald,

The Migration Guide contains a list of the changed files, so you can skip over the files you've changed while merging. The changed file list also contains the changed TGE script files, so you can easily compare the files in 'starter.fps' with your mod.

Check out this Script Patch, it removes all hard references in the sgo's. The Lighting Pack script source files were pulled from the pack because they were being distributed with demos and games (against the license).

All Lighting Pack files are already in the common directory (script files, icons, ...). The Lighting Pack datablocks can be moved by tweaking the file 'common\synapseGaming\contentPacks\lightingPack\sgDeployConfig.cs'.

-John

#3 I can verify this works flawlessly, Initially, it kinda threw us, but you can actually merge the common files anywhere you want, and all works as it should

#4 What about the changes to game.cs and init.cs in the starter.fps?

this is in initClient init.cs

//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------
exec("common/synapseGaming/contentPacks/lightingPack/sgDeployClient.cs");
//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------

this is in onServerCreated game.cs
//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------
exec("common/synapseGaming/contentPacks/lightingPack/sgDeployServer.cs");
exec("./sgExamples.cs");
//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------

i made an onCommonServerCreated() in the common folder to run the onServerCreated stuff (minus the examples cause i dont need that)
but im not sure where a good place is to move the client init stuff in the common folder

#5 You can try using 'initBaseClient' and 'initBaseServer' in 'common/main.cs', these might work (though I've never tried using them).

Let me know if those work and I'll look into moving the calls there permanently.

#6 I have a similar issue with the reference to the starter.fps directory in the light editor's .sgo

I don't use starter.fps as my base game folder and it can be rather irritating to have to move the
new light scripts into the correct folder every time I use the light editor.

I know this is pretty trivial but is there some easy way for me to change the save/load paths
for the light editor?

#7 The script file 'common/synapseGaming/contentPacks/lightingPack/sgDeployConfig.cs' contains all of the Lighting Pack path variables (you'll need the script library patch mentioned above) - you can change these to whatever you like, but make sure the variables target an active mod directory (Torque only loads files from the active mods).

#8 I can also verify that this is all possible. We currently do not have a common or a starter.fps directory. We were able to modify all the lighting paths to use just our games directory with no problems. It might take some script hunting but its all possible.

#9 Ok i put
//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------
exec("common/synapseGaming/contentPacks/lightingPack/sgDeployServer.cs");
//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------
in common/server/server.cs right after onServerCreated(); (about line 48)

and i put

//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------
exec("common/synapseGaming/contentPacks/lightingPack/sgDeployClient.cs");
//-----------------------------------------------
// Lighting Pack code block
//-----------------------------------------------

in common/client/canvas.cs right before OpenALInit(); (about line 49)

i tried what you originally suggested, and the client side stuff crashed because there was no GuiModelessDialog stuff yet
also the server stuff did extremely bizzare stuff if you call it where you suggested

#10 Ok, it sounds like that won't work - I was hoping those functions would provide alternative locations for the code.

Basically the problem is that the majority of the init functions defined in common are overridden by starter.fps. In order to avoid this you would need to add code to each mod to call into new methods in common, but that's no different than just using the Lighting Pack code.

Are you using a generic mod template to create all new mods? If the Lighting Pack code was added to the template all of the mods that copy the template would have the code. The common/.../deploy directory was specifically designed to minimize Lighting Pack code in the mod directories, so new code will likely end up in the deploy directory and not in the mods.