mojira.dev
BDS-5191

Server ignores gamemode after world gen

What I expected to happen?

When changing the gamemode property, new players would join with that gamemode.

What actually happens?

Players join with the gamemode set at world generation regardless of changes to server.properties afterwards and in contradiction to the gamemode displayed in the console.

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 gamemode value to creative

  4. Start the BDS instance again

  5. Connect with a Minecraft client and note that your gamemode is survival despite the default level being changed to creative.

Linked issues

Comments 10

The server reads certain values once on creation. I believe there is an existing report for this but dont have the time to search right now.

As a workaround you can change that player to creative using console commands.

The server reads certain values once on creation. I believe there is an existing report for this but dont have the time to search right now.

As a workaround you can change that player to creative using console commands.

@unknown: Sounds good. If I fix that user, will all new users be creative? Or if I want a creative server, I should redo the install?

@unknown: Sounds good. If I fix that user, will all new users be creative? Or if I want a creative server, I should redo the install?

I think I understand better now.  When the user first logs in, the client sets a bunch of properties for the user based on the server.properties.  So future users will see "creative" and be okay.  If what I'm saying is not wrong, this ticket should be closed and possibly marked as "solved by" the existing report you refer to.  Thanks!

I think I understand better now.  When the user first logs in, the client sets a bunch of properties for the user based on the server.properties.  So future users will see "creative" and be okay.  If what I'm saying is not wrong, this ticket should be closed and possibly marked as "solved by" the existing report you refer to.  Thanks!

Have updated the report and confirmed it.

Have updated the report and confirmed it.

this appears to have been resolved in 1.19.2

 

this appears to have been resolved in 1.19.2

 

John Baber-Lucero

(Unassigned)

Confirmed

Retrieved