They cannot. If I add someone fresh they get the "not invited to play" message. However, when I add their XUID manually, they are able to connect without issue. Seems like whatever gathers the XUID information upon the users first connect, isn't and preventing the user from joining with that message.
Just had it happen again. Let one without an XUID within the allowlist.json stay since they were off for a few weeks and before this update it would have allowed them on and then added their XUID into that file, but it said they weren't invited and never added their XUID. I then pulled there XUID # from a website, added it to the allowlist.json into the file and it allows them to connect without issue.
Guess for replication, add a user through the console and have they try to connect, it will tell them that they are not invited, even know Xbox Gamertag is correctly put and cased as it needed for be.
For example, my Xbox gamertag is "IRL Dave" so I'll so whitelist add "IRL Dave" (since I have a space in my name I need to use quotes), it will add the line
{"ignoresPlayerLimit":false,"name":"IRL Dave"}
, to the allowlist.json. When I try to connect, I'm not invited. Manually update the allowlist.json to include my XUID to appear like this:
, on that line, and I'm able to connect without issue.
So somewhere in that Online mode player authentication, where it would usually add the XUID, it is not, and in turn it is blocking their connection by saying they are not invite to play, until their XUID is manually put it.
That doesn't display the format right on this post, but just one entry per line and so on and MUST include the XUID if not known, I've had to look them up.
BDS-18536
They cannot. If I add someone fresh they get the "not invited to play" message. However, when I add their XUID manually, they are able to connect without issue. Seems like whatever gathers the XUID information upon the users first connect, isn't and preventing the user from joining with that message.
There was not. I don't have that console log anymore to copy/paste, but nothing indicated a change within the console.
Just had it happen again. Let one without an XUID within the allowlist.json stay since they were off for a few weeks and before this update it would have allowed them on and then added their XUID into that file, but it said they weren't invited and never added their XUID. I then pulled there XUID # from a website, added it to the allowlist.json into the file and it allows them to connect without issue.
Guess for replication, add a user through the console and have they try to connect, it will tell them that they are not invited, even know Xbox Gamertag is correctly put and cased as it needed for be.
For example, my Xbox gamertag is "IRL Dave" so I'll so whitelist add "IRL Dave" (since I have a space in my name I need to use quotes), it will add the line
{"ignoresPlayerLimit":false,"name":"IRL Dave"}, to the allowlist.json. When I try to connect, I'm not invited. Manually update the allowlist.json to include my XUID to appear like this:
{"ignoresPlayerLimit":false,"name":"IRL Dave","xuid":"2535458138542642"}, on that line, and I'm able to connect without issue.
So somewhere in that Online mode player authentication, where it would usually add the XUID, it is not, and in turn it is blocking their connection by saying they are not invite to play, until their XUID is manually put it.
Are you having the same issue as I?
BDS-18536Are you hosting on Nodecraft by chance?
This only way I and and another server I was talking with got our allowlist.json working has is it was flattened and one entry per line:
[ {"ignoresPlayerLimit":falce,"name":"Player 1","xuid":"###############"}, {"ignoresPlayerLimit":false,"name":"Player 2","xuid":"###############"}, {"ignoresPlayerLimit":false,"name":"Player 3","xuid":"###############"} ]That doesn't display the format right on this post, but just one entry per line and so on and MUST include the XUID if not known, I've had to look them up.