[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

Create a new BDS Server with default server.properties file
Start the server, wait for it to finish initial start, and stop the server gracefully
Change the gamemode value to creative
Start the BDS instance again
Connect with a Minecraft client and note that your gamemode is survival despite the default level being changed to creative.

Environment

Windows 10 client, Ubuntu server

Linked Issues

is duplicated by1

BDS-7685Server loads gamemode property but game is always set to survivalDuplicate

relates to1

BDS-271Server ignores default-player-permission after world genFixed

Comments6

IonicEcko 2020-05-12, 11:54:30 AM

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.

IonicEcko 2020-05-12, 11:54:45 AM

Restricted to staff

MEQS_DUPE

John Baber-Lucero 2020-05-12, 07:01:26 PM

IonicEcko: 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?

John Baber-Lucero 2020-05-12, 09:39:21 PM

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!

IonicEcko 2020-06-23, 05:15:10 AM

edited 2020-06-23, 05:22:04 AM

Have updated the report and confirmed it.

Derrick Walton 2022-07-12, 12:47:36 AM

this appears to have been resolved in 1.19.2

History11

IonicEcko 2020-06-23, 05:11:31 AM

Changed summary:

gamemode=creative in server.properties being ignored Server ignores gamemode after world gen

IonicEcko 2020-06-23, 05:12:47 AM

Changed description:

What I expected to happen?

When changing the gamemode, new players would join with those permissions

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

Steps to reproduce

Create a new BDS Server with default server.properties file

Start the server, wait for it to finish initial start, and stop the server gracefully

Change the default-player-permission-level value to visitor

Start the BDS instance again

Connect with a Minecraft client and note that your permissions are set to member despite the default level being changed to visitor.

Server version: 1.14.60.5 running on Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

Client version: Windows 10 (latest? I don't know how to check minecraft client version)

server.properties has two changes from the default:

gamemode=creative
allow-cheats=true

screen -r $SERVERNAME:
0 NO LOG FILE! - setting up server logging...
0[2020-05-09 04:00:55 INFO] Starting Server
0[2020-05-09 04:00:55 INFO] Version 1.14.60.5
0[2020-05-09 04:00:55 INFO] Session ID df239b72-f63e-483c-8610-0af9f28695e2
0[2020-05-09 04:00:55 INFO] Level Name: Bedrock level
0[2020-05-09 04:00:55 INFO] Game mode: 1 Creative
0[2020-05-09 04:00:55 INFO] Difficulty: 1 EASY
0[2020-05-09 04:00:56 INFO] opening worlds/Bedrock level/db
0[2020-05-09 04:01:05 INFO] IPv4 supported, port: .....
0[2020-05-09 04:01:05 INFO] IPv6 supported, port: .....
0[2020-05-09 04:01:05 INFO] IPv4 supported, port: ....
0[2020-05-09 04:01:05 INFO] IPv6 supported, port: ....
0[2020-05-09 04:01:11 INFO] Server started.
0[2020-05-09 18:19:19 INFO] Player connected: $PLAYERNAME, xuid: ....
0[2020-05-09 18:21:35 INFO] Player disconnected: $PLAYERNAME, xuid: ....

When $PLAYERNAME actually logs in, he sees survival mode. I don't remember if the server was set to the default survival mode the first time he logged in for testing if the mode is somehow sticky per user.

IonicEcko 2020-06-23, 05:12:53 AM

Changed description:

What I expected to happen?

When changing the gamemode, new players would join with those permissions

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

Steps to reproduce

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

Server version: 1.14.60.5 running on Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

Client version: Windows 10 (latest? I don't know how to check minecraft client version)

server.properties has two changes from the default:

gamemode=creative
allow-cheats=true

IonicEcko 2020-06-23, 05:21:23 AM

Changed description:

Server version: 1.14.60.5 running on Ubuntu 20.04 LTS (GNU/Linux 5.4.0-29-generic x86_64)

Client version: Windows 10 (latest? I don't know how to check minecraft client version)

server.properties has two changes from the default:

gamemode=creative
allow-cheats=true

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.