Commands & Admin

Always-Registered Commands

Command	Who	What it does
`/slotcreator`	Admins	Machine editor — place, move, stats, jackpot, bankroll
`/slotperms`	Anyone	Diagnose permissions and print the `server.cfg` line to add
`/slotsleaderboard`	Anyone	Public ranking (command name is configurable)
`/slotfix`	Anyone	Hard reset (camera / panel / placement) if something gets stuck
`/slotsexport`, `/slotsimport`	Admins	Export / import the editor's machine layout

Permissions

Admin access is granted by an ACE permission or by your framework's admin group:

lua

Config.Admin = {
    useAce          = true,
    acePermission   = 'orb_slots.admin',
    autoGrantGroups = { 'group.admin', 'group.superadmin', 'group.owner', 'group.god' },
    useFramework    = true,   -- also accept framework admins
}

To grant the ACE manually in server.cfg:

cfg

add_ace group.admin orb_slots.admin allow

If in doubt, run /slotperms in-game — it tells you whether you're recognised as an admin and prints the exact line to add. Every admin action is validated server-side.

Developer / Calibration Commands

Only registered when Config.DevCommands = true (keep it false in production). These spawn test cabinets and tune placement/camera:

/ps1 … /ps4   /psv1 … /psv3   /psh1 … /psh3   /psf1   /psa
/slotprop   /slotremoveall   /slotground   /slotgroundall   /slotcam
/statue   /statuez   /statueturn   /statuepos

Integrations

There are no general-purpose exports — the client↔server protocol (spin, claim, buy-in, leaderboard) is internal and permission-guarded. For external dashboards or stat integrations, read the orb_slot_* SQL tables directly.