Welcome to the ModereX Control Panel — a real-time, web-based moderation hub for your Minecraft server. Everything you do here is instantly synced to the server: punishments take effect immediately, activity logs update live, and staff chat works cross-platform between the panel and in-game.

What You Can Do

• Moderate players — Ban, mute, warn, kick, and IP-ban with full evidence support
• Monitor in real-time — See who's online, watch chat live, and get instant alerts
• Automate moderation — Set up automod rules for chat filtering, spam, caps, and links
• Track everything — Full activity logs for chat, commands, sessions, punishments, and automod events
• Monitor performance — TPS, memory, CPU, entity counts, laggy chunks, and diagnostics
• Record & review — Session replays with 3D playback of player actions
• Communicate — Staff chat works between the web panel and in-game simultaneously
• Customize — Choose from 5 themes, 13 background patterns, 7+ accent colors, and sound effects

How It Works

The panel connects to your Minecraft server via WebSocket. When you issue a punishment, it's executed on the server instantly. When a player joins or chats, you see it here in real-time. The connection status is shown in the top-right corner — a green dot means you're connected and synced.

How to Connect

1. Open the panel URL in your browser (usually server-ip:8080)
2. You'll see a unique authentication token displayed on screen
3. Join the Minecraft server and run /mx link <token>
4. The panel will automatically authenticate and load your session

Alternatively, you can generate a token in-game with /mx gettoken and paste it into the panel.

Trusted Devices (Auto Sign-In)

After a successful login, your device is remembered as "trusted." Next time you visit, you'll be signed in automatically without needing a new token. You can manage this in My Settings > Device Trust.

• Trusted devices use encrypted token storage (AES-GCM)
• Auto-login works for up to 7 days
• You can revoke trusted devices at any time from Settings

Lost Access / Token Issues

1. Close all browser tabs with the panel open
2. Clear your browser's local storage for this site (or use incognito mode)
3. Navigate to the panel URL again to receive a fresh token
4. Link the new token in-game with /mx link <token>

Gateway Mode (Multi-Server)

If your network uses the ModereX Gateway, you'll first see a server selection screen. Pick the server you want to moderate, and the panel will connect through the gateway. You can switch servers at any time without re-authenticating.

Just connected for the first time? Here's a quick walkthrough of what to do:

1. Explore the Sidebar

The left sidebar is your main navigation. Each item opens a different page. The most important pages are:

• Dashboard — Overview stats and quick actions
• Players — Browse and search all players
• Punishments — View all punishment history
• Activity Log — Full audit trail of chat, commands, and events

2. Check the Dashboard

Start on the Dashboard to get a quick overview: how many players are online, active punishments, recent activity, and quick action buttons. Click any stat card to jump to its detail page.

3. Look Up a Player

Go to the Players page and click on any player's row to open their profile drawer. This shows their full history, IP info (if you have permission), sessions, and lets you take actions.

4. Customize Your Experience

Visit My Settings to personalize the panel:

• Choose a theme (Default, Apple Light, Apple Dark, Opera GX, Oldschool)
• Pick an accent color or set a custom one
• Select a background pattern (13 options including Aurora, Matrix, and Nebula)
• Toggle sound effects on/off and adjust volume

5. Use Global Search

Press Ctrl+K at any time to open global search. Search for players by name or UUID, jump to pages, or find punishment cases. Use arrow keys to navigate results and Enter to select.

The Dashboard is your command center. It provides a real-time snapshot of your server's moderation state at a glance.

Primary Stats (Top Row)

These large stat cards are clickable — click any to jump to the relevant page:

• Active Punishments — Total currently active bans + mutes + warns
• Automod Events — Number of automod rules triggered recently
• Watchlist Alerts — Alerts from monitored players
• Players Online — Current player count on the server

Secondary Stats (Second Row)

• Active Bans — Currently active bans only
• Active Mutes — Currently active mutes only
• Warnings (24h) — Warnings issued in the last 24 hours
• Staff Online — Staff members currently on the server

Quick Actions

Below the stats, you'll find shortcut buttons for common tasks: Punish Player, View Logs, Manage Watchlist, Automod Rules, and Settings.

Activity Feed

The bottom section shows the most recent moderation events across the server: punishments issued, players joining/leaving, automod triggers, and staff actions. Click "View All" to see the full Activity Log.

The Players page lists every player who has joined the server. Use the search bar to find players by name, UUID, or IP address.

Player Table

