First Outpost Battle: A Bugged Mess?

The first outpost battle for the Server 64 war zone has concluded, and to say it was “rocky” would be an understatement. What was expected to be a massive clash between Server 64 and the combined forces of Server 5 and 47 turned into a confusing, bug-riddled event that left many commanders scratching their heads.

The Setup

The stage was set for an epic encounter. We had a new VIP 18 on the field, and the whales were out in force.

“Look at this nice massive server five and server 47. Going to go right at it.”

With power levels reaching 674 million, the anticipation was high. But as soon as the battle started, things went sideways.

The 30-Second Capture?

The most glaring issue was the capture timer. Typically, these battles are a tug-of-war, but reports from the field indicate the capture time was absurdly short.

“Time left to capture 30 seconds. Jeez. What the heck is the point of this? I mean, nobody can even get in there.”

It seems the outpost was captured to 100% almost instantly, leaving no time for a real counter-attack or for the mechanics of the battle to play out. If a capture period is less than five minutes—or in this case, seemingly seconds—it renders the entire event pointless.

Stuck Squads and Useless Cannons

To make matters worse, basic mechanics appeared to be broken:

• Cannons: “The cannons don’t do anything.”
• Movement: Squads were getting stuck inside the outpost structure itself.

“No, we’re stuck. I’m just stuck inside of it. That’s great. So, we got bugs. Way to go on the opening round.”

Conclusion

This was the opening attempt at capturing a war zone outpost from another server, and it fell flat. Between the blink-and-you-miss-it capture time and the movement bugs, there was “nothing at all that anybody could do.”

Commanders are rightfully annoyed. Waking up early for a major event only to watch it break is a tough pill to swallow. Hopefully, the developers will address these issues promptly and provide some compensation for the botched launch.

“Definitely going to be an uprising about this one.”

Stay tuned for updates as we learn more about what went wrong and when we can expect a fix.