PlodPlod

Linux - hosted by Nodecraft if that helps.

I've now upgraded the server to 1.20.32.03 and had the same problem again. In particular, when editing allowlist.json manually or using our host's control panel, the new player could not access the game.

Similarly when I used the console command whitelist add [name] the player could not join - BUT if I run allowlist reload afterwards it seems to have the desired effect.

So it seems the bug is still there but reloading the allowlist before they attempt to join seems to act as a workaround.

Yes, I tried with both the server and client on 1.20.15 and the issue persists.

Hi, I have the same issue.

The answer is no, using the command doesn't solve the issue. It had the effect of:

• adding the new player without their XUID (so they still can't connect as the XUID is missing)

• deleting all the other players in the allowlist.json file that don't have an XUID specified

To make matters worse, the public service most people used to obtain XUIDs has now closed so it's now almost impossible to add new players to BDS servers, or for existing players without an XUID in the allowlist.json file to play on the server.

As far as I know the only way to obtain an XUID now is for the player themselves to visit their xbox.com profile and search for "xuid" in the page source.

This seems to be an issue again in 1.20.12

I can confirm this affects 1.19.41; in fact it seems significantly worse since we updated our servers to that version.

It seems to be the thorns enchantment that causes the issue - it doesn't matter what weapon is used to cause the damage. My understanding is the problem is limited to servers, and is present in the full 1.18.30 release.

I think this is a duplicate of MCPE-148531

I didn't have this problem in 1.17.0 / 1.17.1 / 1.17.2 but I do now have it on 1.17.10, on a PC trying to access a private server.

Duplicate of MCPE-71243