Movement

[A-rms]

Movement issue:
Movement is just the position being updated for each call to tick(dt) (and you can have movement absent any user input).

So, each call to tick(dt), the position (stored as a member variable probably) will have it's value updated based on how much time has elapsed (dt), and it's speed (and/or acceleration depending on how we want it to feel) - see the pin from yesterday...

Note: And, because it's position will change each tick (assuming non-zero speed and/or acceleration), then when render is later called - the player will be rendered in a new position, which will cause us to see the illusion of motion (even though it's really just a lot of still images being drawn very quickly).