Slick Forums

Two worthwhile features added:

1. Now possible to use @Mapper annotation to automagically inject a ComponentMapper into your system at runtime.



2. Now possible to exclude entities with an aspect.

Means all entities with Position.class and Sprite.class and NOT Physics.class will be processed by this system. You can add multiple exclusion components as well.

Whoa, now this is cool

This is so great! I like where you are taking the framework style-wise. I just participated in Ludum Dare #24 using artemis and it hasn't let me down once again. I wouldn't give that source-code as an good example to anyone though. 48h makes you do a lot of ugly stuff to finish in time
Thanks for making this framework even more awesome

I like new @Mapper annotation!

_________________
Blog | Last game Gravity Duck tribute | In progress Gravity Duck tribute

I'd love to have an OR function. That would be perfect. The exclude I've never used, but I've implemented a simple version of the OR function, but doing this with aspects would mean a better design.

I'll look into it.

I don't mean something like parenthesis for now, like ((A ^ B) - D) + C, this could turn into a complex and unused feature. I can't think in systems that can do things like ((A^B)-C)+((A^B)-D). I'd start with no parenthesis at all, and then you rethink. Doing things like Aspect.aspectForAll(A,B).excluding(C) and Aspect.aspectForOneOfThem(A,B,C) seems to be a good starting point.

You can also do:

world.setSystem(new ABCSystem(Aspect.getAspectFor(A.class)));
world.setSystem(new ABCSystem(Aspect.getAspectFor(B.class)));
world.setSystem(new ABCSystem(Aspect.getAspectFor(C.class)));

Creating three instances of the same system should work for this case.

I didn't knew I could do that, seems like hack ^^

Well, it's possible... only problem is you cannot retrieve the system from the world, it will return you the last inserted system:


Better would be to create an abstract ABCSystem which has all the logic, and extend it with ASystem, BSystem and CSystem each defining their own aspect, and they would really only have a constructor. That way you can retrieve from world each system.

But frankly, Aspect.aspectForOneOfThem(A,B,C), seems like a hack too ^^

If it's officially supported by the framework, I don't see as hack ^^