Insta Desynch into "Need to wait because you left a game early"

[Pathingreculiaopenca]

its been 3 times in a row
Im amazed the incredible levels of unprofessionalism and lazyness from the devs

First insta desynch…amm ok i guess, not big deal, wait a brief moment and try again

Close the game and open again
Second time…10 minutes
Ok this is getting annoyng

3rd time in a row
Now 30 minutes of waiting

Its incredible that every single patch, without exception for the last years…Every single patch bring more bugs, more problems and make things worst instead of improving things

Pathing? worse…Now i need to check if my units got stuck because yes, just like one time 22 knights got freeze in a small tree line in the middle of the map because yes. RTS games are about fighting the game itself before your opponent
Villagers? More stupid, taking incredible reroutes, freezes.
TC not Firing?
1 Tile wall hop?
Teleportation?
Random TC gather point?
Ungarrison pathing?

Now i cannot play because devs are more worried pretending to be serious after nerfing kitans and bring more bugs

and dont buy that pathetic excuse that “90 old code”
You can hire 1 or 2 people from those times
Or even apply some community testing right? ive seen how it has been proposed that the collision side of villagers is reduced to stop bumping and freezes, nothing complex from a developer stance
Devs? Naaah, now lets bring more brokens civs under a pay to win fiasco and pretend all the bugs do not extist

Just insuferable unprofesionalism and lazynes

[cmfrydos]

I understand the frustration; quality regressions are real and the current desync bug is highly disruptive. But labeling the developers “lazy” or “un-professional” crosses a line and doesn’t help the issue get fixed any faster.

What’s happening and what you can do right now

• Desync on match start: The issue you’re seeing is being tracked here and is already under active investigation: Out of sync issue as soon as game starts (1v1 ranked arabia).
  Until it’s resolved, the safest workaround is to avoid queuing Arabia.
• Pathfinding problems: The team is gathering reproducible cases. Well-documented replays and videos are invaluable. You can contribute here: Investigations into Pathfinding.

Why it isn’t as “easy” as it looks
Modern RTS path-finding, collision, and flocking algorithms have to be reliable, fast, and scalable; even small changes can break edge-cases for thousands of players. Research in this area is ongoing, so fixes take time, testing, and iteration.

---

Constructive feedback backed by data moves the game forward; personal attacks do not. Let’s channel the frustration into clear bug reports so the devs can prioritize and patch faster.