If they merged databases without fully understanding the code, causing these various losses, then they sabotaged the game’s future for short-term profits.
The bug report forums are increasingly full of data losses 😶
If they merged databases without fully understanding the code, causing these various losses, then they sabotaged the game’s future for short-term profits.
The bug report forums are increasingly full of data losses 😶
used as flag bits in some random 17 year old code’ etc.
Anyway, something like this would explain the weird way Blizzard have handled this whole issue. It isn’t just
guild banks (I got a 100%
6-tab wipe, *and* a full …🧵
used as flag bits in some random 17 year old code’ etc.
Anyway, something like this would explain the weird way Blizzard have handled this whole issue. It isn’t just
guild banks (I got a 100%
6-tab wipe, *and* a full …🧵
I mention signed int overflow (somewhere in 20 year old code), but they must use ‘flag bits’ a lot throughout the code and database… 🧵
I mention signed int overflow (somewhere in 20 year old code), but they must use ‘flag bits’ a lot throughout the code and database… 🧵
impact any big guilds or streamers).
I wonder whether merging all servers into one is responsible for a lot of the weird data losses throughout the game? …🧵
impact any big guilds or streamers).
I wonder whether merging all servers into one is responsible for a lot of the weird data losses throughout the game? …🧵
1. Rollback. Announce warbands will be delayer. This would need a lot of work, as they had a lot of new code / UI etc. Early access payments lost, new expansion delayed.
2. Sweep under carpet. This option would require …🧵
1. Rollback. Announce warbands will be delayer. This would need a lot of work, as they had a lot of new code / UI etc. Early access payments lost, new expansion delayed.
2. Sweep under carpet. This option would require …🧵
With hypothetical 32-bit UUIDs, they could have calculated that 2.2 billion UUIDs were needed, they ran the scripts, and lost the .2 billion UUIDs due to signed integer overflow …🧵
With hypothetical 32-bit UUIDs, they could have calculated that 2.2 billion UUIDs were needed, they ran the scripts, and lost the .2 billion UUIDs due to signed integer overflow …🧵
Prior to warbands, some server mergers had occurred. But nothing on this scale.
They fired most?all devs in recent years …🧵
Prior to warbands, some server mergers had occurred. But nothing on this scale.
They fired most?all devs in recent years …🧵
WoW was launched when Pentium 4 was good. That was a 32-bit CPU, as was Intel Core ‘1’. Core 2 was 64-bit!
Did they run into …🧵
WoW was launched when Pentium 4 was good. That was a 32-bit CPU, as was Intel Core ‘1’. Core 2 was 64-bit!
Did they run into …🧵
- The data loss happened when, essentially, merging many (all) server-data into one mega-server, for warbands.
- They must use some form of UUID to allow the different parts the …
1/🧵
- The data loss happened when, essentially, merging many (all) server-data into one mega-server, for warbands.
- They must use some form of UUID to allow the different parts the …
1/🧵