Why is that the ticks on E2 are ending at times a full 1 minute ahead of the end of the actual tick!?

It's OUTRAGEOUS, I've lost my army TWICE now because of it!

Sorry If it comes of like I'm being a whiney ass kid but I mean SERIOUSLY?? First I'm shorted 1k blues from a win and now the server is literally RAPING me and my entire alliances due to this BS!? We've lost literally around 90 squads due to "server issues" and I can bet my left nut that even if by some miracle that someone replies to this without being sarcastic or crass nothing will be done about it.

You DO realize that sometimes servers go early or late, right? Sometimes it's 1 minute before the countdown, sometimes 1 minute after.

I realize that there is a high probability of the tick ending within say 30 seconds before but 1 minute? Battledawn 101 is to launch an attack within the last 2 minutes and for lockdown's in the last minute... how on earth are you supposed check when you're about to be trapped if the server either 1. freezes when you refresh or 2. ends a full minute early?

I fully understand that running this thing must be difficult and hey everyone's human but I'm also sure you can understand my frustration when 3 of my alliance members and myself - twice, have been wiped out due to server issues and nothing to do with gameplay...

Unfortunately I've found it worse than normal. On E3 right now, early ticks are frequently happening, sometimes up to 2 minutes before the countdown ends. I've found, using a clock online and my own home clock, ticks are happen at at the XX:18, XX:38, XX:58 (3 tick world).

However it's not too hard to pick up on, I worked this out in the first couple of ticks in to the era and adapted to it.

The secret is to always watch for if ticks are rolling early. So if you notice ticks are rolling 1 minute early, Launch your EOT attacks with 1:30 to go, etc.

Under normal circumstances I would do. However when the server is fluctuating between 0, 00:20, 00:38 and 1 min it's hard to gauge anything as if you launch at 1:30 but the tick ends on time you've been seen and the chances are the attacks useless. Similarly if the tick ends at 1min or higher then you have 30 seconds to continually refresh to check if you're being spy attacked which more often than not results in it freezing, meaning you have to log out of that world and log back in - by which time the tick has ended and you've been raped.

Edit: Not being a smart ass but shouldn't it be the other way around? Making sure the tick ends on time rather than the player having to channel rain man in an attempt to gauge when the tick shouldn't end but does?

he is fully correct here. i mean. on E2 its REALLY bad. it has no pattern. some ticks wont end for a minute after it should have ended (ex. 8:01 tick still going) or they end a minute before (ex. 7:59 tick is over.) its really a problem here

Agreed E2 has had server issues

Why thank you! So it's not just me being an ass clown.

thats how it feels sometimes , my entire alliance has lost all our armys combined in one bad tick deal in the past , Trying to guage enemy squads bouncing and traveling and timeing everything down to the bottom of tick so they dont catch you trying to set them up .

Andrew gave us resource's when it was obviously the servers fault , not sure if they do this anymore though .