Open 56738 opened 1 year ago
I would suspect something similar to https://github.com/PaperMC/Paper/issues/8451 going on. The client crash in that issue is caused by the entities having high velocity when untracked, but root cause might be the same: Ticking stopping before they reach the end of the tracking distance, and as a result they aren't untracked properly. Spigot sets the tracking distance for displays to the relatively high value of 128 by default which probably makes this more likely to occur compared to the low default tracking distances of other entities.
Can confirm that this happens, however unlike in your case I can perfectly reproduce this on the latest version of Spigot as well. Interestingly, following what Malfrador mentioned, if you reduce the tracking distance for displays down from 128 to something much smaller (for example, I tried 32) the entities are untracked properly.
Expected behavior
Entity count in F3 should drop when leaving the view distance of text displays
Observed/Actual behavior
Entity count in F3 stays the same
Steps/models to reproduce
level-type=flat
,spawn-...=false
,generate-structures=false
), also/op
yourselfE: .../1
(you are the only entity)/summon text_display
, F3 should now showE: .../2
/tp 100 -60 0
, F3 still showsE: .../2
/tp 10000 -60 0
, F3 still showsE: .../2
Client render distance should be reasonably high (tested with 12 and 32).
Plugin and Datapack List
None
Paper version
Checking version, please wait... This server is running Paper version git-Paper-101 (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 81619a6) You are running the latest version
Other
/tp
3844-Spigot-b41c46d-c335a55
)