1596210bba
A right click with glowstone on a respawn anchor did nothing and a charged anchor never became the respawn point: the block reported the use and the game dropped it. RespawnAnchorBlock is now played out (game/respawn_anchor.rs): useItemOn charges with glowstone (the block change, block.respawn_anchor.charge, the used item and the charge_respawn_anchor criterion), passing to the off hand's glowstone; useWithoutItem sets the respawn point in the Nether (block.minecraft.set_spawn once, respawn_anchor.set_spawn) and elsewhere explodes: the anchor goes, then a power 5 fiery BLOCK explosion with the bad_respawn_point damage source whose centre resists like water when water would flow into it. Dying with an anchor as the respawn point travels to its dimension and respawns at findStandUpPosition (DismountHelper's safe and unsafe passes, facing the anchor with calculateLookAtYaw), using a charge and playing respawn_anchor.deplete; a missing or empty anchor falls back to the world spawn with block.minecraft.spawn.not_valid. The point is saved in the player's respawn compound with its dimension; a bed or /spawnpoint replaces it. Dying in the Nether without one now respawns in the Overworld. Explosions gained what these need: a damage type, a block resistance override, BaseFireBlock.getState for their fire, the explosion radius in the block loot context (survives_explosion and explosion_decay drawing from the table's random sequence) and TntBlock.wasExploded without a game event. tools/test_use_item_on_parity.py now charges, uses and blows up anchors in both dimensions through vanilla's real ServerExplosion on the stand-in level, and respawns at anchors among blocks through ServerPlayer.findRespawnAndUseSpawnBlock. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>