Commands

This page is aligned with the active command registry in ../infinitea-bot/src/main.ts#createSlashCommands.

Command Conventions

• All commands are guild-context commands.
• If a command has both a default permission and runtime checks, runtime checks still apply.
• Option names below match the registry exactly.

Core Utility

/arpg

• Purpose: Show ARPG timeline data for a selected game.
• Permissions: Default command visibility.
• Arguments:
  • game (required, autocomplete)
• Example:

/arpg game:path-of-exile

/temp-message

• Purpose: Post a message that is auto-deleted after a duration.
• Permissions: Send Messages
• Arguments:
  • duration (required, HH:MM:SS or seconds)
  • message (required)
• Example:

/temp-message duration:00:10:00 message:Maintenance starts in 10 minutes.

/clear

• Purpose: Delete messages in the current text channel.
• Permissions: Manage Messages
• Arguments:
  • number_of_messages (required, integer 1-500)
  • filter_by_user (optional)
  • filter_by_role (optional)
  • filter_by_bot (optional boolean)
• Example:

/clear number_of_messages:100 filter_by_role:@RaidTeam

/remove

• Purpose: Remove reactions from recent messages in the current text channel.
• Permissions: Manage Messages
• Arguments:
  • number_of_reactions_to_remove (required, integer 1-500)
  • emoji (optional)
  • filter_by_user (optional)
  • filter_by_role (optional)
  • filter_by_bot (optional boolean)
• Example:

/remove number_of_reactions_to_remove:200 emoji:🔥 filter_by_bot:false

/roles

• Purpose: Bulk role operations by filter role criteria.
• Permissions: Administrator
• Subcommands:
  • add: where_user_has_role_1 + give_them_role_1 required; _2/_3 options optional.
  • remove: where_user_has_role_1 + take_away_role_1 required; _2/_3 options optional.
  • replace: where_user_has_role_1 + replacing_with_role_1 required; _2/_3 options optional.
• Example:

/roles add where_user_has_role_1:@Trial give_them_role_1:@Member

Leaderboards And Activity

/rank and /card

• Purpose: Show rank card for yourself or another member.
• Permissions: Default command visibility.
• Arguments:
  • user (optional)
• Example:

/rank user:@Member
/card

/leaderboard

• Purpose: Show current leaderboard panel, or per-user summary when user is provided.
• Permissions: Default command visibility.
• Arguments:
  • user (optional)
• Behavior: Bot reply auto-deletes after about 120 seconds.
• Example:

/leaderboard
/leaderboard user:@Member

/post_leaderboard

• Purpose: Post a persistent leaderboard panel with refresh/select controls.
• Permissions: Manage Messages
• Arguments:
  • activity_type_1 (required, autocomplete)
  • activity_type_2 ... activity_type_9 (optional, autocomplete)
• Allowed values:
  • Activity: Voice, CommRep, Engagement, Reaction, StaffRep, Message
  • Ember: Ember Current, Ember Lifetime, Embers Spent
• Example:

/post_leaderboard activity_type_1:Message activity_type_2:Voice activity_type_3:Ember Current

/drop

• Purpose: Manually trigger an XP drop for testing.
• Permissions: Administrator
• Arguments:
  • activity_type (required choice)
  • amount (required integer, min 1)
  • lottery_chance (optional integer 0-100)
  • lottery_multiplier (optional number, min 1)
• Runtime guardrails:
  • Staff reputation drops are rejected.
• Example:

/drop activity_type:Message amount:150 lottery_chance:20 lottery_multiplier:2

/xp

• Purpose: Add, remove, or reset XP.
• Permissions: Administrator
• Subcommands:
  • add user amount [activity_type]
  • remove user amount [activity_type]
  • reset user [activity_type]
• Arguments:
  • user (required)
  • amount (required for add/remove, min 1)
  • activity_type (optional choice; omitted means all tracked types where applicable)
• Example:

/xp add user:@Member amount:500 activity_type:Message
/xp reset user:@Member

/give_rep

• Purpose: Give 1 Community Reputation point.
• Permissions: Default command visibility.
• Arguments:
  • user (required)
• Example:

/give_rep user:@HelpfulMember

/give_staff_rep

• Purpose: Give 1 Staff Reputation point.
• Permissions: Administrator
• Arguments:
  • user (required)
• Example:

/give_staff_rep user:@Moderator

Emberworks

/emberworks, /wallet, /bal, /balance

• Purpose: Open Emberworks wallet/hub UI.
• Permissions: Default command visibility.
• Arguments:
  • /balance supports optional user
• Examples:

/wallet
/balance user:@Member

• Related: Emberworks

Info Book

/info

• Purpose: Fetch Info Book entry content.
• Permissions: Default command visibility.
• Arguments:
  • category (required, autocomplete)
  • subcategory (optional, autocomplete)
• Entitlements:
  • Category access requires INFO_BOOK_CATEGORIES.
  • Subcategory access requires INFO_BOOK_SUB_CATEGORIES when subcategory is used.
• Example:

/info category:Rules
/info category:Rules subcategory:Voice

• Related: Info Book

LFG

/post_lfg

• Purpose: Post the configured LFG container in the current channel.
• Permissions: Manage Messages
• Arguments: none
• Example:

/post_lfg

• Related: LFG System

Sentry Reporting

/report_history

• Purpose: View a user's moderation report history.
• Permissions:
  • Default: any of Manage Messages, Manage Roles, or Manage Nicknames
  • Runtime: same permission check enforced
• Arguments:
  • user (optional)
  • discord_id (optional, 17-20 digits)
• Example:

/report_history user:@Member
/report_history discord_id:123456789012345678

/report

• Purpose: Submit a moderation report.
• Permissions:
  • Default: any of Manage Messages, Manage Roles, or Manage Nicknames
  • Runtime: Ban Members required
• Arguments:
  • user (optional)
  • discord_id (optional, 17-20 digits)
  • At least one of user or discord_id must be supplied.
• Entitlement: SENTRY_REPORT
• Example:

/report user:@Member
/report discord_id:123456789012345678

• Related: Sentry

Portals Ticket Lifecycle

/claim

• Purpose: Claim an active portal request channel.
• Permissions: Send Messages plus portal runtime support-access checks.
• Arguments: none
• Example:

/claim

/close

• Purpose: Close an active portal request channel.
• Permissions: Send Messages plus portal runtime support-access checks.
• Arguments: none
• Example:

/close

/delete

• Purpose: Archive an active portal request channel.
• Permissions: Manage Messages plus portal runtime support-access checks.
• Arguments: none
• Example:

/delete

• Related: Portals, Portal Requests