Skip to content

Release 0.1.2: keep the respawn at the gate when last locations are restored - #5

Merged
mgilardi merged 1 commit into
mainfrom
respawn-0.1.2
Nov 11, 2026
Merged

mgilardi merged 1 commit into
mainfrom
respawn-0.1.2

Conversation

@mgilardi

Copy link
Copy Markdown
Contributor

The cause, found with 0.1.1's trace: Multiverse-Inventories restored a respawned player's last spot, the step into the OneBlock gate. Voidwell now checks the player is within a block of the landing half a second after a OneBlock respawn, and puts them back if not. Pairs with Waystation 0.7.0.

Tested: first-visit, void-death and way-bell sections on Paper 26.2 with Waystation 0.7.0, 21/21.

🤖 Generated with Claude Code

…estored

0.1.1's trace on the Server lead's copy of the real server found the cause:
Multiverse-Inventories' apply-last-location-for-all-teleports put a
respawned player back on their last spot in the station, the step into
the OneBlock gate, and the gate took them to their island. 0.1.1's check
only asked whether they were in OneBlock.

Now the check half a second after a OneBlock respawn needs the player
within a block of the landing; otherwise Voidwell puts them back there and
logs a warning naming that setting. Waystation 0.7.0 adds the second line:
a teleport that leaves a player at a gate can't let it fire on their first
step.

Tested: the first-visit, void-death and way-bell sections on Paper 26.2
with Waystation 0.7.0, 21/21, including the console playing
Multiverse-Inventories right after the respawn. The whole suite wasn't
rerun for this release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mgilardi
mgilardi merged commit cf4a36c into main Nov 11, 2026
2 checks passed
@mgilardi
mgilardi deleted the respawn-0.1.2 branch November 11, 2026 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant