Bug: World destruction leads to invalid indexing about arch HOT 4 CLOSED

• If the ids are recycled it will be great to reutilize entities bumping up their version for interoperability/storing reasons
  Do you mean that once a world is being recycled/destroyed entities of this world should increase their version by one to indicate that there was a change?

• It may be worth thinking about worlds reusing: so the destroyed world would not be GC'ed but stored in a recycling queue; it would cover the first need of entities recycling

I agree with this one here. However this should be handled as an additional "feature" or "refactor", ill create a ticket for this later on ^^

b1e88aa hould fix this bug.
World.Id is now being recycled and Worlds are not moved, so the bug should be fixed.

from arch.

I think changing to Dictionary will be the fastest solution

from arch.

Thanks for reporting! :)

Well a dictionary is incredible slow. I would prefer two different solutions, either removing a world just sets it spot in the list to null, but does not remove it completely or the list is replaced by an array and set to null. Destroyed world ids could also end up in a queue for being recycled to fill empty spots.

from arch.

Hey @genaray
I like your proposal.
The only things I would like to emphasize and know your opinion on are:

• If the ids are recycled it will be great to reutilize entities bumping up their version for interoperability/storing reasons
• It may be worth thinking about worlds reusing: so the destroyed world would not be GC'ed but stored in a recycling queue; it would cover the first need of entities recycling

from arch.