Bug with /gamerule spawnRadius x /setworldspawn
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4.4k
- Forks
- 623
- PR merge metrics
- No merged PRs in 30d
Description
Expected behavior
When the /gamerule spawnRadius is 0 and /setworldspawn ~ ~ ~ is set to another coordinate than the normal starter World Spawn the players with no respawnpoint should respawn on the exact Block wich will be set with /setworldspawn ~ ~ ~. But if the /gamerule spawnRadius is 0 players respawn at the first world spawn.
Observed/Actual behavior
If you change the /setworldspawn ~ ~ ~ and do /gamerule spawnRadius 0 you should spawn at the befor set world spawnpoint.
When /gamerule spawnRadius is 0 the game spawns you somewhere else than the set Respawn Point.
When /gamerule spawnRadius is 1 or more the game spawns you at the world spawnpoint wich was changed bevor.
Steps/models to reproduce
- Mark the normal World Spawnpoint.
- Go to another location. Mark and set the World Respawnpoint with /setworldspawn
- Now set the Respawnradius with /gamerule spawnRadius to 0 and move away a bit.
- Do /kill and you should spawn at the Normal World Spawnpoint.
- Now set the Respawnradius with /gamerule spawnRadius to 1 or more.
- Again do /kill and you should now spawn at the World Spawnpoint location set in Step 2.
Plugin and Datapack List
No Plugins or Datapacks used.
Folia version
Folia version 1.21.8-6-ver/1.21.8@612d9bd (2025-09-30T14:11:15Z) (Implementing API version 1.21.8-R0.1-SNAPSHOT)
Other
This issue was reported befor in the 1.20.4 Version of Folia but it is back again.
https://github.com/PaperMC/Folia/issues/222
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the behavior in Folia 1.21.8 using /setworldspawn, /gamerule spawnRadius 0 or 1, and /kill, then compare the two respawn outcomes. No source file or test is named; inspect the world-spawn and respawn handling reached by these commands, and consider the issue done when spawnRadius 0 respawns at the changed world spawn block.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100