Stat squish confirmed: How will unsynced old content be handled?

[Seraphor]

That is why it surprises me, Wow I did this when the numbers began to not be visible correctly on the screens because they were absurdly high amounts with much larger player content (25 man)

They're simply getting ahead of it before it gets that bad. They still have more expansions planned after Endwalker.

[Nayout]

They're simply getting ahead of it before it gets that bad. They still have more expansions planned after Endwalker.

The problem is that we can still see the numbers without problems, in Wow they made the changes after making a modification in the previous ones to the numbers to display on the screen in a more orderly way.

It is also that I see the belts and it gives me the feeling that either the servers we have are shit or the game code is.

[Rongway]

The problem is that we can still see the numbers without problems, in Wow they made the changes after making a modification in the previous ones to the numbers to display on the screen in a more orderly way.

The bounds of a 32-bit integer, which is still the standard for a plain "int" in languages like C++ are ±2.1 billion. You can specify that you want to use 64-bit integers or even arbitrarily large integers if you import a custom data type that does so, but you would have to go through the entire code base and change every relevant instance of the word "int" to "long long". Worse, you would have to make sure you were only changing the ints that actually needed to be changed, and not the ints that are fine with the smaller value range, because just doing a replace-all to make everything a long long will make many numbers take up twice as much space as they need. Bad, unexpected things happen when you start changing data types in a code base. It would be safer just to change the stat formulas so that the numbers stay within the bounds of the data types already in use. There are other technical considerations, but these are big ones.

Given the upper bound of 2.1 billion and the next patch's biggest mob's maxHP of 440 million, we could already run into a problem against that boss. Unlikely though it be, I can think of one surefire way to cause unexpected behavior in that boss by forcing a calculation past the 2.1 billion limit. I won't discuss the exact situation here because, strictly speaking, explaining how to cause unexpected behavior in the game is against Terms, but the situation exists, and changing the stat scaling now to prevent this in the future is 100% a decision I support as a computer scientist.