Issue was already posted and closed for not being possible to reproduce. MCPE-47573
Method 1:
Create an entity with a
minecraft:tick_worldcomponent.Spawn it into the world, then save and exit the map.
Change the entity's identifier (make sure to change all instances).
When loading back into the map, the entity will be gone, but its ticking area will be left behind permanently.
Method 2:
Create an entity with a
minecraft:tick_worldcomponent.Spawn it into the world, then save and exit the map.
Remove the
minecraft:tick_worldcomponent.Kill or despawn the entity. Ticking area is left behind.
Ticking areas are fully functioning and are not listed by /tickingarea.
Related issues
relates to
Attachments
Comments
migrated
migrated
there were definitely some fatal bumps with this component being introduced, but it has gotten a lot better since then. I'm certainly in favor of having this looked further into, though.
EveryCabbage884
Resolving temporarily as Awaiting Response. Could you please attach the add-ons you're using to this ticket?
migrated
I encountered this bug after using a ticking ender pearl pack, somehow when used they were creating ghost ticking areas that couldn't be deleted from in game.
strangely, you CAN see these ticking areas if a normal ticking area is created, with the command /tickingarea list. if there are no ticking areas, /tickingarea list returns nothing.
this could be a big issue for players that have ticking ender pearls and are using stasis chambers for returning to far away places, as they will create ghost ticking areas, I personally had about 10 ghost areas from a communal stasis chamber.
attached a ticking armor stand and a ticking pearls pack for testing
GoldenHelmet
I had tried to reproduce this with the pack from MCPE-48138 using /kill @e, and could not reproduce. However, I do wonder if MCPE-119312 could cause this to occur randomly.
The first set of repro steps in the description here would not be valid b/c they require using a 3rd-party world editor. However, the second set of steps might be reproducible by deactivating a behavior pack.
migrated
Is this still an issue in the latest version?
migrated
I've had this issue on my previous server, which i had to entirely delete because of these tickingareas causing extremely high RAM usage. Not sure if this is still an issue, but if the devs did nothing then it probably is. I'm now scared of making my server non-whitelisted again because of hackers who might spawn agents and create the issue again.
migrated
Cleaning up old tickets: This ticket has not been updated recently (~3 months+) so is being closed as Cannot Reproduce. If you feel this is still a valid issue then please comment, or create a new ticket following the Issue Guidelines.
Quick Links:
📓 Bug Tracker Guidelines – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
migrated
this is still an issue as of the current version i am still unable to remove these tickingareas on my world the remove all from the ticking command doesnt affect ones made by entites. The command needs to be updated to find these ticking areas made by entities so they can be removed as there is no program or software that can remove it for us. I demand you get this fixed and get it fixed now
GoldenHelmet
Could you attach a copy of the affected world with information on where the ticking areas are and how they got there?