Answer
Create a Stack Key menu, place one action in each slot in the desired order, and assign one hotkey to the Stack Key. Each invocation selects the next enabled slot according to the Stack Key’s advance settings.
Steps
- Add a new PME menu and choose Stack Key as its type.
- Add the first action as a Command or Hotkey item.
- Add the remaining actions in the order they should cycle.
- Disable any slot that should be skipped without deleting it.
- Assign the Stack Key’s hotkey in a keymap scope valid for every action.
- Start with Advance On → Every Press for a direct A → B → C → A cycle.
- Test from a known Blender state and verify every action is valid in that mode and editor.
For example, a Stack Key can cycle three selection commands, three viewport display states, or a short ordered set of tool hotkeys. A slot may call a Blender operator directly or reproduce another hotkey, but direct commands are easier to reason about when an operator is available.
Optional undo behavior
Undo Previous Command asks Blender to undo the prior Stack Key action before executing the next slot. Use it only when every transition is meant to replace an undoable previous operation. It is not a general reset mechanism, and mixed commands may not create compatible undo steps.
Pitfalls
- Stack order follows enabled slots; a disabled slot is skipped.
- All actions share one hotkey scope. A slot that needs Mesh Edit Mode will still fail if the Stack Key is invoked in Object Mode.
- Hotkey items reproduce input and can collide with active tools or modal handlers. Prefer Command items when possible.
- Do not enable Undo Previous Command merely to make a cycle look reversible. Verify Blender’s undo history for the actual operators involved.
Related answers
- How Stack Key Remember Slot and Quick Repeat work
- Make one PME hotkey work in Object Mode and Edit Mode
- Use modifier keys inside one PME item