Don't use reload() unless you've made changes to datablocks within the specific file. Doing so initiates a datablock retransmission to the clients (which lags, and anyone in the process of loading will stall).
It has always worked for me... You're just mentally challenged... It's ok Eolk, we still love you.
I have at least one recent example where resending datablocks would actually break the functionality of a script.
The engine's implementation of the network protocol doesn't explicitly support sending static data more than once. It doesn't mean that it doesn't work at all, but it is a hack and it does break things.
Comments
Edit: Apparently, it doesn't like me typing in certain characters. Freaking thing.
For construction use reload(), for other use compile() and exec().
God, that was annoying.
So i just type compile(weapons\blah.cs) ?
compile only prepares the file to be loaded (checks syntax, compiles to bytecode, etc...)
And if you altered datablocks you need to use reload to perpetuate the changes to the clients.
And yes...that is effectively how you use the functions.
It has always worked for me... You're just mentally challenged... It's ok Eolk, we still love you.
The engine's implementation of the network protocol doesn't explicitly support sending static data more than once. It doesn't mean that it doesn't work at all, but it is a hack and it does break things.