RuneXPartner Console
RUNE//X · PARTNER INTELLIGENCE NETWORK
Built for trusted creator communities

Shared intelligence.Local command.

RuneX gives Discord communities a controlled way to detect known threats, document evidence, and enforce partner protections without surrendering control of their own server.

Enter partner console Join RuneX Discord
01 Discord-native02 Audit-ready03 Partner-controlled
RX
RuneX IntelligenceProtection overview
Operational
Protection modeActivePartner rules synchronized
DetectionLiveJoin + manual scans
Case historyAuditedChanges stay traceable
Representative activity● SECURE
✓
Partner scan completeMember roster checked · no interruptions
!
Automatic strike recordedDuplicate-safe partner detection · STR-AUTO
↗
Case audit updatedEvidence and moderator history preserved
⌁
Partner signalVerified
◇
EnforcementServer controlled

One protection layer for the work your community cannot afford to lose.

GLOBAL CASESPARTNER SCANSAUTOMATIC STRIKESAPPEAL PATHSCOMMERCE ACCESS
LIVE NETWORK

The RuneX network,
as it stands now.

SECURE DATA LINKConnecting to RuneX
GLOBAL INTELLIGENCE—

documented blacklist cases

PARTNER NETWORK—

active verified servers

RUNEX SERVICEConnecting

bot operating status

LAST SIGNALWaiting

automatic website sync

PUBLIC PARTNER DIRECTORY

Communities connected to RuneX.

Verified partners control whether their server is shown here. Private partner records never appear on the public website.

Partner directory is connecting

Approved public listings will appear automatically.

THE PEOPLE BEHIND RUNEX

Meet the team.

A small team building shared protection, accountable moderation, and a safer partner network for creator communities.

MEMBER // 01 CORE TEAM
Creator & Lead Developer

Pearly

Builds the RuneX platform, partner systems, website, and core protection workflow.

846601713141284925Open Discord profile
MEMBER // 02 CORE TEAM
Owner & Community Direction

Nefeli

Leads the community, partnership direction, and final operational decisions.

265330888030683157Open Discord profile
MEMBER // 03 CORE TEAM
Emblem Creator

Honeydew

Created the official RuneX emblem and helped shape the project’s visual identity.

712131209513402408Open Discord profile
PRODUCT

Protection with context,
not just a ban list.

RuneX connects detection, documented casework, partner controls, and review paths so moderation decisions stay useful and explainable.

01
Detection

Partner scans

Run report-only reviews or enforce eligible matches while retaining control over each server.

02
Intelligence

Automatic strikes

Record repeat detections with the source server, baseline reason, evidence, and a duplicate-safe audit key.

03
Casework

Case intelligence

Keep reasons, evidence, aliases, edits, strike history, and enforcement totals in one traceable record.

04
Control

Local exceptions

Partner teams can use local whitelists, local blocks, and protected management-server behavior.

05
Resolution

Managed appeals

Blacklisted users receive a clear appeal path while moderation staff retain the complete case context.

06
Commerce

Commerce access

Configure creator products and verify supported purchases before assigning protected Discord access.

HOW IT WORKS

A clear path from signal to decision.

Every partner retains authority over its own community. RuneX provides the shared context and controlled tools needed to act consistently.

Discuss partner access
  1. 01

    Connect your server

    Invite RuneX and place its role correctly for the permissions you choose to use.

  2. 02

    Choose your protections

    Configure report-only or enforcement behavior, logs, local blocks, and exceptions.

  3. 03

    Detect with context

    Manual scans and join checks compare members with documented RuneX cases.

  4. 04

    Review the record

    Staff can inspect evidence, strikes, edits, and enforcement history before deciding next steps.

COMMANDS

Powerful when needed.
Quiet when not.

RuneX stays inside Discord, where partner teams already work. Access is permission-aware and sensitive responses can remain private.

Partner protection

Scan and configure

/scan

Review the current server or enforce eligible blacklist matches.

/settings

Configure RuneX protection and partner-server behavior.

/ping

Confirm the bot is online and responding.

Case intelligence

Review and manage

/bladd

Create a documented blacklist case.

/blsearch

Open the current intelligence record for a user.

/strike

Add, view, or void a case strike with audit history.

Mass operations

Process controlled batches

/blmassadd

Import Discord IDs from pasted text or a TXT file.

/blmassedit

Safely add to or replace supplied batch fields.

/blmasslist

Browse existing mass-blacklist batches.

Creator commerce

Verify protected access

/commerce-product-add

Connect a supported creator product to a role.

/commerce-product-list

Review configured products and status.

/verify-purchase

Verify a supported purchase and grant access.

Command availability depends on staff level, server configuration, and enabled RuneX features.

SAFETY BY DESIGN

Automation with
guardrails.

Shared intelligence is only useful when it is paired with review, local choice, and a route to correct mistakes.

✓ Management server protected
01

Report before enforcement

A report-only scan shows matches without attempting bans, giving staff a deliberate review path.

02

Protected appeal access

The management and appeal server blocks enforcement so affected users can still reach the appeal process.

03

Local authority remains local

Partner servers choose their own settings, exceptions, role hierarchy, and whether enforcement is enabled.

04

Changes stay attributable

Case edits and strike removals preserve who changed what and when, supporting accountable moderation.

VERIFIED PARTNER NETWORK

Access is earned.
Control stays local.

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.

Open Partner Console Ask about partnership
VERIFICATION PROTOCOL6 CHECKS
  1. 01

    The applicant owns the server or has Manage Server authority.

  2. 02

    The server ID, owner ID, primary contact, and community purpose are supplied.

  3. 03

    RuneX safety, evidence-handling, privacy, and appeal rules are accepted.

  4. 04

    RuneX is installed with the required role placement, logs, and permissions.

  5. 05

    A report-only test scan and configuration review are completed successfully.

  6. 06

    RuneX management manually approves the server before dashboard access unlocks.

GET THE RIGHT HELP

Three paths. One clear next step.

Each request opens through the RuneX Discord, where dedicated ticket panels route it to the right team.

General help

Support

Get help with RuneX, partner setup, commands, or a technical issue.

Open support
Case review

Appeal

Request a formal review of an existing RuneX blacklist case.

Start an appeal
Submit evidence

Report

Send staff a new safety report with the information and proof they need.

File a report
RUNEX PARTNER NETWORK

Protect your community
without losing control.

Talk with the RuneX team about partner access, setup, and the right protection mode for your server.

Start partner verification