[BDS-167] whitelist file not updating with xuid (Bedrock server) Created: 18/Oct/18  Updated: 19/Aug/20  Resolved: 19/Aug/20

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.6.1.0
Fix Version/s: None

Type: Bug
Reporter: John Baumbauer Assignee: Unassigned
Resolution: Incomplete Votes: 1
Labels: None
Environment:

Windows 10


Attachments: PNG File 14234.png     PNG File game photo until crash.png    

 Description   

created a whitelist java fileย  like:

[
{
"ignoresPlayerLimit":false,
"name":"Minecraft user Name"
}
]

Logged into the game and connected to the server game and exited. The xuid is not being added to the file as documented in the How to file.

Is there a way to get the xuid value in game?



 Comments   
Comment by [Mojang] Mega_Spud (Jay Wells) [ 19/Aug/20 ]

Cleaning up old tickets: This ticket had been set to 'Awaiting Response', but has not received a response from the reporter (~3 months+) so is being closed as Incomplete. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines which includes steps to reproduce the problem.

Quick Links:
๐Ÿ““ Issue Guidelines – ๐Ÿ’ฌ Mojang Support – ๐Ÿ“ง Suggestions – ๐Ÿ“– Minecraft Wiki

Comment by IonicEcko [ 10/Feb/20 ]

Hi John,

I believe, if this wasn't working at the time, it now is. I know as recently as a couple of days ago SilentWisperer white-listed using names.

Are you able to confirm if you're still having this issue?

Ionic

Comment by Travis Painter [ 04/Jan/19 ]

This worked just fine for me yesterday on 1.8.ย ย 

Comment by Redisturbed [ 19/Oct/18 ]

You are able to Check the Xuid on your client. Settings>Profile>

on the lower Right side . CIDย  Is the Same as Xuid

[

{ "ignoresPlayerLimit": true, "name": "Redisturbed" }

,

{ "ignoresPlayerLimit": true, "name": "Redisturbed", "xuid": "****************" }

]

The Xuid was taken from the server screen
NO LOG FILE! - [2018-10-18 20:07:40 INFO] Player connected: **************

ย 

Generated at Sat Jan 11 07:13:07 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.