Each row shows the player's avatar, name, platform (Java/Bedrock), online status, last seen time, and flag count. Online players show a green badge; players with active punishments show ban/mute indicators.

Player Profile Drawer

Click any player row to open their detailed profile in a slide-out drawer. The drawer shows:

• Identity — Username, UUID, IP address (requires moderex.info.ip)
• Punishment History — All past and active bans, mutes, warns, kicks
• Nickname History — Previous names the player has used
• Chat & Command Logs — Recent messages and commands (requires moderex.logs.chat / moderex.logs.commands)
• Session History — Join/leave timestamps and play duration
• Automod Triggers — Rules this player has triggered

Right-Click Context Menu

Right-click any player in the table for quick actions: View Profile, Punish, Add to Watchlist, or Copy UUID.

Actions from the Drawer

The profile drawer has action buttons at the top:

• Punish — Opens the punishment modal pre-filled with this player
• Watchlist — Toggle watchlist monitoring for this player
• Copy UUID — Copy the player's UUID to clipboard

Punishment Types

• Ban — Prevents the player from joining. Can be temporary or permanent.
• IP Ban — Blocks all connections from a player's IP address. Use for ban evasion.
• Mute — Blocks the player from chatting, using /msg, writing signs, and books.
• Warn — Issues a warning. Warnings can auto-escalate to mutes or bans via the escalation system.
• Kick — Immediately disconnects the player. Kicks are logged but have no lasting effect.

How to Punish a Player

1. Click the Punish Player button on the Dashboard, or click "Punish" from any player's profile drawer
2. Select the player (or type their name if not pre-selected)
3. Choose the punishment type from the dropdown
4. Enter a reason (required) — be specific and factual
5. Set a duration using the duration picker (years, months, weeks, days, hours, minutes), or toggle Permanent
6. Optionally attach evidence (files or activity log entries)
7. Click Submit to execute

Duration Picker

The duration picker lets you set precise durations. You can enter values in any combination of fields. Example: 1 month + 2 weeks = 6 weeks total. Toggle the "Permanent" switch for a permanent punishment (requires moderex.ban or moderex.mute permission; temp-only staff use moderex.tempban / moderex.tempmute).

Mass Punishments

Need to punish multiple players at once? You can add multiple players to the punishment modal using the player tag pills. This is useful for groups of rule-breakers caught in the same incident. Each player receives an individual case ID.

Revoking Punishments

To revoke an active punishment, go to the Punishments page, find the case, and click the revoke button. You'll be asked for a reason. Revoked punishments are kept in history but marked as revoked. Kicks and expired punishments cannot be revoked.

Viewing Punishment Details

Click any punishment case to see full details: the player, staff who issued it, reason, duration, evidence attached, and timeline. Requires moderex.command.viewpunishment.

Templates let you save common punishment configurations for quick, consistent enforcement. Instead of typing the same reason and duration every time, create a template once and apply it with a single click.

Creating a Template

1. Go to the Templates page
2. Click Create Template
3. Enter a name (e.g., "Hacking - 30 Day Ban")
4. Select the punishment type (Ban, Mute, Warn, Kick)
5. Set the default duration
6. Enter the default reason
7. Save the template

Using a Template

When punishing a player, you can select a template from the dropdown to auto-fill the type, reason, and duration. You can still modify any field before submitting.

Recommended Templates

• Hacking — Ban, 30 days, "Using unauthorized client modifications"
• Toxicity — Mute, 7 days, "Toxic behavior / harassment"
• Spam — Mute, 1 hour, "Chat spam"
• Advertising — Ban, 7 days, "Advertising other servers"
• First Warning — Warn, "Rule violation - first offense"

ModereX has a built-in evidence system that lets you attach proof to any punishment. Evidence is permanently linked to the case and can be reviewed later by any staff member with permission.

Types of Evidence

• File Uploads — Screenshots (PNG, JPG), videos (MP4, MKV, MOV), and other files up to 250MB
• Activity Log Entries — Select specific chat messages, commands, or events from the player's activity log as evidence

How to Attach Evidence

1. In the punishment modal, expand the Evidence section
2. To upload a file: click the upload button or drag & drop a file
3. To attach activity logs: search the player's recent activity and click entries to select them
4. Selected evidence appears as pills below the search area
5. Submit the punishment — evidence is linked to the case automatically

Viewing Evidence

