OmniPanel

OmniPanel is an all-in-one administration, moderation, player-management, and server-utility plugin built for modern Minecraft servers.

Instead of stacking separate plugins for staff tools, punishments, ranks, homes, kits, regions, player inspection, maintenance, events, authentication, and server management, OmniPanel connects those systems through one central platform.

The plugin is designed around menus, dialogs, shared permission checks, and consistent workflows rather than forcing staff to remember dozens of commands.

Whether you're running an SMP, community server, creator server, private server, or larger network, OmniPanel gives your staff one place to manage the server.

---

Why OmniPanel?

A normal server can quickly end up running separate plugins for:

• Moderation
• Punishments
• Staff Mode
• Player inspection
• Ranks
• Homes
• Kits
• Regions
• Events
• Authentication
• Maintenance
• Discord integration
• Player utilities
• Administrative tools

That usually means separate permission systems, different interfaces, overlapping commands, duplicate data, and plugins that do not know about each other.

OmniPanel is built differently.

One panel.

One connected permission system.

One moderation workflow.

One set of player-management tools.

One API for other plugins to integrate with.

---

Main Panel

Everything starts with:

/panel

The panel provides access to OmniPanel's administrative systems through a permission-aware interface.

Features include:

• Section-based navigation
• Feature-level permissions
• Search
• Pagination
• Context-aware menus
• Player selection
• Confirmation screens
• Paper Dialog integration
• Permission-aware buttons
• Staff-only actions
• Public-player menus where appropriate
• Back and Close navigation
• Extension support for add-ons

Opening /panel does not automatically give access to everything inside it.

Every protected feature is still checked server-side.

---

Panel Visibility & Access

OmniPanel uses a centralized access system for protected panel features.

Administrators can grant access to:

• Entire sections
• Individual features
• Specific staff members
• Specific ranks

This makes it possible to give staff exactly what they need.

For example:

• Helpers can inspect players without editing inventories.
• Moderators can freeze, jail, teleport, and moderate players without receiving rank-management access.
• Builders can receive region and building controls without punishment permissions.
• Developers can receive diagnostics and technical tools.
• Owners can retain complete access.

The built-in Panel Visibility & Access editor allows authorized staff to:

• Select a player or rank
• Choose full or custom access
• Browse sections
• Enable or disable individual features
• Review changes before applying them
• Grant or revoke complete sections

LuckPerms integration remains authoritative where available.

Explicit permission grants, denials, contexts, and external LuckPerms changes are respected.

---

Player Browser

Browse players through OmniPanel without needing to type usernames manually.

Player information can include:

• Online status
• Platform
• Rank
• Last seen
• Current world
• Playtime
• Homes
• Punishment history
• Staff notes
• Presence state

Player Actions provide access to additional tools depending on staff permissions.

---

Player Actions

Player Actions are organized into categories such as:

• Care & Movement
• Moderation & Records
• Utilities
• Advanced
• Additional Player Tools

Available actions depend on the staff member's permissions.

Integrated tools include:

• Teleportation
• Healing
• Inventory inspection
• Ender Storage inspection
• Punishment history
• Staff notes
• Freeze
• Jail
• Moderation tools
• Utility actions

Target actions remain bound to the selected player rather than silently falling back to the staff member.

---

Inventory Inspection

OmniPanel includes shared inventory-inspection sessions for staff.

Example:

/invsee inventory <player>

Viewing and editing are separate permissions.

The inventory system supports:

• Read-only inspection
• Authorized editing
• Storage slots
• Armour
• Offhand
• Concurrent-session protection
• Inventory transaction guards
• Offline player inspection
• Offline editing backups
• Login protection while an offline edit is active

Read-only sessions cannot write changes back to the target player.

Real player items are treated as items, not as GUI buttons.

---

Expanded Ender Storage

OmniPanel includes an expanded Ender Storage system backed by its existing storage database.

Features include:

• 54 usable chest slots
• Staff inspection
• Personal /echest access where permitted
• SQLite persistence
• Backups
• Legacy-data imports
• Vanilla synchronization
• Physical opening and closing sounds
• Lid animation
• Shared-viewer handling
• Corruption safeguards

Invalid stored item data fails closed instead of silently replacing stored items with empty slots.

