/permcheck - Server Raidability Check

The /permcheck command tests whether a server is raidable. It does this by checking your member permissions (such as UseExternalApps) or by executing a message-sending visibility check.

Command Usage

/permcheck

How It Works

  1. Member Permissions Check:
    • If the user has active member permissions in the channel (non-zero bitfield), it checks for the UseExternalApps permission.
    • If UseExternalApps is present: Server is raidable.
    • If missing: Server is not raidable.
  2. Fallback Message Test:
    • If member permissions could not be checked, the bot attempts to send a test message (_ _).
    • If the message is successfully sent and public: Server is raidable.
    • If the message is forced ephemeral: Server is not raidable (messages are private).
    • If the message-send fails (exception): Server is not raidable (missing permissions).
  3. DM Check:
    • Direct messages are always raidable. Responds with: "dms are always raidable mf, are you lwk fucking slow???"

Interactive Features

The Raid Button

When /permcheck finishes running, it outputs a customized ContainerBuilder UI:

  • If Raidable:
    • Sets green accent color (#57F287) with header # raidable!!1!1!1!!.
    • Attaches a success button: "click me to r4id!!!!!!" (Custom ID: rynzen_permcheck_r4id_trigger).
    • Clicking this button immediately executes the /r4id command for the user (only the user who triggered /permcheck can click this button, others get "this button aint for u lol").
  • If Not Raidable:
    • Sets red accent color (#ED4245) with header # not raidable!!1!1!1!!.
    • Attaches a disabled button: "not raidable" (Custom ID: rynzen_permcheck_button_disabled).
  • /r4id - Start a raid
  • /interaction-r4id - Interaction-based raiding
  • /auto-r4id - Automated raiding panel