Pearly
Builds the RuneX platform, partner systems, website, and core protection workflow.
846601713141284925Open Discord profile RuneX gives Discord communities a controlled way to detect known threats, document evidence, and enforce partner protections without surrendering control of their own server.
One protection layer for the work your community cannot afford to lose.
A small team building shared protection, accountable moderation, and a safer partner network for creator communities.
Builds the RuneX platform, partner systems, website, and core protection workflow.
846601713141284925Open Discord profile Leads the community, partnership direction, and final operational decisions.
265330888030683157Open Discord profile Created the official RuneX emblem and helped shape the project’s visual identity.
712131209513402408Open Discord profile RuneX connects detection, documented casework, partner controls, and review paths so moderation decisions stay useful and explainable.
Run report-only reviews or enforce eligible matches while retaining control over each server.
Record repeat detections with the source server, baseline reason, evidence, and a duplicate-safe audit key.
Keep reasons, evidence, aliases, edits, strike history, and enforcement totals in one traceable record.
Partner teams can use local whitelists, local blocks, and protected management-server behavior.
Blacklisted users receive a clear appeal path while moderation staff retain the complete case context.
Configure creator products and verify supported purchases before assigning protected Discord access.
Every partner retains authority over its own community. RuneX provides the shared context and controlled tools needed to act consistently.
Discuss partner accessInvite RuneX and place its role correctly for the permissions you choose to use.
Configure report-only or enforcement behavior, logs, local blocks, and exceptions.
Manual scans and join checks compare members with documented RuneX cases.
Staff can inspect evidence, strikes, edits, and enforcement history before deciding next steps.
RuneX stays inside Discord, where partner teams already work. Access is permission-aware and sensitive responses can remain private.
/scanReview the current server or enforce eligible blacklist matches.
/settingsConfigure RuneX protection and partner-server behavior.
/pingConfirm the bot is online and responding.
/bladdCreate a documented blacklist case.
/blsearchOpen the current intelligence record for a user.
/strikeAdd, view, or void a case strike with audit history.
/blmassaddImport Discord IDs from pasted text or a TXT file.
/blmasseditSafely add to or replace supplied batch fields.
/blmasslistBrowse existing mass-blacklist batches.
/commerce-product-addConnect a supported creator product to a role.
/commerce-product-listReview configured products and status.
/verify-purchaseVerify a supported purchase and grant access.
Command availability depends on staff level, server configuration, and enabled RuneX features.
Shared intelligence is only useful when it is paired with review, local choice, and a route to correct mistakes.
A report-only scan shows matches without attempting bans, giving staff a deliberate review path.
The management and appeal server blocks enforcement so affected users can still reach the appeal process.
Partner servers choose their own settings, exceptions, role hierarchy, and whether enforcement is enabled.
Case edits and strike removals preserve who changed what and when, supporting accountable moderation.
The RuneX Partner Console gives approved server leadership a direct path to onboarding, configuration status, protection tools, and support without exposing private case information publicly.
The applicant owns the server or has Manage Server authority.
The server ID, owner ID, primary contact, and community purpose are supplied.
RuneX safety, evidence-handling, privacy, and appeal rules are accepted.
RuneX is installed with the required role placement, logs, and permissions.
A report-only test scan and configuration review are completed successfully.
RuneX management manually approves the server before dashboard access unlocks.
Each request opens through the RuneX Discord, where dedicated ticket panels route it to the right team.
Get help with RuneX, partner setup, commands, or a technical issue.
Open supportRequest a formal review of an existing RuneX blacklist case.
Start an appealSend staff a new safety report with the information and proof they need.
File a reportTalk with the RuneX team about partner access, setup, and the right protection mode for your server.
Start partner verification