Us modders all know we can make our scenes invisible using: But how do we wipe our scripts from the new B24 scenario screen? Is there some sort of InScenario variable we need to know about?

Get an area that doesn't actually exist?

But then it still shows up in scenario. I get what you mean, but it just shows up with no scenes to play with.

No, I want to make it totally unknown to the player that the script even exists.

Have another mission call said invisible mission.

You'll have to elaborate further on that, I don't understand what you mean.

Err wait, nevermind that post.
But what is this for?

Converting unmapped lands to B24. It uses so many scripts the player isn't meant to see and they clutter the scenario window like nobody's business.

Probably the latter. Also Unmapped lands wouldn't be able to switch between scenes if you did that.

Solution A:
Stuff all the scene scripts into different functions. Stuff these functions into one hellishly massive script file that reads the config, and decides which function to run.
I assume that StartActivity can take a third argument of a scene.

Main issue besides ugliness is that besides the metascreen itself, you would have to hardcode areas.

from what I'm getting here...you need to be doing dofile, and you need to pull some startactivity shenanigans.

Well, it looks like Unmapped Lands isn't going to work for B24 then.

Use file IO to write more includes into the definition ini, will probably require a restart, but should work.

What you could do is make all your scenes use the same activity. The StartActivity function for that activity will check SceneMan.Scene.PresetName to determine what the current scene is. From there, it loads the correct UpdateActivity and EndActivity functions by using dofile. It should work just fine.

Ah-ha! Thank you TLB, you are a genius!

Further tinkering is required, it would seem.

You might also want to define a separate function for starting the mission, which you can call in the mission starting code after replacing the functions using dofile. If you don't, then the start function for all the missions won't run.