PaperMC / PaperMC/Paper

Wrong Z axis respawn range

Open
#13,618 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

status: accepted upstream: vanilla version: 26.1.2
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

When the player respawns, the Z axis value of the respawn position should use full range provided by the respawn_radius game rule.

Observed/Actual behavior

When the respawn_radius game rule is above 50, the Z axis value of the respawn position is always close to the lowest possible value. The closeness and the respawn_radius value seem to be proportional.

Steps/models to reproduce
  1. Set world spawn point with /setworldspawn
  2. Set the respawn radius to be 50 or above with /gamerule respawn_radius <value>
  3. Respawn multiple times
Plugin and Datapack List

Server Plugins (0):
There are 3 data pack(s) enabled: [vanilla (built-in)], [file/bukkit (world)], [paper (built-in)]

Paper version

[22:14:25 INFO]: Checking version, please wait...
[22:14:26 INFO]: This server is running Paper version 1.21.11-111-main@302c47c (2026-02-07T22:59:49Z) (Implementing API version 1.21.11-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.21.11-105-581214a (MC: 1.21.11)

Other

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with /setworldspawn, gamerule respawn_radius, and repeated respawns, then trace the respawn-position handling for the Z axis. Done means the Z coordinate uses the full range provided by respawn_radius, including values above 50.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.