Thanks to Polar#0001 for supplying the names:char mappings.

Thanks to Polar#0001 for catching this mistake.

Each movement cycle will now validate the respective amount of tiles, based on movement speed, instead of the full path at once.

Reworks the old event bus system. Goal was to allow parameter-bound events, i.e. `Event<Player>`, which would permit for event actions to have player (or any other specified type) as a context-receiver. This was important as players will now store a collection of pending events through their lifecycle. These events were isolated in a way where "player-bound" events no longer require a player field and instead the "invoke" portion of the event-bus requires the player as input. If we did _not_ take this approach, players would end up with a list of events that contain a reference to themselves, such as the following:

// event needs access to player for the "action" lambda set through plugins
class LogInEvent(val player: Player) : Event

class Player {
    // ...
    public val events = mutableListOf<Event>()
}

fun onLogIn(player: Player) {
    // player now stores an event that has a ref to their own object - bad!
    player.events += LogInEvent(player) 
}

Also adds `MovementTempMask` struct