Slick Forums

_________________
/Peter

Thanks, I've always coded around said problem - thinking I'd investigate the cause some other time. I've updated the artemis fork I maintain - since the main artemis repo doesn't appear to be actively maintained anymore - I thought I'd mention it here.

_________________
: bytecode-weaving antiboilerplate lib for artemis. | : bugfixing and performance optimized fork.

I'm also wondering if the call to Entity:changedInWorld() couldn't be done automatically by the add/removeComponent() methods. The only thing that changedInWorld() does is to add a reference to the entity in World.changed. Unless you add/remove huge amounts of components to your entities every frame, I don't think it'll be much of an performance impact.

I'm also working on my own version of Artemis. And I think it would be nice if you could just add/remove components/entities and have it work without having to call extra methods or checking for null pointers.

_________________
/Peter

_________________
: bytecode-weaving antiboilerplate lib for artemis. | : bugfixing and performance optimized fork.

No it's not, I'm afraid. But it's basically your fork with just a couple of tiny changes. Eg. I added a name field to entities in order to quickly find out what kind of entity it is when debugging.

_________________
/Peter