Slitherine

All,
I have isolated part of the problem with my campaign editor-there is a single scenario that starts the problems.
I have successfully started a campaign and loaded 5 scenarios into it, restarting the campaign and advancing through the scenarios one by one using the #igotnukes function. I started with two scenarios, tested, added a scenario, tested, in succession until I had campaign that worked with 5 scenarios.

It works fine until I try to add another scenario beyond that -- when a new one is loaded, it jumps ahead of all the others and that is what the campaign opens with -- not the original first scenario. I changed the last scenario to another one, and that one became the new "first" scenario.

When I deleted the last scenario and tried to get back to the last working version of the campaign, it reverted to the Dead Strategic Map.

Is there a setting within that last successfully loaded scenario that I installed that could be causing these wacky errors?

Any ideas why a scenario would cause the one after it to "jump ahead" to first in line when the Campaign starts?

I guess the next step would be to skip loading the 5th scenario and try to see if another one works, but I thought I'd ask and see if anyone had a similar problem previously.

thanks in advance -- any advice as to how to troubleshoot would be appreciated.

conboyxc

Post the campaign here and I'll take a look.

Thanks!
I'll pm it to you when I get it rebuilt to the point before it fails.
I don't want all those half-baked scenarios posted publicly (yet).

thanks again,
conboy

All, for the record just in case somebody else has the same problem:

The reason the campaign start jumped around was because the campaign start box was checked on that scenario (the little box in the upper right corner of each scenario in the settings/branches tab). I inadvertently checked it and that's the scenario it started on.

just that simple.

now we know.

conboy