---

Punishment System

OmniPanel includes a full punishment workflow for staff moderation.

Supported actions include:

• Warnings
• Temporary warnings
• Mutes
• Temporary mutes
• Bans
• Temporary bans
• IP bans
• Temporary IP bans
• Kicks
• Freeze
• Jail
• Reversals
• Staff notes
• Punishment records

Temporary punishments require valid finite durations and respect configured limits.

Punishments use the authoritative backend so GUI actions, API submissions, records, and enforcement stay connected.

---

Punishment Records

Punishment history can include:

• Staff actor
• Target
• Case
• Source
• Action
• Reason
• Duration
• Timestamp
• Result
• Available evidence

History uses compact summaries with full details available through the existing record interface.

Warnings, kicks, reversals, and expired temporary punishments are not incorrectly shown as permanent active sanctions.

---

Punishment Presets

OmniPanel includes searchable punishment presets for reviewed moderation situations such as:

• Fraud
• Phishing
• Malicious links
• Evasion
• Bot raids
• Exploits
• Harassment
• Spam

Custom server presets remain supported and remain authoritative.

Normal Minecraft behaviour such as legitimate trading, giveaways, or regular PvP is not automatically treated as a violation.

---

Duration Builder

Temporary punishments support normal duration units including:

• Seconds
• Minutes
• Hours
• Days
• Weeks
• Months
• Years

Duration validation is handled before temporary punishments are applied.

---

AutoMod

OmniPanel includes built-in chat moderation and evidence handling.

Features include:

• Blocked-word detection
• Strict-word lists
• Word-boundary matching
• Current-message evidence
• Spam detection
• Moderation alerts
• Configurable confidence requirements
• Saved evidence
• Staff review flows
• Atomic word-list updates

Commands include:

/automod words add
/automod words remove
/automod words list

and:

/automod strictwords add
/automod strictwords remove
/automod strictwords list

Blocked-word checks use the actual current message rather than stale content from previous messages.

---

AI Moderation Evidence

Where AI-assisted moderation is configured, OmniPanel treats AI output as evidence for review rather than automatic truth.

The moderation context accounts for normal Minecraft activity including:

• PvP
• Trading
• Economy activity

Automatic decisions require:

• A recognized category
• Evidence from the real message
• A verbatim matching quote
• Contextual support
• The configured confidence threshold

The default evidence confidence threshold is:

0.95

High-impact or uncertain cases remain review-oriented by default.

Evidence records can contain:

• Original message
• Matching quote
• SHA-256
• Capture time
• Source
• Model confidence where available

AI confidence is a safeguard, not proof.

---

Staff Mode

OmniPanel includes a built-in Staff Mode with safe inventory recovery.

Features include:

• Staff inventory backup
• Staff tools
• Vanish support
• Join/quit recovery
• Inventory restoration
• Flight-state restoration
• Collision restoration
• Pickup-state restoration
• Protection-state restoration
• Recovery after disconnect or shutdown
• Persistent tool identifiers
• Protected tool movement
• Staff Mode title
• On-duty action bar

Entering Staff Mode fails safely if the staff inventory cannot be backed up.

---

Staff Tools

Available administrative tools include:

• Sentinel Blade
• Excavator Pickaxe
• Timber Axe
• Justice Hammer

Tools can be granted individually instead of requiring access to every administrative tool.

Punishment-related tools still require the corresponding punishment permissions.

Issuing a staff tool does not overwrite occupied inventory slots.

---

Staff Chat

Staff Chat uses the same access system for:

• Toggling
• Sending
• Receiving
• Visibility
• Execution

Default and Member players do not receive Staff Chat automatically.

Staff messages are routed before normal public chat auditing or Discord forwarding.

If access is revoked before a pending Staff Chat message is sent, the message is cancelled instead of leaking into public chat.

---

Emergency Staff Teleport

OmniPanel includes:

/stafftp [message]

This allows authorized staff to send a private emergency teleport invitation.

Staff can respond using:

• Clickable Accept
• Clickable Deny
• /stafftp accept
• /stafftp deny
• /tpaccept
• /tpdeny

Emergency staff teleport requests always require explicit acceptance, even if normal TPA auto-accept is enabled.