Evidence attached to a punishment can be viewed from the Punishment Details page. Images show as inline previews, videos can be played directly, and activity log snapshots show the original log content at the time of attachment.

The Watchlist lets you monitor suspicious players. When a watched player does something noteworthy (joins the server, triggers automod, receives a punishment), you get an instant alert on the panel.

Adding Players

• From any player's profile drawer, click the Watchlist button
• Or go to the Watchlist page and click the + button to search and add players
• Optionally add a reason for monitoring (visible to other staff)

How Alerts Work

When a watched player triggers an alert, you'll see:

• A slide-down alert bar at the top of the panel with the player's name and event
• A sound notification (if enabled in Settings)
• Quick action buttons to view the player's profile or dismiss the alert

Watchlist Page Layout

The page shows two columns: Monitored Players on the left (with status indicators) and Recent Alerts on the right (newest first). Click any alert to jump to the player's profile.

Automod automatically moderates chat based on configurable rules. It runs server-side and can block messages, warn players, or escalate to punishments — all without staff intervention.

Rule Conditions

• Contains — Matches if the message contains specific words or phrases
• Regex — Advanced pattern matching (e.g., d[i1!]sc[o0]rd to catch "discord" variants)
• Spam Detection — Detects repeated messages or flooding
• Caps Filter — Triggers on excessive capital letters (configurable threshold)
• Link Filter — Detects URLs. You can whitelist specific domains.
• Repeat Detection — Catches players repeating the same message

Rule Actions

When a rule triggers, one or more actions execute:

• Block — Silently blocks the message (only the sender sees it)
• Warn — Issues an automatic warning to the player
• Mute — Automatically mutes the player for a set duration
• Ban — Automatically bans the player
• Alert Staff — Sends an alert to all online staff and the web panel

Automod Tester

Click the Automod Tester button to test messages against your rules without affecting real players. Type a test message and see which rules would trigger and what actions would be taken.

Best Practices

• Start with "Block + Alert" actions and escalate only after monitoring false positives
• Use regex sparingly — overly broad patterns cause false positives
• Always test rules with the Automod Tester before enabling them
• Set reasonable cooldowns to avoid spamming staff with alerts

ModereX integrates with anticheats like Grim to provide a unified alert dashboard. Anticheat violations appear as real-time alerts on the panel and can trigger automatic actions.

Alert Levels

For each anticheat check type, you can configure the alert level:

• Off — Ignore this check entirely
• Toast — Show a small notification in the corner
• Alert Bar — Show a prominent slide-down alert
• Urgent — Full-screen alert with sound

Thresholds & Auto-Actions

• Alert Threshold — Minimum violation level (VL) before the panel alerts you
• Auto-Kick — Automatically kick the player at a specific VL
• Auto-Ban — Automatically ban at extreme VL levels
• Auto-Record — Automatically start a replay recording when flagged

Activity Logs provide a complete, searchable audit trail of everything that happens on the server. This is your primary investigation tool when reviewing player behavior.

Log Types

• Chat Messages — Every message sent in any chat channel
• Commands — All commands executed by players
• Punishments — Bans, mutes, warns, kicks issued
• Automod Events — Rules triggered and actions taken
• Sessions — Player join and leave events with timestamps
• Staff Actions — Config changes, revocations, watchlist modifications

Advanced Search

The search bar supports advanced syntax for precise filtering:

• player:Steve — Show only logs for a specific player
• type:chat — Filter by log type (chat, command, punishment, etc.)
• Free text search — Search across all log content
• Combine filters: player:Steve type:command

Filtering & Pagination

Use the filter panel to narrow by type, player, staff member, or date range. Choose page size (50, 100, or 200 entries per page) and use pagination controls to browse through results.

Using Logs as Evidence

When issuing a punishment, you can select specific activity log entries as evidence. These entries are snapshotted and permanently attached to the punishment case.

Staff Chat is a real-time communication channel shared between the web panel and in-game. Messages sent from the panel appear in the in-game staff chat, and vice versa.

Features

• Cross-platform — Messages sync between panel and Minecraft server in real-time
• Message History — Last 100 messages are preserved when you navigate away and come back
• Sound Notifications — Configurable alert sound when a new message arrives
• Online Staff List — See who's currently online (shown in the right column)
• Markdown Support — Use basic formatting in messages

Usage Tips

• Use staff chat to coordinate on ongoing moderation situations
• Messages from the panel show your Minecraft username as the sender
• Staff chat requires the moderex.staffchat permission

