Packet 62

SetPlayerGameTypePacket

The client handles the change of the UI element (the gametype dropdown, although this can be avoided by changing via command or on the server), then the client sends a packet to the server, then the server changes the player's gametype and sends a packet back (UpdatePlayerGameTypePacket) to make sure it matches on the client.

Packet datagramWire order

HeaderID 62varuint

0Player Game Typevarint32 · variable (up to 5 bytes)

Serialized fields

1 top-level fields

0Player Game TypeCompressionEnum-as-ValueGameTypeas varint32
1. 0Undefined
2. 1Survival
3. 2Creative
4. 3Adventure
5. 4Default
6. 5Spectator
7. 6WorldDefault

Changelog

Stable releases

Changes between stable protocol releases.

No stable release changes are recorded for this packet.

All builds

Changes between consecutive stable releases and preview builds.

1.26.60-preview.21

Released: 2026-09-02
Protocol: 2207
Previous build: 1.26.51

Packet

1 entry

Changed 1

SetPlayerGameTypePacket7 changes · ID 62

Changed supporting type GameType: Changed enum value Undefined from 0 to -1.
Changed supporting type GameType: Changed enum value Survival from 1 to 0.
Changed supporting type GameType: Changed enum value Creative from 2 to 1.
Changed supporting type GameType: Changed enum value Adventure from 3 to 2.
Changed supporting type GameType: Changed enum value Default from 4 to 5.
Changed supporting type GameType: Changed enum value Spectator from 5 to 6.
Changed supporting type GameType: Changed enum value WorldDefault from 6 to 0.