HomeLink

HomeLink: teleport reliability and safety fixes

Fixed

• Teleports, sounds, particles, messages and request timeouts ran on a background thread, which could crash the server or corrupt entities; everything now runs on the server tick
• Teleport protection used the player's saved Invulnerable flag; logging out (or the server stopping) during it left the player invulnerable for good. Protection is now kept in memory only
• /tpcancel and cancel-on-damage never worked, and several teleports could be stacked: players were never marked as teleporting
• A home file that couldn't be read was treated as "no homes" and was overwritten by the next /sethome; corrupt files could break joining. Unreadable files are left alone, corrupt ones are moved aside as .corrupt-<time>, and saves go through a temp file
• A malformed config crashed the server on start; it now falls back to the defaults without touching the file, and invalid values are corrected in memory with a warning
• /tpto and /tphere placed you half a block off the other player, sometimes inside a wall
• An old request timeout could delete a newer request; accepting or denying a request also cancelled requests that player had sent to others
• Accepting a request while another teleport was pending lost the request
• Teleports to a player who had just died weren't cancelled
• Opening a second singleplayer world registered all events again and broke teleports
• With a delay of 0, /tpback positions and teleport protection were skipped
• The "not initialized" message said "SimpleClumps"

Changed

• /home without a name uses your home called "home", or your only home; otherwise it lists your homes
• Damage, movement and /tpcancel now cancel a pending teleport straight away and tell both players
• Teleport protection can't be chained back to back with instant teleports
• Errors during a teleport are caught and logged instead of reaching the server tick
• Home files are now pretty-printed JSON