Suddently Ar leaderboard isn't showing me anymore.
Nesseley opened this issue ยท 26 comments
Hey!
Recently this started to spam in my console.
12.01 22:03:30 [Server] INFO Could not fetch UUID of player 'Inferi'!
12.01 22:03:29 [Server] INFO Could not fetch UUID of player 'Inferi'!
12.01 22:03:29 [Server] INFO Could not fetch UUID of player 'Erikp98'!
12.01 22:03:29 [Server] INFO Could not fetch UUID of player 'Erikp98'!
12.01 22:03:29 [Server] INFO Could not fetch UUID of player 'Kriss005'!
12.01 22:03:29 [Server] INFO Could not fetch UUID of player 'Kriss005'!
This goes on and on with ALOT of players.
And now with no error, I suddently no loner show in /ar leaderboard. I have the most ontime, but now im gone. When i use /ar check it says i have 27days wich is correct, but ar leaderboard doenst show me.
A restart semes to fix the problem, but this is an issue.
/ar leaderboard also takes a LONG time to load, while /ar check and all other commands are normal.
This means the players in the uuids.yml are not up to date or corrupt. I'm not sure why it is fixed after restarting though, that's weird.
Nesseley:
uuid: 959429c2-b123-4c1e-827b-1e1a7c16b731
updateTime: 1452697922422
This is my user and UUID. Correct information.
But keeps spamming "Could not fetch UUID of player" in console..
This sometimes (now always) starts after /ar leaderboard has ben used.
Got this error when i stopped my server right now.
http://pastebin.com/bWWXKxV4
When i start the server it says that it is correct set up.
"[16:21:33] [Craft Scheduler Thread - 4/INFO]: [Autorank] Config files have been correctly setup!"
Hopefully this helps you find out what is wrong. :)
After this restart more people dissapeared from the Leaderboard.
Now I can't find their time using /ar check player
But in the files I can see their name both in Playerdata and UUIDS_X
I got this without any restarts: http://pastebin.com/vSZcQ3JJ
Here you go: http://pastebin.com/zBRh67pR
Also I did use /ar archieve 55m yesterday too see if that was a problem with too many users (removed 600) But it still has the same problems. :)
So, I changed the way Autorank deals with leaderboard updating. It can still take a while (I tested it with 22000 uuids), but it caches the complete leaderboard and refreshes it every 30 minutes. If it detects UUIDs that are in the data.yml but not in the uuid files, it will do nothing until that specific player logs in.
Try downloading dev build #457: http://62.131.38.74:8080/job/Autorank/457/
Tried out the build now! No errors so far!
Will def. wirght back if something pops up.
(This also fixed the " Could not fetch UUID of player 'player'!" spam btw)
I still would like to check players /ar check player when they are offline since last restart thoe, still no fix for this? I don't understand why this happens when the player is in all the right files :/
Could you describe what you see when you perform /ar check? What happens? Could you also send your most recent data.yml and all uuid files in your uuids folder?
/ar check is casesensetive. Thats why they havent been logged before..
https://gyazo.com/526d87d20034d8e6c2597220ca151bb4
Is this something you can fix?
It will be hard finding players thats use caps in their names multipletimes and so on.
Hmm, I think this bugged slipped in yesterday, it did work before. Anyway, good find. I'll fix it for you.
Awesome, I havent found any other bugs with this build so you can maybe try to release it more public! Its a nice fix to the UUID spam that I have seen more people asking about. Il try the one you make now, and tell you back if it works as it should. :)
Havent tried the new build yet!! (Too many players online, and i don't dare to angry them)
Got this error on first build you gave me: http://pastebin.com/sucQfsv5
Do you think this is fixed in new build?
Could you give me your IP? I would like to join to see if all is working well :)
Okay, so obviously it will take a bit longer, I found unexpected behavior of Bukkit, so I'll have to change Autorank to work around this.
Found a thing that got ruined in the lastet update.
Leaderboard now shows everyone in lowercase.
"nesseley" instead of "Nesseley" and so on.
This is due to the fact that players are now stored in lowercase in the data.yml. I might find a way around this, but I'm not sure.