Releases: joshuaprince/CoordinateOffset
Releases · joshuaprince/CoordinateOffset
v4.0.8 (1.17.1-1.21.4)
- Fix compatibility with GrimAC
- Update packetevents dependency
Shaded with retrooper/packetevents@3d2a872
v4.0.7 (1.17.1-1.21.4)
- Support 1.21.4
Shaded with retrooper/packetevents@d6c81f3
v4.1.0-alpha1 (1.17.1-1.21.3)
This is an experimental release. If you do not need PlaceholderAPI support, I recommend using the latest release instead.
- Add basic PlaceholderAPI support
- Placeholders defined by CoordinateOffset:
%coordinateoffset%
: Resolves to a player's current offset as a comma-separated string, e.g. "1600,-320"%coordinateoffset_x%
: Resolves to the X-component of a player's current offset, e.g. "1600"%coordinateoffset_z%
: Resolves to the Z-component of a player's current offset, e.g. "-320"
- Add PlaceholderOffsetProvider class to set offsets based on an external placeholder
- Supports
placeholderXZ
required key to define the placeholder string (must resolve to a comma-separated
pair of integers which are both divisible by 16) - Supports
worldScaling
key with identical syntax to ConstantOffsetProvider
- Supports
- Placeholders defined by CoordinateOffset:
- Known limitations
- Things WILL break if any player on the server does not have proper placeholder values set when resolving the
placeholderXZ
value. A proper fallback mechanism is necessary for a non-alpha release. - Things WILL break if a PlaceholderOffsetProvider attempts to resolve an offset which is not divisible by 16.
Things will also break if aworldScaling
setting divides the resolved offset such that the result is not
divisible by 16. Use at your own risk and ensure that all offsets provided by a placeholder are divisible by
(16 * 8) for the default worldScaling configuration.
- Things WILL break if any player on the server does not have proper placeholder values set when resolving the
v4.0.6 (1.17.1-1.21.3)
- Fix packet decoding error and kick caused by potions in inventory or in a container
- Update packetevents dependency
v4.0.5 (1.17.1-1.21.3)
- Support 1.21.2 and 1.21.3
v4.0.4 (1.17.1-1.21.1)
- Update packetevents dependency
- Make "version not found" joke in the changelog
v4.0.3 (1.17.1-1.21.1)
- Support 1.21.1
- Fix "Unknown player of Offset lookup" errors related to logging in from another location
v4.0.2 (1.17.1-1.21)
- 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
v4.0.1 (1.17.1-1.21)
- Fix NBT errors causing world to sometimes not load when joining
Notes from v4.0.0
- 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)
v4.0.1-RC1 (1.17.1-1.21)
Preview build to test fix for #13