Requests are session-bound, expire properly, and cannot be reused after reconnecting.

---

Public Teleport Requests

Normal player teleport commands remain public:

/tpa
/tpahere
/tpaccept
/tpdeny
/tpcancel
/tpauto

Players can configure:

• Whether they receive teleport requests
• Whether normal requests auto-accept

Emergency staff requests remain separate from normal auto-accept behaviour.

---

Homes

OmniPanel includes a public homes system.

Commands include:

/home
/homes
/sethome
/delhome
/unsethome

Features include:

• Named homes
• Teleportation
• GUI access
• Safe deletion
• Region checks
• Atomic persistence
• Rank-based home limits
• Alias-aware rank handling

When multiple active ranks are present, OmniPanel uses the highest applicable home allowance instead of adding allowances together.

Default Home Limits

Rank	Homes
Default	2
Member, Helper	3
VIP, Moderator	4
MVP, YouTuber, Builder, Admin	5
Hero, Developer, Manager	6
Champion, Legendary, Executive, CEO, Co-Owner, Owner	7

Existing custom limits remain supported.

---

Random Teleport

/rtp remains available as a normal player command.

Default cooldown:

60 seconds

Existing explicitly configured cooldowns are preserved.

Available destinations include:

• Overworld
• Nether
• End
• Close

Administrative RTP controls include:

• Cooldown
• Countdown
• Target worlds
• Search radius
• Attempts
• World-border handling
• Safety filters
• Protected-region buffer
• No-RTP zones
• Cooldown clearing
• Testing

The cooldown starts only after a successful teleport.

---

Personal Settings

Players can open:

/settings

The personal settings menu is separate from OmniPanel's administrative settings.

Available options include:

• Receive TPA requests
• TPA auto-accept
• Player visibility
• Collision
• Item pickup
• Personal time
• Personal weather
• Settings sounds
• Hostile natural-spawn preference
• Peaceful natural-spawn preference
• Stack My Items
• My Coordinates
• Clear My Inventory
• Reset

Personal time and weather only affect the player's view and do not alter the world's global state.

---

Safer Inventory Clearing

Inventory clearing requires a protected confirmation.

The confirmation is tied to:

• Player
• Target
• Inventory state
• Session

The following cannot accidentally confirm a clear:

• Escape
• Cancel
• Shift-click
• Double-click
• Number keys
• Drop clicks
• Bottom-inventory clicks
• Replayed confirmations
• Expired confirmations

If the inventory changes before confirmation, the old request becomes invalid.

---

Personal Mob-Spawn Preferences

Players can control nearby natural hostile and peaceful mob spawning around themselves.

The system is local to the opted-out player and configurable by radius.

It does not:

• Change a global gamerule
• Delete existing mobs
• Affect spawners
• Affect spawn eggs
• Affect breeding
• Affect command-spawned mobs
• Create separate client-only mobs

Nearby players who allow spawning take priority in shared areas.

---

Rank Manager

OmniPanel includes deep LuckPerms integration for rank management.

Features include:

• Main-rank assignment
• Additional ranks
• Promotions
• Temporary ranks
• Permanent ranks
• Duration selection
• Rank display
• TAB synchronization
• Chat synchronization
• Name-tag synchronization
• Rank aliases
• Offline assignments
• Serialized rank writes
• Failure rollback

Normal rank assignment replaces the player's previous main rank.

Additional ranks are managed separately through Multi Ranks.

Unrelated groups and direct player permissions are preserved.

---

Apply Rank to Everyone

Authorized staff can bulk-apply a selected rank.

The flow allows staff to choose:

• Online players only
• All known players

Before applying, OmniPanel displays the operation count and requires confirmation.

Protected and owner-level accounts are skipped.

Permission:

omnipanel.access.ranks.apply-to-everyone

---

Rank Badges

OmniPanel includes a generated rank-resource-pack contribution containing custom rank badges.

Current rank badges include:

• Owner
• Co-Owner
• CEO
• Executive
• Manager
• Admin
• Builder
• Developer
• Moderator
• Helper
• MVP
• VIP
• YouTuber
• Hero
• Champion
• Legendary
• Member
• Default

Presence badges are also included for:

• LIVE
• AFK

The badges use the dedicated font:

