Gates in danger???

[Anyriand]

NGD...

I couldn't play last night for over an hour, I gave up and eventually went to sleep. Today when I wake up Horus is back(yay!) but Alsius has the gates in danger. And why is that?? Why wasn't the map reseted? Why do I have to sit at the gate for 2 hours?? LAME!
This wouldn't happen if the servers didn't go down before we could take our forts back last night.

Even though I'm sure you did not wish for any of this to happen, it did.So I expected a bit more from NGD... seriously...:rale:

[Kyrottimus]

As it happened;

Ignis took trell. After a dedicated but futile attempt to retake the fort from the zerg (and it was a zerg of at least 20) of mostly high-level mentalist mages, they upgraded it to 4 and moved on to Imp.

No more than two minutes went by after Imp was captured than did we get uber lag-spikes 50-80k ms and "-connection problem"

Players were able to log in and out for awhile, with massive delays, lag-warping (rubber-banding), no mobs were visible, no one could click on save altars and no gates were present. One note of contention: The yellow "Gates will be in danger in X minutes" timer was still counting down, even though no one could see anyone else or do anything about it. Chat was about the only part of the game that worked as it should.

After awhile (maybe an hour or two), horus went down completely. When it came back up, both Trell and Imp were still in ignis hands, our gates in danger, and a Syrtis zerg dangerously probing our gate's defenses after they rushed Trell and took it from the Igs. After some back and forth skirmishing with the syrts at our gate, we finally managed to retake trell, then a few minutes later Imp just as our orange gate-vulnerability timer counted out.

Now, I see 2 potential solutions to prevent this sort of thing:
1. Considering we the defending realm had no physical way to retake Trell or Imp (the game was unplayable) during this server "failure", but yet the timer still worked fine, there should be a stop-gap measure added to the code regarding this sort of server error to freeze all timers when this sort of server failure occurs.

2. Upon server "fix" or resetting, either revert all forts to their owners OR (and this is what I suggest), reset the yellow timer to it's last known time before the server went screwy: with a provsion that 5 minutes of live-server go by to allow for SOME game population to re-enter.


Just how I see it, and +1 to Anyriand's observations all around.

[ncvr]

Actually, when the server came back up, there was around 25 minutes left on the timer. We did have time to get our forts back.

[Kyrottimus]

Actually, when the server came back up, there was around 25 minutes left on the timer. We did have time to get our forts back.

I stand corrected; I thought I got back in 5 min after server came up and gate status was orange. I guess I was later than I thought.