[2.0.65] Cannot pan remote view by keyboard without "Start walking" permission

[emlun]

What happened:
At the start of a new game, I can pan the remote view using the movement (WASD) keys.
After revoking the "Start walking" permission from myself, I can no longer pan the remote view using the movement (WASD) keys.

Expected:
After revoking the "Start walking" permission from myself, I can still pan the remote view using the movement (WASD) keys.

Reproduction steps:

1. Start a new game.
2. Open remote view. Use the movement (WASD) keys to pan the remote view. Observe that this successfully pans the remote view.
3. Close remote view.
4. Open the console and run the /permissions command.
5. Edit the default permissions group: uncheck the "Start walking" permission. Close the permissions settings.
6. Open remote view. Use the movement (WASD) keys to pan the remote view. Observe that nothing happens, but the view can still be panned by click and drag with the mouse.

Additional info:
In Factorio 1.1.91 this works as expected: after revoking the "Start walking" permission, I can still pan the map view using WASD. The issue appears consistently in both Factorio 2.0.7 and 2.0.65, with and without the Space Age mods (Elevated Rails, Quality, Space Age).

I realize this is probably an extremely niche problem to have at all. I'm encountering it only because I'm playing a self-imposed challenge of beating the game without walking at all, so I'm using the permission system to enforce that. Unfortunately that now also makes remote view cumbersome to use. I could work around this by using a mod/scenario/command to set game.player.character_running_speed_modifier=-1, but I'd prefer not using console script commands if possible.

[Rseding91]

Thanks for the report however this is working correctly. Remote view is completely different from the map view in 1.1 and uses the same walking movement logic as the character view to move around.

[emlun]

Thanks for the reply! I realize that is why it works the way it does, my report is rather that this is unexpected for the player. It's also odd if viewing the permissions system from a security perspective (for multiplayer, not just self-imposed challenges): if the purpose of permissions is to limit capabilities, then the "Start walking" permission does nothing to limit remote view movement capabilities because you can still use the mouse to move the view anywhere you want. It is both surprising and not useful that both these actions are governed by the same permission, because they are semantically different even if they're implemented with the same code (and it's clearly not exactly the same code anyway, since remote view isn't affected by Exoskeletons for example).

Anyway, I appreciate that this is still extremely low priority at best. I'd be happy if you reconsidered, but I understand if you won't. I can work around it. Thanks for your time!

[Rseding91]

I can see where you're coming from but maybe this helps explain it more:

The game runs by listening to "input actions" generated by the players keyboard and mouse state - things like "start walking". This system has existed since before version 0.10.0 from over 10 years ago and allows the game to work in multiplayer and with replays. The permissions system then sits on top of that and lets you filter out specific input actions.

In that way the permissions system was not created as an all encompassing granular system but instead a simple set of filters on what the engine was already using to process player inputs. It has always played second fiddle to the input action system that's designed to make the game playable.

[emlun]

Heheh, I see. Thanks for explaining! This would definitely be a "high risk, low reward" thing then, if these things are that foundational.