Simon Schmid

UI and Views visualize the current game state. They don't affect the game simulation. They can emit input like button clicks, but the game simulation doesn't know if this input...

1st result of applying this strictly with TDD (Audio): Before: - AudioComponent - PlayAudioSystem - AudioService - no abstraction, dependency to unity After: - No Component / System / IListener...

I also refactored my views now. All testable and very nice :) - removed ViewComponent - Removed all view systems - Views updated themselves using the new Entitas events -...

I really start loving the new events. It feels so clean now :) (We introduced the idea in 2016, but now that we can generate it's even nicer)

Yes :)

Updated diagram to include commands. External input should be checked first and if valid creates commands which affect the simulation. Invalid input could be for example buying an item, but...

I recently built a few smaller games following the "Game Architecture with Entitas" diagram very strictly and I was really happy with the results. After the latest Video Tutorial about...

As another consequence I could get rid of the following contexts: Input, UI, Audio. I only have game and command context left. Feels like everything becomes simpler 👍

ViewService, AudioService and all the other services are all less than 50 lines of code. Things became veeery simple now :)

You can definitely have systems for input, no problem. I'm thinking in a very general and very broad context, one in where you can take the game logic as is...