omnipanel:ranks

The normal Minecraft font is not replaced.

Text fallback remains available when the resource pack is not accepted.

---

ResourcePackManager Integration

OmniPanel contributes its generated rank assets to the existing ResourcePackManager workflow.

ResourcePackManager remains responsible for:

• Combining packs
• Hosting
• Prompting players
• Delivering the final pack

OmniPanel does not compete with ResourcePackManager by sending another standalone pack.

If using the badge system, keep your normal combined ResourcePackManager setup configured.

---

Name & Chat Styles

OmniPanel includes configurable name and chat styling.

The current style collection contains:

468 selectable styles across 13 pages.

Included collections include:

• Smooth Signatures
• Silk Motion

Existing profile IDs and saved player selections remain compatible.

Supported settings include:

• Animation enablement
• Speed
• Frame timing

Name, chat, and TAB styling share the same renderer.

Minecraft team colours still use Minecraft's native 16-colour limit where required, while compatible component displays can retain richer RGB and gradient styling.

---

AFK & Presence

OmniPanel includes an AFK and presence system integrated with rank display.

AFK protection resists passive movement such as:

• Water
• Wind charges
• Knockback
• Ordinary velocity
• Player collision
• Mob collision

AFK is cleared by actual player movement, /afk, or successful teleportation.

Camera movement alone does not count as returning.

Mounted players are dismounted when entering AFK, and AFK players cannot be mounted.

AFK movement protection does not provide damage immunity.

---

Kits

OmniPanel includes a GUI-driven kit system.

Kit features include:

• Creation and editing
• Cooldowns
• Permissions
• Preview
• Search
• Categories
• Safe item delivery
• Overflow handling
• Rollback on failed transactions
• Playtime rewards

Kit claims preserve existing inventory contents and merge compatible stacks where possible.

A partially filled inventory is not automatically treated as full.

---

Playtime Kit Rewards

Kits can optionally reward players after reaching configured playtime thresholds.

Configure through Manage Kit or:

/kit playtime <kit> <minutes|off>

Rewards are stored per UUID and kit threshold.

Cooldown resets do not cause the same playtime reward to be granted again.

The Kit API exposes:

playtimeMinutes

---

Donor Utilities

VIP, MVP, Hero, Champion, and Legendary can receive default access to utilities such as:

/echest
/craft
/anvil

Each utility has its own:

• Permission
• Configuration switch

Existing explicit grants and denials remain authoritative.

/echest uses OmniPanel's existing expanded Ender Storage rather than creating a second storage backend.

---

Region Protection

OmniPanel includes its own native region system.

Regions can control server behaviour such as:

• Building
• Breaking
• Interaction
• PvP
• Water
• Lava
• Buckets
• Protected boundaries
• Region ownership
• Staff bypass
• Event usage

WorldEdit and FAWE selections can be used to create or resize OmniPanel regions.

Selections must be complete and belong to loaded worlds.

Changes respect configured volume limits.

Failed region writes roll back automatically.

---

WorldEdit Selection Integration

Authorized integrations can use a player's WorldEdit selection for native OmniPanel region operations.

A WorldEdit selection by itself does not provide OmniPanel protection.

The selection must first be saved as an OmniPanel region.

---

Server Rules

OmniPanel includes an editable Rules Studio.

Authorized staff can:

• Add rules
• Edit rules
• Delete rules
• Reorder rules

Configurable options include:

• Title
• Introduction
• Page size

An empty rules list can still be edited.

---

Maintenance Mode

Maintenance controls are available through OmniPanel Settings.

Features include:

• Enable/disable
• Custom text
• Placeholders
• Escaped newlines
• Fallback controls

Editing maintenance text does not automatically enable maintenance mode.

---

Jail

OmniPanel's jail system can control:

• Commands
• Chat
• Building
• Interaction
• Items
• PvP

Jail configuration access is separate from the ability to jail a player.

Allowed-command lists are synchronized across jail guards, including intentionally empty lists.

Jail notices retain the recorded jailer and punishment duration.

---

Watch & Notify

Authorized staff can use the existing watch service to monitor selected player activity and receive notifications.

Watch access and notification access remain separately permission-controlled.

---

Owner Log

Owner Log records important administrative and moderation activity.

