Ship Map - Create the necessary ECS systems and components for an entity to know where it wants to go and for it to travel there.

[alexanderson1993]

Entities on the ship map are positioned based on three components: A 2D position component with x,y coordinates, a deckAssignment component (or some other, more descriptive name) which says what deck the entity is on, and a shipAssignment component that says which ship the entity is on.

As an entity moves around the ship, they first decide which node they want to visit and find a path to follow using the #264 pathfinding algorithm. Rarely should an entity decide where it wants to go - maybe once every few seconds, but not every game frame.

However, the entity does update its xy position every frame, moving in the direction of the next node on their destination list. This is what will cause their icon to move across the screen. Their movement should be realistic, based on the kind of entity. For example, an adult human walks around 1.3 meters per second. The scale of the ship is 10 pixels/points per meter, so the person should move 13 points per second, or 0.22 meters per frame. Cargo containers have a similar speed.

When an entity is moving to a node on a different deck, it should hold its position for a period of time - if the entity is taking a turbolift, and that turbolift also moves at 1.3 meters per second, it would take 7 seconds to go between decks. Ideally, the entity would spend half the time on the previous deck and the other half on the next deck.

For now, we won't worry about collisions between entities moving through the ship. We'll assume they're smart enough to not run into each other. 🙂

So, the tasks for this issue:

• Create a component(s) that can be assigned to an entity defining
  • Their ship assignment
  • Their deck assignment
  • Their position on the deck
  • Where they want to go
  • At very least the next node that the entity needs to move to. Optionally it could store a list of all the nodes it needs to traverse to reach its destination.
  • Any information needed to traverse decks.
• Create a system(s) that operate on the above components to move them from where they are to their destination on the ship.

This issue is not concerned with creating logic around making the entity decide where it wants to go - just with how it gets there.

This feature is foundational to how Thorium Nova will work, so it needs to be well designed and thought through and have automated tests. You should make a Pull Request early and ask for feedback on how the code is implemented so you don't need to go back and refactor if and when you get feedback.