you have your information wrong, we weren’t aware, and FLYD definitely wasn’t, i was only aware after Dz told in a seperate cht, and then spoke with neutron who said he remembered seeing a similar bug but that the floating one didnt exist, it wasnt until shield had 2 ticks charge left that he remembered more of it after some talking, this bug isn’t something you’d really prep for- unless you plan to lose an army and kick a member
i think saying FLYD is responsible for not going to admins is not cool, if anything the responsibilites fall on me Dz and Neutron- and i did go to alex 8 hours beforehand. Yes now that the bug is ruled illegal the actions are reversed but with the info i was given i couldnt have known 100% it was not allowed, even alexander could appreciate that thought process
This is just to say it wasnt kept as some known secret and done out of malicious intent- if i had found out about the bug earlier i would have asked admins, i actually messaged alex about it within 2 hours of me finding out about it (like 8hrs before FLYD incident)
So I hear the verdict is out. And by the looks of it Flyd will have to take the battle… After pulling back from so many battles which they could have easily won their huge army gonna get farmed. Defensive mindset never wins.
“Never venture, never win!” Sun tzu ~
I wasn’t aware for half of these bugs I found out before I joined AT. When we had all 10 members decided, we all said our share of what we know about this game and everyone gave some tips/tricks and ae wrote em all down. It was cool and fun, never had an alliance such organized as this one in the start, but then the fire nation attacked and red smokes were everywhere lol
I do not remember the last time i got ld and triple damaged.
Oh, wait that never happened. To get ld and triple damaged you need to really really bad to a point where people like you are regarded as good players in comparison to them.
The only reason NA survived this long was luck and people were like. “LOL na who? They won’t last more than 200 ticks”
And guess what happened? They didn’t lol.
Even with the discussion all the points in favor of NA was out of pure desperation not a notable point was made. Even NA knew FLYD was doomed they just played along cause they were desperate.
I recommend you actually go to school instead of wasting your time here, winning a BD era won’t give you a job and money to feed your family when you have too.
I like how everyone is flipping tables still over “BD sucks and is a shit game.” No shit, but the quality of the game itself isn’t why any of us are here. The people are the game
It’s been interesting seeing how the community as a whole has treated the progression of this CE compared to past ones. In a way, I’d say everyone was too kind to each other this era and it lead to the diplomacy spaghetti; we all knew there was a tick-limit from the start.
Remember the first time FLYD got LD+Damaged (PFH even showed them a screenshot of there being spies on that gate which made us all smash our head on a desk); TFI could have suicided there and broken open the GL front at tick ~1.2k. NA “outplayed” everyone as much as everyone else played themselves. A bunch of useless/useful idiots in the grand scheme of the era wanted to feel good about having a bunch of numbers next to their name instead of fighting in a war game. NA didn’t “sit and hide”, the rest of the world just couldn’t find the courage to sacrifice themselves for something bigger.
TFI suiciding 340 squads into 1000 wasn’t the play in my opinion lol @SetG never backs down from a fight issue was an agent got messed up sadly or flyd would have died earlier from a double damage
I mean I could see why you guys choose not to do that at the time. However, in retrospect, it’s a fun thought exercise to play the “what-if” game if that’s how and when you decided to utilize the TFI units. If I’m recalling correctly AM was massed up fairly not far away, WIND was literally right there, and WAR was also nearby (but somehow losing ground to 4 PFH members)
