Make sure the corresponding number on the Numpad is unbound, and close the Keyboard Shortcuts dialogue.
Press the corresponding number on the Numpad.
Observe that it will trigger the shortcut bound to the regular number.
Expected behaviour: Since Numpad numbers has their own shortcuts, expected behaviour would be that it will not trigger a shortcut bound to a regular number.
Actual Behaviour: As listed above.
The only conclusion would to treat this as a bug since it simply makes no sense to have this logic.
Temporary Workaround: Bind an empty “dummy macro” to the corresponding NumPad key.
I have the same behaviour on both my Catalina computers, so maybe something there. I’ve double checked the System Keyboard preferences, but I can’t see anything odd.
Pressing Key 3 shows only “3”. Pressing 3 on the numpad show “Num 3”.
So it appears in the Keyboard Shortcuts dialogue as everything is normal. But the software will still trigger the shortcut assigned to “normal 3” when pressing Num 3 when the Keyboard Shortcuts dialogue is closed.
EDIT: Also tried switching to a different layout (US International) than my language (Swedish), still same behaviour.
EDIT 2: In case someone else has this issue: The workaround mentioned also requires the actual “dummy macro” to contain something, so I created an empty logical project preset for the dummy to trigger. This blocks the bindings on the Numpad keys.