Amon | wen
The story goes like this, recently Steam has a relatively unpopular but still "rave reviews" meat pigeon card game "Cobalt Core".
The game was officially released on the 8th of last month, and the combination of innovative cards and spaceship combat gameplay, as well as the perfect integration of mecha and animal character characteristics, has earned it a high praise rate of more than 97%.
At the same time, relying on the cute and three-dimensional Furry character setting, it has attracted many domestic and foreign players, and it has also gained a lot of popularity in various player forums.
So you may be familiar with the Chinese name "Cobalt Blue Core".
The game was developed by Rocket Rat Games, a relatively small indie game studio that had only developed one game before.
However, they are very concerned about their game, and in the month after the game's release, they have made 6 updates, large and small.
The update not only fixes the subtle bugs and combat mechanics triggering issues that have occurred in the game before, but more importantly, it also adjusts the strength balance of the player's reaction during gameplay, such as a certain card is too weak, and a certain character's mechanics are too rigid, etc.
This was supposed to be an excellent "after-sales" worthy of praise from players.
But recently, the game's production team discovered a strange thing. There is a boss in the game that players can defeat, and due to its strong combat power, the "defeat rate" against it in the player's stats has been in a low non-health state.
The production team that discovered this report from the big data system immediately adjusted the values and characteristics of the boss and referenced it in the latest version of the game.
However, the second time they received big data feedback, it showed that the boss's kill rate had not increased significantly, so they nerfed it again in the beta, but it still didn't work.
Changing stats, mechanics, limiting perks, etc., the production team tried all sorts of ways to weaken it, but it didn't seem to be very useful, and in the beta stats, it always sat firmly in the lowest kill rate, and seemed to taunt the players and the production team.
Annoyed, the production team decided to put a version number on their beta version as well, so that they could figure out how many experiments it would take to defeat the seemingly buggy boss.
In fact, due to the frequent changes in the beta version, they didn't update the version number of the game's beta version before.
Unexpectedly, after this test version update, the production team strangely found that many players were still playing an old version that had been eliminated and was no longer supported by Steam.
Steam users should be aware that games on this platform are automatically updated to new versions before launch, so there's no such thing as "forgetting to update" and still syncing data.
For this old version that has not been updated, the boss is still the original strength, and the production team retrieved all the data of the entire player when calling up the player's big data, that is, it was the player data of the old version that polluted the boss's kill rate report.
After learning this outrageous news, some players went to the piracy forum to search for it, only to find that someone had stolen the beta version of the game and developed it into a pirated game, and a large number of players were playing this pirated game that could not be automatically updated, resulting in a large amount of polluted data that was still in the initial version.
It led to this speechless oolong incident of "slashing 5 times in a row, and the boss is indifferent".
This investigation can be regarded as the easiest way to solve the problem that has been a headache for the production team for a long time, and then just filter the player data of the old version.
But the fact that even the beta version has to be pirated, and how the production team found out about it, is still a bit difficult to explain.
-END-