1. The keys defined in the control files are meant to be default control sets. In the future, the player should pick a default control set (Keyboard, Gamepad, etc.) and then customize it.

2. Joystick commands are routed via the same Keyboard interface. Iirc, they have names like Joy*Button* and Joy*Axis*. I do not know whether this works at the moment. I planned to pass partial axis movements to the strength parameter. But the current axis position could be passed in x/y for convenience.

3. For generic vehicle functions (move/interact/stop interact?) it might make sense to have the global PlayerControl function be a forward to the current cursor only. However, then every object that wants to be controllable (say, e.g., a monster) would need to include the Clonk or copy that script. So maybe it would be better to have that in a global function as well (say, global func PlayerControl calls global func ObjectControl). Object-specific functions should go directly to the object, imo, because the Clonk cannot know anything about the nature of the control being passed. If we use Timi's control design, object specific functions would be shortcuts only anyway. Those would be enabled/disabled by the vehicle as the Clonk grabs/ungrabs it.

4. The example wasn't meant to reflect the final design. I don't really care whether digging scripts are put into the shovel or into the Clonk. Anyway, I don't get your question.

5. There's a large list of keys in the engine. I haven't documented them yet. In addition, I planned to add mouse controls: Mouse*Move, Mouse*Button*, Mouse*WheelUp/Down for GUI coordinates; and if that isn't handled MouseLandscape*Move, MouseLandscape*Button*, MouseLandscape*WheelUp/Down. Naturally, anything bound to the Mouse*Move-command (e.g., the cannon aim may want to follow mouse movement) should be enabled on demand only, as it would generate a lot of control traffic.
It is also possible to do use a different control name as a key. For example, you could set the key for Drop to "Down,Throw". This would look up the keys assigned to the down and to the throw control and use them for the Drop control. That way, if the user reconfigures the throw control, he will automatically reconfigure drop as well.

6. I wanted to allow the definition of additional keysets in language packs. I guess we could also have an automatic detection based on the selected keyboard layout.

7. You can define a key such as "Shift+W".

Cool
PS: What when a scenario wants to overload the control? Like Hazard could put "Duck"/"Aim" on CTRL. Is that possible? And how would that be supposed to work for more than one player per keyboard? ("Duck=CTRL" "DuckPlr2=.."?)