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

Bedrock client joins in Survival on a Creative server and cannot switch gamemode #2869

Closed
code-monet opened this issue Mar 1, 2022 · 4 comments
Labels
Suspected Server Behavior This probably isn't a Geyser bug but rather something the server is doing.

Comments

@code-monet
Copy link

Describe the bug

Reported previously, eg #2492.

I have a creative mode server running, where if I join from a Java client, it joins in creative mode as expected. However, when connecting from Bedrock, the gamemode is Survival, and cannot be changed from client side settings.

If I delete my (bedrock) .dat file from the world/playerdata dir, restart the server and reconnect, then I join in Creative mode as expected. However, there's still something funny - in the client Settings, server game mode is apparently "survival", but personal game mode is "creative", and still cannot be changed. If I restore the old .dat file and (restart and) reconnect, then the issue is replicated.

I can try replicating, but it will be tedious - would the offending .dat file help (attached)?
offending_player.zip

To Reproduce

Not sure. I have an offending player .dat file, but don't know how to reproduce otherwise.

Expected behaviour

When connecting the Creative server from Bedrock client, client should a) join in the default Creative mode, and b) maybe be able to change personal gamemode from settings?

Screenshots / Videos

No response

Server Version and Plugins

This server is running CraftBukkit version 3443-Spigot-699290c-2c1e499 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT)
[08:26:24] [Server thread/INFO]: Checking version, please wait...
[08:26:24] [Thread-13/INFO]: You are 2 version(s) behind

Also using:
ViaVersion v4.2.1
floodgate v2.1.0-SNAPSHOT

Geyser Dump

https://dump.geysermc.org/jzBQXQY1QudtmbehXMcATMa5kjtoerX6

Geyser Version

2.0.2-SNAPSHOT (git-master-0fd903e)

Minecraft: Bedrock Edition Version

1.18.12

Additional Context

I'm not sure what led to the offending .dat file being created in the first place, so a bit of history:

  1. The server originally existed as a vanilla Java server.
  2. I added GeyserMC stand-alone a couple of days ago from master, and was able to connect from Bedrock in creative.
  3. A few hours ago I added Spigot to the server, and installed GeyserMC as a plugin, along with floodgate (and ViaVersion). Now I see this bug.
@Camotoy
Copy link
Member

Camotoy commented Mar 4, 2022

The player data file shows up as survival for both Java and Bedrock.

@code-monet
Copy link
Author

That player file is for the Bedrock client only - this is from before I linked accounts. It's just not clear why the profile got switched to survival - originally I was playing from Bedrock as creative, as described above.

Anyway, for posterity, to deal with this, there are a couple of options:

  1. Have an admin change the target player's gamemode
  2. Stop server, delete the offending profile, restart (will reset the player, of course)

@ghost
Copy link

ghost commented Mar 11, 2022

That player file is for the Bedrock client only - this is from before I linked accounts. It's just not clear why the profile got switched to survival - originally I was playing from Bedrock as creative, as described above.

Anyway, for posterity, to deal with this, there are a couple of options:

1. Have an admin change the target player's gamemode

2. Stop server, delete the offending profile, restart (will reset the player, of course)

You can create a event listener that sets creative gamemode on join.

@onebeastchris
Copy link
Member

Closing due to this likely being server behavior - if you are still experiencing this, send a new geyser dump.

@onebeastchris onebeastchris closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2023
@onebeastchris onebeastchris added the Suspected Server Behavior This probably isn't a Geyser bug but rather something the server is doing. label Jun 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Suspected Server Behavior This probably isn't a Geyser bug but rather something the server is doing.
Projects
None yet
Development

No branches or pull requests

3 participants