Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update bedrock-entry.sh to clean up old settings #346

Merged

Conversation

brendonthiede
Copy link
Contributor

Setting white-list to true with no whitelist.json file causes all players to show up as not invited. If this container was ran with a version prior to https://github.com/itzg/docker-minecraft-bedrock-server/pull/337/files using an allow/white list, white-list=true would be set in server.properties in the Docker volume, but PR 337 removed the whitelist.json file.

Setting `white-list` to true with no `whitelist.json` file causes all players to show up as not invited. If this container was ran with a version prior to https://github.com/itzg/docker-minecraft-bedrock-server/pull/337/files using an allow/white list, `white-list=true` would be set in `server.properties` in the Docker volume, but PR 337 removed the `whitelist.json` file.
@brendonthiede
Copy link
Contributor Author

This may be a rare occurrence, but I had previously used WHITE_LIST_USERS in my docker-compose.yml to configure the invited players. The latest bedrock-entry.sh completely removes the deprecated whitelist.json usage in favor of the allowlist.json, but since I'd used the whitelist.json in the past there were traces of that configuration left behind in the data volume. This PR would remove the remaining "whitelist" configuration and only leave the "allowlist".

Copy link
Owner

@itzg itzg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you! I had flipped between iterations of that and left the old bits behind in the process.

@itzg itzg merged commit 2888c55 into itzg:master Aug 16, 2023
@ijbaird
Copy link

ijbaird commented Aug 22, 2023

This appears to break allow lists by adding the extraneous white-list = 'false' to the bottom of server.properties (for me).

@itzg
Copy link
Owner

itzg commented Aug 22, 2023

I thought the bug in Bedrock was only triggered by the presence of the whitelist file. So, @ijbaird you're observing that just the property being present breaks it too?

If that's the case, then the set-property tool will need to be enhanced to support removal of properties and not just updating/adding.

@ijbaird
Copy link

ijbaird commented Aug 22, 2023

I thought the bug in Bedrock was only triggered by the presence of the whitelist file. So, @ijbaird you're observing that just the property being present breaks it too?

If that's the case, then the set-property tool will need to be enhanced to support removal of properties and not just updating/adding.

Yes, I'm seeing that the presence of the property setting is enough to trigger the bug.

@ostat
Copy link

ostat commented Aug 24, 2023

Yes, I'm seeing that the presence of the property setting is enough to trigger the bug.
This seems similar for us.

I followed this issue #336, and was not able to solve the issue.
Our docker container was still using WHITE_LIST_USERS
To get it working again,

In the docker-compose files we have this.

    environment:
      #ALLOW_LIST: "true"
      ALLOW_LIST_USERS: "name1,name2..."

I deleted the allowlist.json, a new one was generated but there are still no xuid values.

In file server.properties around like 37 we had white-list=false and at the end at line 115 we had allow-list=true. I commented out the white-list=false and restarted the container. white-list=false was added to the end of the file but I can now log on to the server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants