Add the ECS system framework

[mattiastofte]

• [x] Make entity and components serializable

[SverreNystad]

@mattiastofte Amazing work! So much goodness here.

There were many good comments, and a small improvement would be to make them into javadocs comments so they show when hovering like this:

I want to create some tests for this module before merging it but again very good work @mattiastofte !

[SverreNystad]

Now as we have merged in the good work of @Artewald with the structure of the project. We can now start work on using our own interfaces towards LibGDX. I noticed that there was use of LibGDX Vector 2 and wondered how use our own systems to use it:

[SverreNystad]

Btw is it also in this module we shall create the internal clock of the game @Artewald @mattiastofte ?

[mattiastofte]

@SverreNystad Thanks. There are still a lot of components and some rendering systems to be implemented, so don't merge this yet anyways:) I don't think the internal clock needs to be mounted here, you just need to pass in delta time when updating the ECS in the game-loop.

[SverreNystad]

Got it. I will make the pull request into a draft till it is ready 😄

[Artewald]

Btw is it also in this module we shall create the internal clock of the game @Artewald @mattiastofte ?

I think we should put the internal clock into game_server, as it's where the logic of the game is played out. We can also have a internal clock in game client, for for example animations?

[Artewald]

Btw is it also in this module we shall create the internal clock of the game @Artewald @mattiastofte ?

I think we should put the internal clock into game_server, as it's where the logic of the game is played out. We can also have a internal clock in game client, for for example animations?

We could also just create a seperate clock package, that both the client and server could use

[SverreNystad]

Btw is it also in this module we shall create the internal clock of the game @Artewald @mattiastofte ?

I think we should put the internal clock into game_server, as it's where the logic of the game is played out. We can also have a internal clock in game client, for for example animations?

We could also just create a seperate clock package, that both the client and server could use

Yes, very good idea @Artewald to keep the implementation in a package and instantiate the clocks on client and server.

[Artewald]

I tried to compile a list of components we need, here's what I found:

• Player: Storing the players UUID
• Money: for money storage on a player and how much gold one should get from enemies when killed
• Card: Cards that the player can hold
• Drawable: Drawing a sprite
• Tower: What damage types it is and how much damage it does
• Target: What target/enemy the tower is attacking
• Position: Position of some entity
• Health: Health for both the village (what we are protecting), enemies and anything else that can take damage
• Enemy: A component describing the enemy

I do not think this is a full list, but they are the components I would like to use to make the GameState in the game server package. It might also not be the best list or solution to the problems we have, so feel free to change it or ask questions

[Artewald]

Could we make the Entity class be serializable so that we can sync UUIDs between game_server and game_client:) This makes our lives much easier when we want to synchronize between them.

[SverreNystad]

Could we make the Entity class be serializable so that we can sync UUIDs between game_server and game_client:) This makes our lives much easier when we want to synchronize between them.

This sounds like an smart idea

[Artewald]

Could we possible add these components as well?

• Store: Has all the cards that the players can buy
• PlacedCard: A placed card on the map