Closed nicolasvac closed 1 year ago
This really just sounds like vanilla behavior, in which if it is the case I'm not sure if it's something we care about handling
Even if it comes out being vanilla behavior, it just seems an unlogic thing to have a global remove() method for the entity that does not assure true removal from all the possible relations and behaviors with the world and other entities.
This is not actually an issue, passengers are correctly removed. Your logic with tasks is causing it to print as 1 because the armorstand hasn't actually been removed yet.
Expected behavior
If i spawn an armor stand and put it as a passenger to a HORSE, and then 5 seconds later I do armorStand.remove() though a sync task, the armor stand despawns correctly and the passengers of that horse should go to zero, as i asked the world to remove that entity.
Observed/Actual behavior
If i spawn an armor stand and put it as a passenger to a HORSE, and then 5 seconds later I do armorStand.remove() though a sync task, the armor stand despawns correctly but the passengers list of that horse stays at 1, and it gets triggered constantly
Steps/models to reproduce
Plugin and Datapack List
Plugins (2): LuckPerms, Survival (custom plugin)
Paper version
Checking version, please wait... This server is running Paper version git-Paper-301 (MC: 1.19.2) (Implementing API version 1.19.2-R0.1-SNAPSHOT) (Git: c40f8d5) You are running the latest version Previous version: git-Paper-300 (MC: 1.19.2)
Other
No response