Putting logic into a mission file

#1 Why not just create a flagbase object, put that into the map instead of the flag object itself.
Durring initialization, check for the CTF variable and if true, create a flag instance and mount to the base.

You could even then use the same flagbase object in different game types, like as a point to spawn a primary target for destruction game types (like a generator, computer core, holy relic, or magic cauldron), or special powerups for deathmatches (extra damage, double points, invisibility, ect...).



Putting the logic in the mission file seems more useful for special triggers, unique objects, and the like.

#2 I see what you're saying. Well, it's not a bad idea--I've kindof gotten resigned to doing it in script, one way or another. But there are other things that I thought would be nice to do in the mission file as well, here and there, so I'd just like to know how to do it.

The main thing I wanted to avoid is having to have a separate mission file for different game types, as that would be a maintenance headache, and your idea certainly helps with that--thanks!

But mostly I just don't grasp the context of the mission file, I guess.

#3 You can put logic into the mission file at the bottom of it, after the line

//--- OBJECT WRITE END ---

so you could put a named simGroup up above in the body of the mission, like

new SimGroup(LogicControlledGroup) {
   };

...

};
//--- OBJECT WRITE END ---

if ($CTF)
{
   %obj = new FlagObject() { blah blah blah };
   LogicControlledGroup.add(%obj);
}

#4 Ohhhhhhhhhhhhhh. You know now that I think about it it was you, Orion, who posted what I'd seen before.

I see now. It's just scripting outside of the actual mission data, but in the same file.

Cool, thanks!