Make non-Lua shortcut state readable.
Posted: Sun Dec 07, 2025 9:15 pm
There exists what feels like a rather arbitrary limitation, that one can't read "non-Lua" shortcuts toggle state. I'm specifically trying to read the toggle-personal-roboport shortcut, so a player can know if it were accidentally toggled.
I can understand when setting is forbidden, perhaps because of whatever logic not expecting a change this way, but READING? It's a true/false value, perhaps "non-readable" (is_shortcut_available) if the controller is one that doesn't use it (e.g. editor), or if it's just not available (pre-unlock).
Code: Select all
Only custom shortcut prototypes with the action type "lua" can be used. For all others there are specific functions/properties.