MapMovementConfirmRequest

Closes the movement handshake: the walk you were granted is done.

CARRIES NOTHING - SEND IT EMPTY. Four of the dumped builds declare it with no fields at all; the current one pads it with a nine-value enum that NO writer in any dumped build populates. The client constructs this message, sets nothing, and submits it.

Watch that padding rather than dismissing it. If a later build starts populating that enum, this message stops being a bare acknowledgement and becomes a "why did the move end" report - and a script that has hardcoded an empty payload will be sending the wrong thing rather than nothing.

The name comes from one oracle only: Ankama's own type map in an early 3.x build. This message postdates the unobfuscated reference build, so unlike most of this catalogue there is no second source to cross-check the spelling.