Records can include:

• Actor
• Target
• Case
• Action
• Reason
• Duration
• Source
• Result

Categories include:

• Punishments
• Commands
• Game-mode changes

Game-mode changes are recorded separately from submitted commands.

Credential-related commands are excluded from command logging.

Features include:

• Filtering
• Pagination
• Refresh
• Detailed records
• Live punishment alerts
• Selected-command tracking
• Game-mode tracking

Disabling recording keeps existing records and does not disable security enforcement.

---

Owner Command Approval

Individual commands can optionally require owner approval.

Owners can:

• Approve once
• Deny

Approval only allows one retry of the exact command under the same session and world conditions.

Approval does not:

• Run the command as console
• Grant missing permissions
• Bypass rank checks
• Bypass world restrictions
• Bypass argument validation

Requests expire and cannot be reused with changed arguments.

---

Command Hub

Command Hub provides a central view of registered server commands.

Features include:

• Command browsing
• Search
• Aliases
• Plugin/provider grouping
• Descriptions
• Usage
• Permissions
• Rank access
• State
• Activity/history

Group operations include:

• Enable All
• Disable All
• Show All
• Hide All
• Reset Group Rules

Public gameplay and recovery commands are protected from inappropriate Command Hub restrictions.

---

Java & Bedrock Support

OmniPanel supports mixed Java and Bedrock environments.

Supported integrations include:

• Geyser
• Floodgate

Features include:

• Platform-aware player handling
• Bedrock punishment support
• Real online UUID handling
• Bedrock-aware authentication
• Bedrock account recovery
• Prefix-preserving identities

Bedrock players keep their actual online UUID rather than receiving an invented offline UUID.

---

Authentication & Recovery

OmniPanel includes account authentication and trusted-console recovery.

Recovery commands:

forcelogin <player-or-known-UUID> [--reset]
forceregister <player-name-or-known-UUID> [--replace]

Recovery supports:

• Online players
• Known offline accounts
• UUID lookup
• Bedrock prefix handling
• Offline account creation
• Credential replacement
• Save-before-unlock behaviour
• Recovery-session consumption
• Re-registration flows

Existing credentials require --replace before they are overwritten.

Credentials are saved before the session unlocks.

Only salted password hashes are stored.

Recovery remains restricted to trusted console usage according to server configuration.

---

DiscordSRV Integration

OmniPanel integrates with the server's existing DiscordSRV installation.

It does not create another independent Discord bot system.

Features include:

• Multiple guild/channel destinations
• Public routes
• Private audit routes
• Staff routes
• Punishment routes
• Permission checking
• Queue handling
• Delivery-error logging
• Route testing
• Destination deduplication

Private routes do not silently fall back to public Discord channels.

---

Discord Account Linking

Supported commands include:

/linkdiscord
/unlinkdiscord

with:

discordlink

remaining available as an alias.

Where supported, OmniPanel uses DiscordSRV's existing AccountLinkManager.

This allows OmniPanel to reuse DiscordSRV for:

• Link codes
• Link status
• Unlinking
• Reverse lookup
• Role-sync identity

OmniPanel does not create a second competing link-code database when native DiscordSRV linking is available.

---

Welcome Messages

OmniPanel supports configurable welcome messages based on location.

Features include:

• World-based welcomes
• Region-based welcomes
• Rich colours
• Styled player names
• PlaceholderAPI replacements
• Cooldowns
• Authentication-aware delayed messages
• Component action bars

Repeated greetings can be suppressed for the same destination without preventing a different region or world from showing its own welcome.

---

Event System

OmniPanel retains its existing event framework for configured server events.

The system supports:

• Event templates
• Locations
• Timers
• Rewards
• Roles
• Toggles
• Staff controls
• Confirmation flows
• Event state
• Safe shutdown handling

Existing event templates and configured event data remain supported.

---

Public Commands

The following gameplay commands remain public by default and do not require panel access:

/rtp
/home
/homes
/sethome
/delhome
/unsethome
/tpa
/tpahere
/tpaccept
/tpdeny
/tpcancel
/tpauto
/settings

Normal gameplay restrictions such as cooldowns, home limits, protection rules, and server configuration still apply.

---

Developer API

