Skip to content
3 Death Saves
Wiki updated as of 2.3.1 (Sep 2026)

Troubleshooting

Foundry registers keybinding actions only at startup. A macro that had no keybind when the world loaded fires its new combination after a reload. Changing the combination on a macro that already had one applies immediately.

The Keybind field is not in the macro window

Section titled “The Keybind field is not in the macro window”

The field sits directly after the macro Type selector. A module that replaces the macro configuration window without that selector leaves the field out. Disable the replacing module to confirm.

My binding on F5 or a lock key never fires

Section titled “My binding on F5 or a lock key never fires”

Foundry refuses to bind F5, F11, F12, Print Screen, Scroll Lock, Num Lock and Caps Lock. The field shows the combination, but the binding never works. Pick a different key.

Delete or Backspace removes the stored binding. The combination keeps firing the macro until you reload.

If another Macro Keybinds binding owns it, assigning it to a different macro removes the older binding without a prompt, though the old macro can still fire on that combination until you reload. If a core or other-module action owns it instead, Controls Configuration flags the conflict; clear or remap the conflicting action there.

My pending keybind landed on the wrong macro

Section titled “My pending keybind landed on the wrong macro”

A keybind pressed on an unsaved macro is held for thirty seconds and goes to the next macro you create by any means. Macros created by other users do not claim it. The notification names the macro that received it.

I renamed a macro and the binding shows the old name

Section titled “I renamed a macro and the binding shows the old name”

Renames you make are synced to your binding. A rename by another user is not, so rename the macro yourself. Controls Configuration keeps showing the name from startup until you reload.

I deleted a macro but its binding entry is still there

Section titled “I deleted a macro but its binding entry is still there”

The entry does nothing when fired, but it still claims its combination, so other actions on that key may not fire. Open Controls Configuration to clear entries for deleted macros, then reload.

Edits in Controls Configuration do not stick

Section titled “Edits in Controls Configuration do not stick”

Macro Keybinds copies your Controls Configuration edits into its own store each time that window renders, including after you save a binding. Removing every binding on a macro’s action drops that macro’s keybind. Re-record it from the macro’s configuration window. A macro that had no keybind when the world loaded does not appear in Controls Configuration until you reload.

Alt plus a number key still swaps hotbar pages

Section titled “Alt plus a number key still swaps hotbar pages”

Disable Default Hotbar Numbers clears only the hotbar number bindings. Alt plus 1 through 5 still swap hotbar pages. A Macro Keybinds binding on one of those combinations fires instead of the page swap.

My Command or Meta binding shows as Control

Section titled “My Command or Meta binding shows as Control”

Foundry treats Command and Meta as Control. A combination recorded with Command fires with either Command or Control.