More than 2 .gsc?

[Creazeee]

Is it possible to have more than 1 .gsc files in the map? I tried setting one as teleporter.gsc and mp_[mapname].gsc. The teleporter.gsc doesn't work. When I tried switching them, the teleporter it started to work, but the other script didn't. So do I have to put it as one .gsc file? I am putting 10 teleporters and one rotate brushmodel in my map. Could someone give me the script? :S


Nvm, I just didn't add this line to my .gsc file.


maps\mp\teleport::main();


-.-'

[Pedsdude]

I just have all my scripting in one file anyway - less can go wrong.

[ekat]

Try this:
thread maps\mp\teleport1::main();
thread maps\mp\teleport2::main();

[Rezil]

You can use multiple .gsc files. It depends on what you want to do with the code in the .gsc. My general practice is this:

- If you have code that is dependant on your map(say, a mini game that uses entities you placed in Radiant), you call the main function using:

Code: Select all

.iwd_path\.gsc_name::main_thread(optional_parameters);

For example:

Code: Select all

maps\mp\gametypes\_misc::foo();

- If your functions are more general(eg. you create a new HUD element for a player), you can actually include the .gsc before doing anything else:

Code: Select all

#include maps\mp\_utility; /*called before main()*/

This tells the engine to include everything from that .gsc file in the .gsc you called it in. Again, this is my way of doing things, it could be the wrong way but I haven't run into any problems with either method.

I just have all my scripting in one file anyway - less can go wrong.

This will work for most people, and is the best way of doing things if you don't have any complex code.

[Drofder2004]

Code: Select all

#include maps\mp\_utility; /*called before main()*/

This tells the engine to include everything from that .gsc file in the .gsc you called it in. Again, this is my way of doing things, it could be the wrong way but I haven't run into any problems with either method.

This should only be used if you are calling the same functions repetitively.

Usually used for maths functions that dont exist in the engine and functions that create things (such as FX, HUD, etc)

The simplest example is databases.
It is quicker to return an entire array of information from a database in one search than it is to repeatably search for the same information many times.

[IzNoGoD]

Code: Select all

#include maps\mp\_utility; /*called before main()*/

This tells the engine to include everything from that .gsc file in the .gsc you called it in. Again, this is my way of doing things, it could be the wrong way but I haven't run into any problems with either method.

This should only be used if you are calling the same functions repetitively.

Usually used for maths functions that dont exist in the engine and functions that create things (such as FX, HUD, etc)

The simplest example is databases.
It is quicker to return an entire array of information from a database in one search than it is to repeatably search for the same information many times.

Nah, it is optimized@compile time.

btw, OP stated that he solved the problem, even before the first reply...

[Drofder2004]

Nah, it is optimized@compile time.

btw, OP stated that he solved the problem, even before the first reply...

So, there are no benefits or issues with using an #include instead of a direct call 'maps/mp/etc'?
If that is the case, why do we not simply include everything else in every file and never use a direct call again?

Surely the "include" is not just for a small amount of character saving convenience?

Also, jsut because the OP found a solution, does not mean the OP knew about all the possible solutions.