Changelog

[1.2.5] - 2026-10-14

Compatibility

• Supports Paper 1.21.11 through 26.3 from a single jar. Requires Java 21 or newer (Paper 26.x servers run on Java 25).
• Saved networks now also record their world key, so they still load if a world's name changes after the 26.x world-folder update.

Added

• Multiple networks per player. Each pearl hit on wool creates a new numbered network instead of replacing your previous one.
• Network limit. The new max-per-player option (default 5) caps how many networks a player can have. When a player goes over the limit, their oldest network is removed.
• Public networks. A network can be shared so every player can use it.
• public-by-default option. When set to true, every network is public and players can't make them private.
• Commands. /wp (or /woolpearl):
  • list: show your networks
  • remove <id|all>: remove networks
  • public <id> / private <id>: share or unshare a network
  • Tab completion for subcommands and network numbers
• woolpearl.public permission to control who can make networks public.
• More anchor protection. A network now shuts off when its anchor wool is burned, blown up or moved by a piston, not only when it is broken by a player.

Changed

• Hitting the anchor of one of your own networks again restarts its timer instead of creating a duplicate.
• A wool block already anchoring another player's network can't be used for a new one.
• The activation message is shorter: Jump or crouch to teleport., plus the expiry time when timed networks are on.
• Saved networks are now stored per network in networks.yml. Files from earlier versions are converted automatically on first start.
• Messages now use Paper's Adventure text components.

Fixed

• Players no longer bounce upward after teleporting from a jump.
• Fall distance is reset after teleporting, so you no longer take fall damage you built up before the teleport.
• Jump detection now reads where you stood when you jumped, so it works even if you're already rising.
• A second pearl thrown immediately after an activation could have its normal teleport cancelled by mistake.
• Config is read once at startup, so changing expire mid-session no longer leaves networks in a mixed state.

Performance

• Network saving now happens in the background every 30 seconds and on shutdown, and only when something has changed. Previously the file was rewritten on every pearl hit.
• Nothing is written to disk at all when timed networks are enabled.
• Anchors in unloaded chunks are no longer loaded just to check them, either at startup or when someone teleports.