- Support 1.21.2 and 1.21.3
- Update packetevents dependency
- Make "version not found" joke in the changelog
- Support 1.21.1
- Fix "Unknown player of Offset lookup" errors related to logging in from another location
- Fix "Unknown player for Offset lookup" errors printed occasionally when players disconnect
- Fix Random offsets occasionally resetting when changing worlds or dying even when the option is disabled
- Update packetevents dependency
- Fix NBT errors causing world to sometimes not load when joining
- Support 1.21
- Fix movement near bamboo and dripstone when an offset is applied
- NOTE: Servers migrating from v3 should add the
fixCollision
section to their CoordinateOffset config.yml. However, this fix is enabled by default even if these lines are omitted.
- NOTE: Servers migrating from v3 should add the
- Remove separate PacketEvents dependency
- PacketEvents is now shaded into CoordinateOffset, so it is not necessary to install as a separate plugin.
- Several fixes to 1.20.6 bugs present in PacketEvents v2.3.0
- Fix players being kicked while near a horse or wolf that is wearing armor (packetevents#827)
- Fix players respawning instantly after dying (packetevents#816)
- Fix treasure maps with icons kicking players (packetevents#811)
- Fix banners with patterns kicking players (packetevents#772)
- Fix decorated pots in an inventory kicking players (packetevents#768)
- Support 1.20.6 (requires PacketEvents dev build #397+)
- Improve exception handling and debuggability
- Drop CommandAPI dependency; rewrite commands in standard Bukkit API
- Fixes for lodestone compasses
- Fix Creative players seeing lodestone compasses pointing the wrong direction
- Fix lodestone compasses on the ground or in other players' hands pointing the wrong direction
- Fix players being kicked when making sounds near a Warden
- Plugin is now compatible with: (in beta; please report issues)
- ViaVersion
- ViaBackwards
- Model Engine
- Plugin is compatible with Geyser (in alpha; not recommended for production)
- With Geyser installed as a plugin, movement is buggy because Geyser's collision-fixing code processes real coordinates, while its translation layer deals with shifted coordinates.
- If possible, it is currently recommended to use Geyser standalone so that the collision-fixing code is disabled.
- Rewrite packet offsetting logic with PacketEvents library
- Plugin now depends on PacketEvents (v2), and no longer depends on ProtocolLib
- Fix exceptions and improperly offsetted coordinates when a player logs in from another location
- Support 1.20.4 (requires ProtocolLib dev build #676+)
- Remove broken shortened links in config.yml comment
- Backport plugin support to Spigot/Paper 1.17.1, 1.18.2, and 1.19 through 1.19.3 (plugin now supports all versions from 1.17.1 through 1.20.2)
- Mark
resetOnDistantTeleport
as unsafe and require opt-in (more details) - Add
worldScaling
option to ConstantOffsetProvider - Fix "facing" packets (e.g.
/tp ~ ~ ~ facing 0 0 0
) not being properly offsetted, causing the player to face the wrong direction - Fix player getting kicked when their vehicle moves too quickly
- Support 1.20.2 (requires ProtocolLib dev build #669)
- Rewrite majority of packet translation logic to support multiple protocol versions
- Add bStats anonymous plugin metrics
- Fix excessive world border packets while border is obfuscated
- Fix login error on BungeeCord/Waterfall (#5)
- Fix glitchy behavior when multiple players are logged into the server with offsets (#4)
- Entities becoming invisible
- Multi-blocks (beds, doors) failing to place properly
- Beds appearing to teleport players into the void
- Improve
resetOnDistantTeleport
in providers to use world view distance to determine when a teleport is "distant"- Previously: Teleports over a distance of 2050+ blocks could trigger a re-roll (random providers) or re-center (zero-at-location providers)
- Now: Teleports over a distance of
(2 * (world view distance + 1 chunk))
or further can trigger resets - On Paper servers, relative teleports (e.g.
/tp ~500 ~ ~500
) will no longer trigger a reset
- Improve API exposure for dependent plugins
- Support ProtocolLib 5.1.0
- Support 1.19.4
- Make world borders visible while an offset is applied, improve border handling and obfuscation
- Expose and document API for other plugins to get and set offsets
Initial release of CoordinateOffset.
Changelog from upstream:
- Rewrite all logic for determining offsets
- Expose offset configuration per player/world/permission through "providers"
- Add
/offset
command (with permission) to query players' current offsets - Fix death compasses not pointing to their correct location