OmniPanel includes a public developer API for plugins that need to integrate with OmniPanel without accessing internal implementation classes.

Current API Versions

Developer API: 4.8.0

Permission Service API: 5.0.0

The API extends OmniPanel's existing systems instead of creating duplicate backends.

An add-on can work with the same:

• Punishment backend
• Rank backend
• Region backend
• Kit backend
• Permission system
• Player Actions
• Presence system
• Event system

used by OmniPanel itself.

---

Available API Surfaces

OmniPanel provides several integration surfaces.

OmniPanelService

Used for service-based add-on integration.

Capabilities include:

• Add-on registration
• Readiness checks
• Capability discovery
• Status
• Heartbeat
• Disconnect handlers
• Menu access
• Extension registration

OmniPanelDeveloperAPI

Provides authenticated/keyed integration helpers.

OmniPanelAPI

Provides access to existing runtime functionality including punishment integration.

OmniPanelRuntimeAPI

Provides runtime-facing integration methods.

---

Region API

Available or expanded region helpers include:

getWorldEditSelectionSnapshot(key, player)
createNativeRegionFromSelection(key, player, name, lobby)
resizeNativeRegionFromSelection(key, player, regionId)
deleteNativeRegion(key, player, regionId)
getNativeRegionIds(key, world)
checkBuildAccess(key, player, location, action)
getPlayerNameStyleSnapshot(key, player)
refreshPlayerNameStyle(key, player)

The service also provides:

checkBuildAccessAsync(...)

Build-access queries use the same rules as actual gameplay, including:

• Regions
• Worlds
• Bypass permissions
• Jail restrictions
• Place checks
• Break checks
• Interaction checks

Async build-access checks capture the location and schedule the authoritative check on the server thread.

---

Extension API

Add-ons can integrate with existing OmniPanel systems including:

• Panel buttons
• Panel sections
• Callback handlers
• Namespaced registration cleanup
• Registration-result details
• Custom Player Actions
• Region providers
• Region flags
• External region details
• Supported region mutations
• Rank permission contributions
• Rank hierarchy snapshots
• Rank weight snapshots
• Player permission snapshots
• Permission refresh requests
• Rank synchronization diagnostics
• AutoMod diagnostics
• Authentication diagnostics
• Player presence
• AFK state
• LIVE state
• Kit readiness
• Kit metadata
• Kit previews
• Kit claims
• Event readiness
• Event templates
• Active event IDs
• Placeholder resolution
• Permission queries

Existing API signatures remain available where compatibility is required.

---

Punishment API

Add-ons can open OmniPanel's punishment interface:

OmniPanelAPI.openPunishmentTarget(
    staff,
    "Target",
    "tempipban"
);

Opening the interface does not apply the punishment until the normal OmniPanel confirmation is completed.

Add-ons can also submit directly through the authoritative punishment backend:

OmniPanelAPI.submitPunishment(
    staff,
    "Target",
    "tempipban",
    "1d",
    "Verified network ban evasion; staff reviewed evidence",
    "my_plugin"
).thenAccept(result -> {
    // Inspect the result status and authoritative applied value.
});

Authorized history can be read with:

var records =
        OmniPanelAPI.getPunishmentHistory(
                staff,
                "Target",
                20
        );

Possible submission statuses include:

APPLIED
REJECTED
DENIED
INVALID_INPUT
INVALID_DURATION
OWNER_APPROVAL_REQUIRED
UNAVAILABLE
FAILED

The returned applied value is authoritative.

A completed future does not automatically mean that a punishment succeeded.

---

Punishment API Safety

Direct punishment submission intentionally does not display OmniPanel's normal confirmation interface.

The calling add-on is responsible for its own confirmation and evidence-review process.

OmniPanel still enforces:

• Staff authorization
• Player session validity
• Owner protection
• Duration limits
• Command-approval policy
• Queue validity

Cancelled, expired, or already-completed queued work is skipped.

Punishment history is bounded and does not expose stored IP addresses.

Keyed API methods validate the API key as well as the acting player's authorization.

---

API Security

An OmniPanel API key does not:

• Grant staff permissions
• Impersonate console
• Bypass action permissions
• Bypass region permissions

Region mutations still require the acting player to have the appropriate permission.

