Sat Nov 08, 2014 4:56 pm
As with all events, they check a condition: --does the player control the Manassas location?, --does the player have =>40 combat elements within this area?, and then do something: --take 10NM from the player, --pat the player on the head for not losing 10NM.
If you capture Manassas before the event checks if you control it the first time, when it checks it the first time, the results will be positive and you immediately win the event. If you take and then lose Manassas before the event fires the first time, the event will not be able to recognize that.
So if you manage to get 40 combat elements into the "Close_to_Richmond" area and then remove them before the event fires the first time, the event will have no idea of that and will continue as if you had never been there.
One could have another event firing much earlier and silently, so that it's not telling the player --hey, you have to lunge at Richmond now--, and if the player manages to fulfill the requirements of the secret even, it turns off the original event and tells the player something like, "newspapers report ecstatically, sudden advances an Richmond may end the war".
This might be seem fair to the very experienced player who knows the real event will fire then-n-then, and that this secret event is waiting for him to trigger it, but it doesn't sound terribly fair to a player who doesn't know all the 'secrets' of the game.