[BDS-271] Server ignores default-player-permission after world gen Created: 03/Dec/18  Updated: 04/Jan/24  Resolved: 04/Jan/24

Status: Resolved
Project: Bedrock Dedicated Server
Affects Version/s: 1.6.1.0, 1.14.32.1, 1.14.60, 1.17.30
Fix Version/s: None

Type: Bug
Reporter: Jake Herstad Assignee: Unassigned
Resolution: Fixed Votes: 26
Labels: None

Attachments: PNG File DefaultPermissions.png     PNG File image-2018-12-11-16-10-06-734.png     PNG File image-2021-09-24-16-34-56-430.png    
Issue Links:
Duplicate
is duplicated by BDS-269 1.7.1 When default permission level i... Resolved
is duplicated by BDS-3266 server.properties (default-player-per... Resolved
is duplicated by BDS-6178 My default game permission is stuck o... Resolved
is duplicated by BDS-6180 Game permission stuck on visitor Resolved
is duplicated by BDS-15574 Unable to change default Member level... Resolved
Relates
relates to BDS-5191 Server ignores gamemode after world gen Resolved
Confirmation Status: Confirmed
ADO: 319742

 Description   

[1.7.0.13] Server ignores the default-player-permission-level property in the server.properties file and sets players to "member" even when set at "visitor". Please fix this ASAP!

What I expected to happen?
When changing the default player permissions, new players would join with those permissions

What actually happens?
Players join with the default-player-permission-level set at world generation regardless of changes to server.properties afterwards.

Steps to reproduce

  1. Create a new BDS Server with default server.properties file
  2. Start the server, wait for it to finish initial start, and stop the server gracefully
  3. Change the default-player-permission-level value to visitor
  4. Start the BDS instance again
  5. Connect with a Minecraft client and note that your permissions are set to member despite the default level being changed to visitor.


 Comments   
Comment by georgekoba [ 08/Jan/23 ]

Still appears for me in 1.19.51.01

Changing default-player-permission-level in server.permissions after World already generated doesn't seem to work for me.

 

Comment by Derrick Walton [ 10/Jul/22 ]

This appears to be resolved in 1.19.2

Comment by Derrick Walton [ 24/May/22 ]

This issue is still relevant on the most recent update. 1.18.31

Comment by Brian O'Reilly [ 25/Sep/21 ]

I was able to use https://github.com/tryashtar/nbt-studio/ to view the contents of the level.dat on 2 worlds I created, one with `default-player-permission-level=member` and one with `default-player-permission-level=visitor`.

Here's the relevant difference:

Comment by Krissy P [ 22/Aug/20 ]

What is a good data viewer to use since it's a real pain to have to wait for each player to get on the server and then assign the proper permission. And, it must be done with every update since it all clears and starts over.

Comment by Alix Greenawalt [ 22/Apr/20 ]

I am still having this issue in 1.14.60.  My setup is backwards, I originally created my server with default permissions as visitor, but I would like them to be members.  The line in server.properties is still being ignored on existing worlds.

Comment by Otocin [ 04/Mar/20 ]

Hey IonicEcko, let me ask you something.

What has changed in 1.14.32.1?

Comment by IonicEcko [ 04/Mar/20 ]

It looks like the default-player-permission setting within server.properties is written to the world file on first launch and then on subsequent launches is not used (and the original values written to the world are used instead).

As a workaround you can open the world in one of the data viewers around and change the values under "abilities" in the world settings. The easiest way to get the settings that correspond to your desired permissions is to create a blank world with the default permissions you want and compare the two.

Comment by IonicEcko [ 18/Feb/20 ]

Is anyone able to help narrow this one down. I've just built a new BDS instance tonight and cannot replicate. I set the default permissions to visitor and when I connected I was a visitor. Have had this in place on my own server for ages now.

Have attached a screenshot from the test as proof.

Edit: I've just had a thought that its likely the world is generated with a specific default permission and any changes post creation don't work. Will investigate this tomorrow.

For those affected, knowing whether you created your world file before or after the change would be immensely helpful.

Comment by Nik [ 08/Feb/20 ]

Got the same issue here on 1.14.21.1 and need to set the default player permission to visitor. I run a small server for my kids and their friends to play on but yesterday someone joined the server whilst no one was around and messed up some stuff and left messages on a load of signs outside their house. Need to be able to secure this and can’t see another way currently. Please get this fixed as it has been out there for some time now.

Comment by Hugh E [ 13/Dec/18 ]

Using permissions.json doesn't really help here. I'd like to leave my server open to anyone (no whitelist), but not allow them to break anything. So, I need a way to set the "default" permission to visitor, which is what the default-player-permission-level setting is supposed to do. Unfortunately, it doesn't work, so all visitors are granted member permissions, which forces me to restrict access using a whitelist.

 

Comment by Michael litvinov [ 12/Dec/18 ]

This relates to BDS-43 and MCPE-26842

However, you can manually set this.

Make a .txt file named permissions and save is as a .json. Use the format above to manually set ops, visitors, or members. The xuid of a player is shown in the console when they join. Hope this helps.

 Edit: Format must be the exact same. This is the only way that this will work. The server isn't ignoring it, it just doesn't have a place to store it. 

 

 

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