The Server Status page provides comprehensive performance monitoring with four tabs of data.

Server Health Tab

• TPS — Server ticks per second (20 = perfect, below 18 = warning, below 15 = critical)
• Memory — RAM usage with heap breakdown
• CPU — Server CPU utilization
• TPS History Graph — Visual chart showing TPS over time with color-coded zones
• World Statistics — Per-world entity counts and chunk counts

Performance Alerts Tab

Configure thresholds for automatic alerts when performance degrades. Set warning and critical levels for TPS and memory. View recent performance alerts and identify potential lag sources.

Resource Monitor Tab

Detailed breakdown of entities by type, chunk distribution across worlds, and a laggy chunks heat map showing problem areas with high entity density.

Diagnostics Tab (Spark)

If the Spark profiler plugin is installed, you can start CPU profiles, take heap dumps, and view per-plugin performance impact directly from the panel.

The Replay system records player sessions that can be reviewed later in a 3D viewer directly in the panel. This is invaluable for reviewing hacking reports, griefing incidents, and other situations where you need to see exactly what happened.

Starting a Recording

• Click Start Recording on the Replays page
• Select the players to record
• The recording captures player movement, block changes, and actions
• Recordings can also start automatically when anticheat flags a player or when a punishment is issued

3D Replay Viewer

Click any completed replay to open the 3D viewer. You'll see:

• Real Minecraft block textures and terrain
• Player models with skins and animations
• Camera controls (orbit, pan, zoom)
• Timeline scrubber with play/pause and speed controls
• Sound effects for block breaks, placements, and footsteps

Replay Settings

Configure recording limits in the Replays page settings section: max duration, storage retention days, max concurrent recordings, and auto-record triggers.

The Configuration page lets you control server-wide moderation settings. Each section requires its own permission to modify.

Chat Management

• Chat Lockdown — Completely disable chat for all non-staff players. Requires moderex.admin.chat
• Slowmode — Add a cooldown between messages (1-120 seconds). Requires moderex.admin.chat
• Clear Chat — Instantly clears chat for all players

Kick All Players

Kick every non-staff player with a custom message. Useful for maintenance. Note: kicks from this page are not recorded as punishments. Requires moderex.admin.kickall

Warning Escalation

Automatically escalate punishments based on warning point accumulation. Configure categories with point values (e.g., "Chat Offense" = 1 point, "Hacking" = 5 points) and tiers that trigger at thresholds (e.g., 3 points = 1 day mute, 10 points = 7 day ban). Requires moderex.admin.warnings

Mute Restrictions

Configure exactly what muted players are blocked from doing: chat messages, private messages, sign editing, book writing, /say and /broadcast, and voice chat. Requires moderex.admin.mutes

Server Lockdown

Prevent new players from joining while allowing existing staff to remain. Set a custom MOTD (shown on the server list) and kick message. Can auto-expire after a set time. Requires moderex.admin.lockdown

ModereX supports full message customization and multiple languages. Every message players see (ban screens, warnings, broadcasts) can be edited from the panel.

Supported Languages

• English (US) — Default
• Spanish (Espanol)
• German (Deutsch)

Editing Messages

The Messages page shows all message keys with their current values. Click any value to edit it inline. Messages support MiniMessage formatting for colors, gradients, bold, italic, and more. Changes take effect immediately on the server.

Ban Screen Preview

The right panel shows a live preview of how the ban disconnect screen appears to players. As you edit the ban.disconnect message, the preview updates in real-time so you can see exactly what players will see.

Available Placeholders

• <player> — Target player's name
• <staff> — Staff member's name
• <reason> — Punishment reason
• <duration> — Formatted duration (e.g., "7 days")
• <case_id> — Unique case identifier
• <date> — Date of the punishment
• <evidence> — Evidence summary (if attached)

ModereX uses a granular permission system to control what each staff member can see and do. Permissions are managed through LuckPerms (or any compatible plugin).

Key Permission Nodes

• moderex.webpanel — Required to access this panel. Not granted to OPs!
• moderex.* — Grants all permissions (owner/admin use only)
• moderex.ban / moderex.tempban — Permanent / temporary bans
• moderex.mute / moderex.tempmute — Permanent / temporary mutes
• moderex.warn — Issue warnings
• moderex.kick — Kick players
• moderex.unban / moderex.unmute / moderex.unwarn — Revoke punishments
• moderex.info.ip — View player IP addresses
• moderex.logs.* — View chat, command, and session history
• moderex.staffchat — Access staff chat
• moderex.admin.* — Configuration and admin features

