Ok I think I may have fixed it. Whew. I need those 3 hours back..
The players table has these three fields
plr_nodeconstructed mediumint(8) unsigned NOT NULL default 0,
plr_nodedestroyed mediumint(8) unsigned NOT NULL default 0,
plr_nodeconstdestroyed mediumint(8) unsigned NOT NULL default 0,
Never really used anywhere in the stats UI, but updated, and they are too high to be accurate (damage maybe?)
Leon Values 16,135,933 16,764,174 11,305,003
Max Value for MediumInt(8) unsigned is: 16,777,215
So very likely the plr_nodedstoryed was failing, and then it fails the rest, to add him to the matches.
Enyo isn't far behind
6,728,524 11,299,559 7,164,702
So I updated the table
plr_nodeconstructed int(10) unsigned NOT NULL default 0,
plr_nodedestroyed int(10) unsigned NOT NULL default 0,
plr_nodeconstdestroyed int(10) unsigned NOT NULL default 0,
Max value now is 4,294,967,295 so hopefully safe for a while
So these values are NOT the nodes values shown in the
https://www.omnipotents.com/utstats/onsrankings.php
Those come from a different table. So I don't know what the above numbers are, I think it might be damage?
Who the fuck knows, and no real comments/data model documentation.
And that save a whole 3 bytes per record (times 825 records) = ~2K whoopie fucking do. Just dumb.
Again its not going to fix the matches that were broken, there's no mechanism to replace the match (and the ~20 data tables) in one fell swoop.
Hopefully tonight when leon plays it will get recorded fine.
Leon feel free to play a solo match and test it
