Slick Forums

Hi, I'm pretty new to Artemis. I've started programming a game of mine with this new framework + Slick and it's taken quite a while to wrap my head around this Component/System structure. BUT! I am finally making a bit of progress.

And before I continue, I would like to say amazing work on Artemis appel. Keep on developing it!

Now, I have ran into an error that isn't very urgent, but I'm worried it will affect my game in the future.
The error I've found is the 64 limit to the ComponentMapper. When I try to add a certain component to over 64 entities, I'm hit with this error. Is there a way that I can change the ComponentMapper to use something other than a Bag to store... (components(?) or whatever it stores)?

To give a couple of details of my game, I'm planning to have pretty much everything made up out of tiles (maybe like 20x20 px per tile). So, I'm going to have more than 64 tiles on the screen at once, each having very similar components. I foresee a problem with the ComponentMapper here.

Any help/suggestions would be great! And please don't hold back from telling me if I'm doing something wrong here. I moved to Artemis so that I could get a fresh start doing something the correct and organized way. All criticism is appreciated.

I'll probably be posting many more questions here in the near future. Stay tuned!

This limit no longer exists on newer versions of artemis.

Hmm... strange, I'll take a look at it.

Hopefully I'll have a fix over the weekend.

Hopefully this year

Not been able to reproduce. First I misunderstood you, thought you meant 64 different types of components. Please send me code that reproduces this. Else this may be specific to your project.

You're requesting ViewController component from entities that don't have it.

Okay, so I should split the ViewSystem into 2 different systems, 1 dealing with the Entity I would like to center on screen and the other dealing with the InWorld Entities.

You could also use the getSafe-method on ComponentMapper instead of get for the optional components.

And you might want to rewrite your super-call like this
super(Aspect.getAspectForAll(Transform.class).one(InWorld.class, ViewController.class)); // or the other way around

Because the way your code looks like, you want all components to have the Transform-component and then either the InWorld- or the ViewController-component.

Something else: Are you sure you want to use the TagManager to tag your squares? You are calling the TagManager.register-method inside of a loop and the TagManager will only remember the last tagged entity with the same tag. TagManager.unregister would also only be able to remove the last tagged entity.

Awesome! Thank you for the suggestions. I will implement them right when I have the time.

In regards to the TagManager thing, I honestly am not 100% sure what it does or how to use it. I was mostly reading off code from a demo game and copied the (what I thought were) essentials and put my own code around it. But I will do more research and figure it out!

Thanks again.