How Permissions Affect the Panel

The panel dynamically adapts based on your permissions:

• Pages you can't access show a "No Permission" overlay explaining what's needed
• Buttons for actions you lack permission for are disabled (not hidden)
• Sensitive data (IPs, certain logs) is filtered server-side — it's never sent to clients without permission
• Permission changes take effect in real-time (15-second refresh cycle)

Permission Hierarchy

1. OP Bypass — Server OPs get all permissions except moderex.webpanel
2. Wildcard — moderex.* grants everything
3. Category Wildcard — moderex.admin.* grants all admin permissions
4. Specific Node — Fine-grained per-action control

Keyboard Shortcuts

• Ctrl+K — Open global search (search players, pages, cases)
• Esc — Close any open modal, drawer, or overlay
• Enter — Select highlighted search result
• Arrow Up/Down — Navigate search results

Power Tips

• Click stat cards — Dashboard stats are clickable links to their respective pages
• Right-click players — Context menu with quick actions
• Drag & drop evidence — Drag files directly onto the punishment modal to upload
• Click punishment badges — In the player table, click ban/mute badges to jump to that punishment
• Column sorting — Click table column headers to sort by that column
• Filter buttons — On the Punishments page, click type badges (Ban, Mute, etc.) to filter the table
• Expandable reasons — Long punishment reasons are truncated; click to expand
• Copy on click — Click UUIDs and case IDs to copy them to clipboard

Appearance Customization

Go to My Settings to customize:

• 5 Themes — Default, Apple Light, Apple Dark, Opera GX, Oldschool
• 7+ Accent Colors — Blue, Red, Orange, Green, Purple, Gold, Magenta, or custom
• 13 Background Patterns — Aurora, Waves, Stars, Grid, Circuits, Hexagons, Particles, Nebula, Matrix, Rain, Geometric, Gradient, Minimal
• Sound Effects — Toggle and adjust volume for UI sounds

DO

• Always provide a clear, specific reason when issuing punishments. "Hacking" is vague; "Using KillAura in PvP arena, flagged by Grim at VL 50+" is much better.
• Attach evidence whenever possible. Screenshots, chat logs, or anticheat data strengthen your case and help with appeals.
• Use templates for consistency. All staff should use the same reasons and durations for the same offenses.
• Check player history first. Open the player's profile before punishing. A first-time offense might warrant a warning, not a ban.
• Use the watchlist for suspicious players instead of punishing on suspicion. Monitor them and gather evidence.
• Test automod rules with the Automod Tester before enabling them. False positives frustrate legitimate players.
• Coordinate via staff chat. Let other staff know about ongoing situations to avoid double-punishing.
• Start with temporary punishments and escalate for repeat offenses. Use the warning escalation system.
• Review activity logs regularly. They often reveal patterns that individual incidents don't show.

DON'T

• Don't punish without evidence for serious offenses. "I saw them hacking" without proof won't hold up to an appeal.
• Don't share your authentication token or let others use your panel session. Each staff member should have their own access.
• Don't issue permanent bans lightly. Reserve permanent bans for extreme cases (repeated ban evasion, severe hacking). Most offenses warrant temporary punishments.
• Don't use IP bans casually. IP bans can affect innocent players on shared networks (colleges, VPNs, families). Only use for confirmed ban evaders.
• Don't modify config settings without understanding them. Server lockdown, chat lockdown, and kick-all are powerful tools. Don't enable them accidentally.
• Don't ignore the warning escalation system. If it's configured, let it handle escalation instead of manually jumping to harsh punishments.
• Don't panic-ban during raids. Use mass punishment carefully with evidence. A panicked response can catch innocent players.
• Don't leave the panel open on shared computers. Always log out or close the tab on public/shared machines.

Common Issues

In-Game Commands

Useful commands for troubleshooting:

• /mx — Main ModereX command (shows version and help)
• /mx link <token> — Link a panel authentication token
• /mx gettoken — Generate a new panel token
• /mx reload — Reload the plugin configuration
• /check <player> — Quick player info lookup
• /history <player> — View player punishment history

Getting Help

If you need further assistance, click the Discord button in the bottom-right corner to join our support server. When reporting issues, include: your ModereX version (shown on Dashboard), browser name, and any error messages from the browser console (F12 > Console tab).