Server-state and UI operations must follow the documented server-thread requirements.

Snapshots are immutable where documented.

Invalid or disabled keys fail without granting access.

The service API uses compatibility-friendly default methods where appropriate so existing implementations are not broken unnecessarily.

---

PlaceholderAPI

OmniPanel supports PlaceholderAPI integration.

Available placeholders depend on the installed version and enabled systems.

Typical OmniPanel information includes:

• Rank
• Prefix
• Suffix
• Online state
• Staff state
• Ping
• World
• Homes
• Warnings
• Mute state
• Freeze state
• Playtime

This allows OmniPanel information to be used by compatible:

• TAB plugins
• Scoreboards
• Chat systems
• Holograms
• Other PlaceholderAPI consumers

---

Permissions

OmniPanel is permission-driven.

Examples include:

omnipanel.use
omnipanel.panel
omnipanel.playerbrowser
omnipanel.playeractions
omnipanel.punish
omnipanel.warn
omnipanel.mute
omnipanel.ban
omnipanel.events
omnipanel.kits
omnipanel.regions
omnipanel.ranks
omnipanel.staff
omnipanel.stafftp
omnipanel.admin
omnipanel.owner

Feature-level permissions are also used throughout Panel Visibility & Access.

Explicit LuckPerms grants and denials remain authoritative.

---

Optional Integrations

OmniPanel can integrate with:

• LuckPerms
• PlaceholderAPI
• Vault
• WorldEdit
• FAWE
• DiscordSRV
• Geyser
• Floodgate
• TAB
• Multiverse-Core
• ResourcePackManager

Support depends on the feature being used and the versions installed on the server.

---

Compatibility

OmniPanel's current build system targets modern Minecraft server software.

Current build coverage includes:

• Paper 1.21.11 baseline API compilation
• Paper 26.2 profile
• Paper 26.3 profile
• Supported Spigot fallback paths
• Purpur-compatible Paper API paths

Native Paper Dialog functionality is used where available.

Spigot does not provide Paper's native Dialog API, so supported fallback interfaces are used where possible.

Production bytecode remains:

Java release 21
Class version 65

The build process uses a newer JDK where required to read newer Paper APIs.

Run the Java version required by the Minecraft server software you deploy.

---

Build Quality

The current OmniPanel source has been reconstructed into a repeatable build instead of relying on post-build binary patching.

The production JAR is compiled directly from source.

Production releases do not bundle:

• Test fixtures
• Mock classes
• Recovery probes
• Server API dependencies

Current 18.9.114 verification includes:

• 0 Java compilation errors
• 368 JUnit tests passing
• 26 helper regression checks passing
• 465 production classes passing JVM verification
• Clean extracted source rebuilding into a byte-identical JAR
• Paper 26.2 targeted regression suite passing
• Paper 26.3 targeted regression suite passing
• Shared Spigot API linkage checks passing
• Descriptor and YAML validation
• CRC validation
• JAR integrity checks
• Duplicate class/resource checks
• Test/stub leakage checks

These checks do not replace real live-server testing.

Resource packs, Discord delivery, Java/Bedrock behaviour, AI responses, plugin combinations, inventories, and gameplay integrations should still be verified on the actual server configuration being used.

---

Installation

1. Download OmniPanel.
2. Place the JAR inside your server's plugins folder.
3. Install any optional integrations your server uses.
4. Start or fully restart the server.
5. Configure staff permissions.
6. Open:

/panel

Do not use hot reloads when updating OmniPanel.

Back up your existing:

• Configuration
• Player data
• Databases
• Resource-pack configuration

before installing a major update.

---

Built For

OmniPanel can be used on:

• Survival servers
• SMPs
• Community servers
• Creator servers
• Event servers
• Roleplay servers
• Private communities
• Staff-heavy servers
• Growing networks

---

OmniPanel

OmniPanel is built around one idea:

Server administration should feel like one connected system, not a pile of unrelated plugins.

Moderation, ranks, player tools, permissions, homes, kits, regions, staff utilities, Discord integration, authentication, and developer integrations all work through the same platform while remaining permission-controlled and extensible.

If you want one place to run and manage the operational side of a modern Minecraft server, that is what OmniPanel is built for.