www.omnipotents.com/forums

Nope still not fixed. I have to find the error when it goes to update the game stats with leon, some where its tripping up. Seems to be ok, on other players.

In gplayers.sql, change all of the smallint(5) and smallint(6) to mediumint(8)

leon's kills won't fit in a smallint

It looks like matches.sql also needs updated from smallint(5 or 6 ) to mediumint(8)

That should be ok, as its match score, the key is gm_num, so we shouldn't exceed those in a single match/game.

I hope to take a better look at it tomorrow.

Almost a half month. Any help, please.

leon wrote: ↑Wed Jun 01, 2022 6:15 pm ...
Almost a half month. Any help, please.

Can somebody translate leon's query to North American English, I'm not sure what he is asking for here. LOL Just kidding leon, but I don't understand.

The hard fix is the custom development work that pooty is doing.

The easy fix is to delete leon's score.

Correct, there's a bug that's preventing leon's score from getting updated. This means any match that leon players doesn't get the right number of players and it messes everything up. I unfortunately haven't had any time to dig into it further and I was hoping to fix it without deleting Leon's current score, which is a fast and easy fix to just delete leon and let him get re-added albeit at 0 pts.

The magic number might be 65536, or 2^{16}, so maybe the data base isn't capable of the extra exponential.

(Excel is said to be limited to 65536 number of rows. Is this significant?)

Since Leon is 24 kills short of that number I wonder what would happen if, as an experiment, Leon entered a game but got no kills (might as well ask for a pony, too), just built nodes to keep himself busy. Would it record the data normally?

BTW, if you reset Leon's scores to zero his player ranking points will go off the charts since he'll be considered a noob playing against "superior" talent.

That's the suspect. One of the tables, which I changed (gplayers.sql)
had that as hard limit. Smallint(6) in mysql is exactly 65535.

I was hoping it would fix it, but updates still fail, so having to track through the tables and the code to find where.