Files
horizon-airdef/crates
Ludovic Marie 6c6b58dd55 Server: the level follows its lone player through Nether and End portals
The server holds one level at a time, as the in-frame game does. While one
player is online (single player on the server thread, or a world with one
player in it), a Nether or End portal swaps the server's level the
in-frame way (switch_level, split out of enter_dimension) and the player
is moved as ServerPlayer.teleport moves it into another level: a Respawn
packet keeping all data, the difficulty, permission level, teleport,
abilities, level info, inventory, effects and the portal travel sound,
then a teleport to the exit once the destination has loaded (the Nether
portal found or built, the End platform, the Overworld's spawn column).
Respawning away from the Overworld takes the level back there first.

What the hub sends follows the level:
- Chunks carry the level's sections only (y 0 to 255 in the Nether and the
  End), without sky light where the dimension has none, and heightmaps
  from the level's floor. Until now every level went out with the
  Overworld's 24 sections, which a client in the Nether or the End reads
  64 blocks off.
- The dimension type follows the level the hub names; the default spawn
  position is the Overworld's.
- A level switch keeps the block change log (an open hub kept none after
  a portal) and the sculk watch list.

Worlds whose player is in the Nether or the End now open on the server
thread too.

The network client maps the End to the End (it drew it as the Overworld)
and shows the death screen on its own PlayerCombatKill, as
ClientPacketListener.handlePlayerCombatKill does, whatever health came
last.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-17 07:54:18 +02:00
..