BREAKING CHANGES

• Replaced the ppd.ViewRangeBuffer trigger scoreboard with ppd.ViewRangeMultiplier, which allows you to modify your view_range in case it flickers

Changes

• Heavily improved the view_range allocation to make it harder for others to see your displays
• Added support for the minecraft:scale attribute

Changes

• Massively optimized PPD
• Added a ppd.ViewRangeBuffer trigger score for players to compensate for server lag or bad ping

Bugfixes

• Fixed a bug where displays would incorrectly teleport to the overworld

BREAKING CHANGES:

• Changed how the destination pos is defined to scores. This allows for better performance, but PPD now no longer works more than 100k blocks out on each axis. The markers can now be removed from the mobstack.

Changes:

• Changed how the translation is calculated to scores
• Displays that are more than 160 blocks away on an axis no longer compute as much
• Made it so displays no longer check if the player's position moved. This means that changes in the destination pos are applied immediately.
• Added a convention that allows users to specify the order in which data pack libraries load

Bugfixes:

• Fixed a bug where the "UUID collision" error would display on every reload
• Fixed a bug where the "Could not uninstall" message would not work
• Fixed a bug where relogging or changing dimensions would make displays that are too far away visible again

Bugfixes

• Fixed a bug where the datapack would stop working if the root marker got stuck in an unloaded chunk
• Fixed a bug where the display entities would fly relative to the player if the distance to the destination was too big
• Fixed a bug where the datapack would not give an error message if an entity with the UUID [I;128,0,0,128] exists but is not loaded

Bugfixes

• Fixed a bug where sometimes the display entity would not update its translation value
• Updated the how_to function
• Removed some leftover dev comments

Initial release

See 'ppd:how_to' for a tutorial and useful information.