PaperMC / PaperMC/Paper

entity tracker desync patch causes weird behaviour

Open
#10,879 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

status: needs triage type: bug version: 1.20.6
Dominant language
Java
Stars
12.7k
Forks
3.5k
Avg merge
3d 13h
Merged PRs (30d)
11

Description

Expected behavior

As it did on 1.20.4 and below, cannot replicate on upstream
Screenshot 2024-06-13 at 5 09 25 PM

Observed/Actual behavior
Screenshot 2024-06-13 at 5 00 10 PM

From what I've seen, ItemFrames are rendered a little bit offset from where they should be on client side, but if client targets the hitbox of where it should be, it displays the ItemFrame display name (in the right way)

Steps/models to reproduce

Using the structure api, paste an .nbt structure that holds ItemFrames

Plugin and Datapack List

[17:06:58 INFO]: Bukkit Plugins:
[17:06:58 INFO]: - Basics, BlobBuild, BlobDesign, BlobEconomy, BlobLib, BlobPets, BlobRP, BlobTycoon, DecentHolograms, ItemEdit, LuckPerms, PlaceholderAPI, TAB, Vault, VoidGen, VoxelSniper

Paper version

[17:07:36 INFO]: This server is running Paper version 1.20.6-139-master@79e2cb6 (2024-06-13T14:55:37Z) (Implementing API version 1.20.6-R0.1-SNAPSHOT)
You are running the latest version
Previous version: 1.20.6-115-9d6f2cc (MC: 1.20.6)

Other

Only present since 1.20.5 on Paper and forks, cannot replicate on Spigot

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the Structure API by pasting an NBT structure containing ItemFrames, then compare Paper 1.20.6 behavior with 1.20.4 and below and with Spigot. Done means ItemFrames render at their correct client-side positions and their display names appear correctly when targeting the expected hitbox.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.