ENTITY_TELEPORT packet fired every 1200 ticks (minute)
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12.7k
- Forks
- 3.5k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 11
Description
Expected behavior
Any entity that isnt moving shouldnt fire it, example an armorstand
Observed/Actual behavior
Placing an armorstand, waiting 1 minute (or boosting tickrate) and the packet it sent
https://github.com/PaperMC/Paper/assets/62521371/280817ee-dc7f-4d2b-a5de-329185234a92
Steps/models to reproduce
- Place an ArmorStand or any entity with no ai
- Wait 1 minute or boost tickrate to speed up
- ENTITY_TELEPORT packet is sent
Plugin and Datapack List
[11:20:34 INFO]: There are 2 data pack(s) enabled: [vanilla (built-in)], [file/bukkit (world)]
[11:20:34 INFO]: There are no more data packs available
[11:20:35 INFO]: Server Plugins (2):
[11:20:35 INFO]: Bukkit Plugins:
[11:20:35 INFO]: - PacketListener, ProtocolLib
Paper version
[11:20:58 INFO]: Checking version, please wait...
[11:20:58 INFO]: This server is running Paper version git-Paper-496 (MC: 1.20.4) (Implementing API version 1.20.4-R0.1-SNAPSHOT) (Git: 7ac24a1 on ver/1.20.4)
You are running the latest version
Other
Tested this on a brand new server to ensure it wasnt some other plugin or anything else affecting it
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the entity update path for an ArmorStand or other entity without AI and identify where the ENTITY_TELEPORT packet is emitted. Reproduce the report on Paper 1.20.4 by waiting 1200 ticks or increasing the tick rate; done means stationary entities no longer send the packet while moving entities retain correct updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100