Inspired by https://www.speedrun.com/aom/runs/y6v45n0m

Right now, the official rules are pretty vague. User.con can be used for some things that I assume we'd all consider cheating, but banning all edits to user.con is probably just annoying to runners. So I think there is some gray area that we should probably explicitly define in the rules.

I think hotkeys can fall into 4 categories:

1. Hotkeys that are available/editable in the settings UI.
2. Hotkeys that can only be hotkeyed through editing files like user.con, but are otherwise actions that you can do through the in game UI (note this isn't the same between EE & TT. e.g. autoqueue! I'm sure at least one run already uses this.)
3. Hotkeys that can only be hotkeyed through user.con, and are not possible through the game UI. examples: "uiSummonWorkersToSelectedUnit" (I believe this is possible in game UI for titan gates & wonders, but can apparently be called on anything?); setting a gather point from your pharoah for animals of Set
4. Hotkeys that perform multiple actions, e.g. select the dig site & call villagers to it in one key press. (spam that at the beginning of the cut scene?!?) Theoretically, you could probably script an entire level into a single key press with infinite APM? This might be non-trivial to define though...there are some common "find" & "train" hotkeys that technically perform multiple actions, but only one succeeds/persists. e.g. many people define a "train age2 myth unit" hotkey that tries to train each myth unit individually, which is technically multiple actions/commands.

I think my gut reaction is that 1, 2, and 3 are fine. I could see both sides on 3 though. I suspect no one wants 4, with some common sense applied for the edge cases mentioned.

I agree! (shocking, given it's my run that needs #3 to be allowed)

Nobody is actively looking to abuse it right now (though I'll admit I spent a few minutes trying to hotkey straight to the excavation site when it was brought up) but there's no reason to not set a precedent and put it in the rules.

Since Aoe3DE has the user.con file I think it's reasonable to expect AoMR will as well. I think that spending some of these last few months before AoMR comes out clarifying rules in prep for the new release, both to have a solid foundation for the new boards, as well to leave these boards in a good state (since I expect runners to move to AoMR at least on the short-term) would be excellent.