Mike Cann

LOL! You mad man! > This works now because this new version is able to check if the removal of a component will cause the entity to be removed from...

> I also support the API we've had so far: Okay cool. I personally have never had the need to do more complex queries such as `any`, `none` etc. But...

Actually, it would be nice if you could also pass an archetype to these functions too. This is what I have been doing: ```ts safeRemoveComponents( from: RegisteredEntity | RegisteredEntity[] |...

Its purely a convenience, so instead of writing something like this: ```ts const myArch = world.archetype("transform", "defaultAttackable", "cellModel"); for(const entity of myArch.entities) world.removeComponent(entity, "defaultAttackable"); ``` or ```ts const myArch =...

> I've been wondering if returning true or false on success/failure of these operations even is needed. In your project, do you ever check them? Theoretically, if I changed all...

Okay no worries, I appreciate you taking the time to consider it. If I still think its warranted once 2.0 comes out I might open another issue or attempt a...

Oh sweet! That looks awesome, nice work :)

Awww okay.. easy come easy go I guess! What would you need to iterate on an entity for anyways?

Im personally not a fan of the rename from "Component" to "Property" but I havent done much with miniplex-react so am unable to comment on the confusion you have mentioned...

> This isn't 100% final, but 2.0 currently exports an id function that you can use to get a stable ID for any entity (just do id(entity) wherever you need...