I noticed after the 1.20.11.01 BDS update that my allowlist.json files will have random playing deleted from the file. It's only happened a few times now, but last night I was online with 4 other people and this morning I looked at the file and it was only the 5 of us that were on that list when I have 15+ added to the list the night prior and no changes made between then and discovery.
Linked issues
Attachments
Comments 7
There was not. I don't have that console log anymore to copy/paste, but nothing indicated a change within the console.
We have noticed this issue as well. This is happening in addition to general issues with the allowlist not letting people on if the xuid isn't present. Sometimes, however, all of the normal information is in the allowlist and you have to remove and add the person again using console commands for them to be able to join.
This seems to happen after a scheduled restart or after a crash, it seems to be random which of the behaviors it exhibits. We do have 279 entries into the whitelist file. The other server with far fewer entries does not seem to have this issue.
After doing a ton of testing to work out why one of our servers had a completely empty allowlist, it appears if the server shuts down and starts up, any users in the allowlist.json file who do not have an XUID are completely ignored when the allowlist is loaded into the server, and then when any change is made (via the allowlist add/remove command) it removes those users from the allowlist. Prior to this, all we had to do was "allowlist add Name" and then they'd join and it would populate that XUID, and remember them even if they joined or not. I suspect this is also the issue occuring in BDS-18545
Edit: as a Note I actually tested this on a brand new server, not an established one. So the number of users in the allowlist has 0 impact.
I'm seeing exactly the same problem. Here's how to get it.
1. (WHEN ALLOW LIST DOES NOT REMOVE A PLAYER) If you added a person to allowlist and he joined the server before the server was closed or restarted, then allowlist saves the xuid of the player and after that allowlist does not remove this player.
2. (WHEN ALLOWLIST REMOVES A PLAYER)
If you added a player to allowlist and then the server rebooted or was restarted, then allowlist will not save the player's xuid and will remove it when the server interacts with Allowlist
This really interferes with the work of the server, since I have an auto-restart on the server every hour, and if the player whose player I added to the white list did not log in during this hour, then after the reboot, you need to enter the command again and ask him to quickly log in so that he is not deleted
Thank you for your report!
We're tracking this issue in BDS-18655, so this ticket is being resolved and linked as a duplicate.
If you would like to add a vote and any extra information to the main ticket it would be appreciated.
If you haven't already, you might like to make use of the search feature to see if the issue has already been mentioned.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 BDS Wiki – 📖 FAQs
Hi
Were there any information about removing entries in allowlist in server console?
This ticket will automatically reopen when you reply,