roguelike-tutorials-website VS python-tcod-ec

There has been discussion on changes to be made. I'd be interested in hearing about your changes. I'm already aware there are serious issues with the previous Python tutorials.

I have a detailed response to the GitHub issue made about the post.

I did a bit of a double take seeing this on HN. Seeing something I helped to create on here is... a strange feeling, to say the least.

While I'm not completely satisfied with the way this tutorial stands right now, I certainly hope that it has given a few people some ideas and motivation for their own roguelike projects.

Feel free to shoot any issues with the site or tutorial text over to the Github page: https://github.com/TStand90/roguelike-tutorials-website (fair warning: I'm pretty bad at responding to issues, and I sincerely apologize for that)

I've also added a new class called Composite to tcod-ec which allows for multiple components per class and looking up components by a base class. While this is more flexible than ComponentDict I feel that the extra complexity detracts from its usefulness greatly and the new container quickly leads into anti-patterns in my attempts to use it. I struggle to make examples for Composite which couldn't be better expressed in other ways. So far it feels like the restrictions of ComponentDict are a feature rather than a flaw.

For my own project I've been skipping the entity repository and systems and implementing only entity/component frameworks for practice and since I might not need systems most of the time (although there are big downsides for entities and components not being in a repository). My own project can be found here.

I don't have ECS yet, I've tried the current Python libraries but didn't like their typing support, so right now I'm experimenting with basic EC frameworks. I have a decent example right now, and it should be clear how this is better than the Python tutorials implementation.