Scripting doesn't work correctly when "resume with clients" stand-alone server option is used.

[streakeagle]

The Forgotten's early cold war servers ( Vietnam, Korea, and 1970s themes ) uses the "resume with clients" option to conserve resources when no one is actively on a server. However, this has recently (some time in the past few months) started causing a problem with scripts.

MOOSE is used to spawn recovery tankers. The MOOSE scripting can use a single template to generate multiple tankers. The scripts can specify the call sign, tacan, radio frequency, and modex number. When using the "resume with clients" option, the call signs are not assigned correctly after the first client logs in and starts the mission. All the tankers end up with the same call sign or the call sign of the template. As soon as the first client logs out and logs back in again, the scripts take effect and all the tankers appear as scripted. If the mission is run in single player or is run with "resume on load", everything works as it should from the first time anyone logs in.

[streakeagle]

I have done further testing. Even if I don't start any of the scripts until after a client has joined and the mission is already running, "resume with client" breaks some of the scripts. I created separate triggers to start one every 10 seconds. MOOSE is loaded at 10 seconds, MIST at 20 seconds, Skynet at 30 seconds, and finally the mission at 40 seconds. But the problem persists.

[Grimes]

Happen to know if moose spawns the units with the callsign or spawns it first and then calls setCallsign?

[streakeagle]

The way the script is written, it shouldn't appear on the map until all of the values have been configured.

But clearly, it has to create some sort of object first, before it can set the values.

Somehow, the changes aren't being executed, or at least visible to the active game engine, until it has paused when all clients have left and then it starts up again.