Admin & Debug Commands
This page is hidden behind SLKARDS' spoiler gate. There's a way to unlock it. If you know the way, use it — otherwise, keep exploring the game.
Admin & Debug Commands
SLKARDS uses Discord’s built-in slash commands. Usage notation: <required> parameters are required, (optional) are optional.
None of the admin or debug commands are ephemeral — their output is posted in-channel so actions leave an audit trail.
[REDACTED]
Section titled “[REDACTED]”Admin commands configure server-specific behaviour — spawn channel, spawn timer, player access, feature toggles. They require the server’s configured admin role, with one exception: /admin-slkards setup can be run by any user with the Administrator Discord permission, since the admin role does not exist yet when the bot is first installed.
[REDACTED]
Section titled “[REDACTED]”The setup wizard for first-time bot installation. This is intended to be the first command run after the bot joins a server.
It walks the admin through all required configuration in a step-by-step interactive flow. The wizard can also be re-run at any time to repair missing channels or reconfigure settings.
-
Admin Role: The bot prompts the admin to select or create the admin role. This role grants access to all admin and debug commands. The admin can pick an existing server role or let the bot create a new
SLKARDS Adminrole. -
Player Role: The bot prompts the admin to select or create the player role. This role is used for pinging players on wipe warnings and other announcements. The admin can pick an existing role or let the bot create a new
SLKARDS Playerrole. -
Channel Creation: The bot creates the
SLKARDScategory and all 13 server-wide channels (announcements,premium,events,wipes,leaderboards,admin-chat,admin-commands,spawn,battles,trading,stores,player-chat,alliances-chat) with the correct permissions per channel as described in Bot Architecture. If any of these channels already exist (from a previous setup), the bot skips creating them and links to the existing ones instead. -
Spawn Timer: The bot prompts the admin to configure the spawn timer interval (min and max hours between spawns). Defaults to 1–3 hours if skipped.
-
Thread Cleanup: The bot prompts the admin to choose the thread cleanup policy: auto-delete after 5 minutes (default), auto-archive after 1 hour, or auto-archive after 24 hours.
-
Confirmation: The bot displays a summary of everything that was configured — roles, channels created, spawn timer, thread cleanup setting — and asks for final confirmation. On confirm, the bot saves all configuration to
configs_guilds, initializes leaderboard embeds in the leaderboards channel, posts the premium info embed, and marks the server as active.
Usage: /admin-slkards setup
[REDACTED]
Section titled “[REDACTED]”Bans a player from using the SLKARDS bot on this server. The player’s data is preserved but they cannot interact with any commands until unbanned. A reason can optionally be specified and is logged.
Usage: /admin-slkards ban <player> (reason)
[REDACTED]
Section titled “[REDACTED]”Unbans a previously banned player, restoring their ability to use SLKARDS commands.
Usage: /admin-slkards unban <player>
[REDACTED]
Section titled “[REDACTED]”Completely resets a player’s data on this server. Intended for cases where a player’s data has become corrupted, or at the player’s own request.
Usage: /admin-slkards resetplayer <player>
[REDACTED]
Section titled “[REDACTED]”Sends a bot-formatted announcement message in the announcement channel. Useful for server-specific SLKARDS news, event announcements, or rule changes. Accepts optional image (attachment with image/* content-type), ping_player_role (boolean — mentions the configured player role), and color (hex #RRGGBB or a series name to use the series-themed embed color).
Usage: /admin-slkards announce <message> (image) (ping_player_role) (color)
[REDACTED]
Section titled “[REDACTED]”Forces an immediate rebuild of every leaderboard for this server, bypassing the scheduled cadence (daily for ELO, every 6 hours for the rest). Useful after a manual data fix or a debug run when an admin wants the boards to reflect the new state right away. Replies inline with a per-category row count. Backed by cogs/admin_config.py.
Usage: /admin-slkards refresh-leaderboards
[REDACTED]
Section titled “[REDACTED]”Displays a paginated log of recent admin and debug command usage on this server, including timestamps, who used them, and what parameters were passed. Useful for auditing admin actions.
Usage: /admin-slkards viewlogs (count)
[REDACTED]
Section titled “[REDACTED]”Creates and immediately starts a new server-wide event. Walks the admin through an interactive setup: event name, type (competition/task/co-op), description, duration in hours, optional passive modifiers (spawn rate, koin bonus, GP bonus multipliers), and reward configuration appropriate to the event type. Once confirmed, the event begins immediately and is announced in the slkards-events channel. Only one event may be active at a time.
Usage: /admin-slkards eventcreate
[REDACTED]
Section titled “[REDACTED]”Schedules a future server-wide event. Identical setup flow to eventcreate, with the addition of a start date and time prompt. The event begins automatically at the specified time. Scheduled events appear in the eventlist output and can be cancelled before they launch.
Usage: /admin-slkards eventschedule
[REDACTED]
Section titled “[REDACTED]”Cancels the currently active event, or a scheduled event by its event ID (visible via eventlist). Requires confirmation. Players retain any rewards already earned before cancellation. A cancellation notice is posted in the slkards-events channel.
Usage: /admin-slkards eventcancel (event_id)
[REDACTED]
Section titled “[REDACTED]”Displays all currently active and scheduled events on this server, including event type, time remaining or scheduled start time, and a brief configuration summary. Ephemeral command.
Usage: /admin-slkards eventlist
[REDACTED]
Section titled “[REDACTED]”Reviews and approves or denies a pending custom series submission. Displays all submitted kard images, names, descriptions and series details for review before approval.
Usage: /admin-slkards customapprove <submission_id> <approve|deny> (reason)
[REDACTED]
Section titled “[REDACTED]”Debug commands are usable only by the server admin role. They exist for testing and forcing specific events, and should only be handed out to trustworthy members.
[REDACTED]
Section titled “[REDACTED]”Forcefully renders a kard, regardless if it has been captured yet or not. Useful for debugging if a kard’s picture does not render, or for visualizing new kards added.
Usage: /debug-slkards make <kard_id>
[REDACTED]
Section titled “[REDACTED]”Forcefully spawns a kard, regardless of the current spawn timer. Useful for testing new spawning mechanics, or checking if a specific kard can spawn.
Usage: /debug-slkards forcespawn (kard_series, kard_id)
[REDACTED]
Section titled “[REDACTED]”Forcefully wipes the kards of all current players. Useful for testing new wipe mechanics, or for decreasing the total player kard count at a moderator’s discretion.
Usage: /debug-slkards forcewipe (time_integer_in_minutes)
[REDACTED]
Section titled “[REDACTED]”Shows the current spawn timer, meaning the time the next kard will spawn. Useful for testing if the spawn timer is working in case of changes.
Usage: /debug-slkards nextspawn
[REDACTED]
Section titled “[REDACTED]”Shows the current wipe timer, meaning the day and time the next wipe will occur. Useful for testing if the wipe timer is working in case of changes.
Usage: /debug-slkards nextwipe
[REDACTED]
Section titled “[REDACTED]”Adds or removes koins (or GP — 0.4) from a player’s balance. Intended for debugging economy issues, compensating players for bugs, or testing. Negative values deduct. The gp currency option is a 0.4 placeholder today; the koins path is identical to the prior /debug-slkards givekoins command. player defaults to the invoking admin. Backed by cogs/debug_economy.py. This unified command replaces the prior /debug-slkards givekoins and /debug-slkards givegp.
Usage: /debug-slkards grant <currency: koins|gp> <amount> (player)
[REDACTED]
Section titled “[REDACTED]”Inserts kard instances into a player’s inventory. Accepts a comma-separated list of kard IDs (e.g. 0,1,2,-1); Almighty IDs are allowed. Each ID adds a fresh instance with default state. player is optional and defaults to the invoking admin. Useful for setting up test scenarios. Backed by cogs/debug_inventory.py.
Usage: /debug-slkards givekards <kards> (player)
[REDACTED]
Section titled “[REDACTED]”Removes one instance per kard ID from a player’s inventory. Accepts the same comma-separated ID list as givekards. If a player owns multiple instances of the same ID, only one is removed per occurrence in the argument. player is optional and defaults to the invoking admin. Useful for unwinding a givekards mistake or reproducing a specific binder shape. Backed by cogs/debug_inventory.py.
Usage: /debug-slkards takekards <kards> (player)
[REDACTED]
Section titled “[REDACTED]”Equips a Juggernaut Suit on a specific kard the target player owns, bypassing the normal Zeno purchase flow. Pass unequip:true to remove an equipped suit from a kard instead. Useful for testing the wipe-interception path without setting up a full GP economy run. Backed by cogs/wipes.py.
Usage: /debug-slkards equipsuit <player> <kard_id> (unequip)
[REDACTED]
Section titled “[REDACTED]”Clears an Almighty-challenge cooldown for a player. Pass a specific series to clear just that cooldown, or omit the series arg to clear cooldowns for every Almighty challenge at once. Defaults to the invoking admin if no player is specified. Backed by cogs/debug_secrets.py.
Usage: /debug-slkards resetcooldown (series) (player)
[REDACTED]
Section titled “[REDACTED]”Reloads the static-data registry (data/static_*.json, data/kardData.json, data/backrooms_almighty.json) without restarting the bot. Useful after editing kard/series/pack content. Backed by cogs/debug_core.py.
Usage: /debug-slkards reloadstatic
[REDACTED]
Section titled “[REDACTED]”Dynamically reloads a single cog by name, picking up code changes without a full restart. The cog must declare itself reloadable (the _bootstrap cog is not). Backed by cogs/debug_core.py.
Usage: /debug-slkards reloadcog <cog_name>
[REDACTED]
Section titled “[REDACTED]”Simulates a specific game event without it actually taking effect, such as a wipe, a spawn, or a battle outcome. Outputs the result to the admin only. Useful for testing probability and verifying game logic. Backed by cogs/debug_core.py.
Usage: /debug-slkards simulate <event_type> (parameters)
See also: Player Commands · Bot Architecture · Data Schema · Notifications