the only way forward from this mess is to firstly figure out why all these stats are being randomly generated. surely it shouldnt be that difficult, RO2 isnt the 1st FPS in history to track stats online.
In beta, before stats were hooked up they were populated with random data. Somewhere between that, and activating the real stat tracking, something screwed up. To me it reads like they never completely removed the random propagation of stats, and THAT's why people sometimes go up in rank, sometimes go down in rank, sometimes they go nowhere in rank.
i think if they were gonna do a stat reset at some point they would have said by now right?
They're going to say very little until they know what the exact problem is. It could be several things.
There may simply be problems with players connecting to the master data server to send their updated data....which means their stored stats are inaccurate in some way. There may be a problem with the master server talking to player clients, which means it has the right stats, but they're not getting reported to us correctly.
It very well may be a problem with the master data server....since they can't seem to reproduce this problem internally. Which would make sense. They have no problems talking to their own master server from their offices. It has problem talking to people through the Steam network and across the world.
And then it could also be some bit of legacy code hanging around that is still getting processed along side our full stats. So, where the normal stat tracking would see no activity in a certain field (weapon, class, ect....) the legacy code might still be filling in any "no change" fields with random data. Including fields that the player just progressed on last match.*
*all the above is wild conjecture
It's not a simple fix, and I really believe it's going to require a reset, because TWI can't concievably go through and clean everyone's profile by hand. They'd have to decided between wiping out ridiculous untrue stats (15,000% accuracy), and leaving other stats that seem reasonable. (200 kills 145 deaths.)
There's no way they're going to do that though, it's a manpower blackhole. And unless they've got a coding prodigy on staff, I don't think they're going to write code to do it for them either. The easiest, most reliable and most equitable solution is to find the problem, guarantee it works over the course of a few days with the community, then declare a stat reset and zero everything out.