In T189290#2768553, @Amodeu999 wrote:

In T189290#2766614, @auxOlives wrote:

It never ceases to amaze how quickly some jump to blame and complain whenever there's an issue. We all get frustrated by this issue, but being respectful doesn't hurt your position. We also probably lost a chunk of our player base with the unstable hours that follow, do you hear us crying? Rank up, the world doesn't revolve around you.

@WilliamBroown @Amodeu999

This problem has been dragging on for 11 years, every update. You don't say this respectfully, it's just very respectful, because there are no other good words addressed to the developers yet! We repeat the same thing to the developer 1000 times, leave the update alone on the test branch, let people adjust their servers and mods for the update, there are errors, fix them on the test, not on the release a month later, let these updates be not every 4 months but every half a year, but stable. There was no intention of offending in my words, it was rather surprise and praise.

In T189290#2766614, @auxOlives wrote:

It never ceases to amaze how quickly some jump to blame and complain whenever there's an issue. We all get frustrated by this issue, but being respectful doesn't hurt your position. We also probably lost a chunk of our player base with the unstable hours that follow, do you hear us crying? Rank up, the world doesn't revolve around you.

@WilliamBroown @Amodeu999

In T189290#2766126, @Geez wrote:

The fact it took over a week to get any acknowledgementis kinda wild. We discorvered this issue within a hour of the patch. How could this have not been identified before going live with 1.27?

The issue has been worked at since it has been first reported.

Hello, the same problem