VjiaoBlack
commented
5 years ago There are a couple of reasons as to why I'm doing this myself as opposed to using one of the (several) game engines or ECS systems out there.
Those reasons include:
- practice C++ at the level of detail of architecting and writing engines,
- practice debugging and profiling C++ (at the level of detail of architecting and writing engines),
- practice foundations of graphics, AI, physics, etc. systems,
- being able to have control over the complexity of my system
- being able to completely master my own system as I reason about plusses and minuses
- being able to master this system and have "rights" to it to use it as a tool to teach.
- letting other people contribute.
Given all of this, it makes sense that I should reconsider this project as a ECS demo project, and/or figure out a way to refactor out solely the ECS code, and then re-use it with my other projects.
Of course, it wouldn't hurt to (at some point) actually use some external C++ engines (or even Unity) to make some games. But given that I've made these decisions NOT to use many external engines, it would be best to:
- think about whether they're actually good decisions
- if so, write down why they're good decisions
- then write down some documentation
Remove logic from components; put them into systems.