PermissionProbe Guide

This page introduces PermissionProbe as a public testing guide. It focuses on what the tool checks, how testers get started, and which commands are useful on an authorized test server.

What It Does

Owner-only read-only permission diagnosis, passive denial recording, watch summaries, scoped reports, Markdown exports, command explainers, feature/player access summaries, player/group comparisons, context-aware server group source traces, expected-profile checks, wildcard/orphan scans, and…

How Testers Use It

Use this page as a public testing guide to PermissionProbe. It explains what the tool checks and how it supports development or compatibility testing.

Available features include:

• Read-only effective permission checks for online and cached offline players.
• LuckPerms source traces for exact, wildcard, user, group, inherited, temporary, and context-tagged nodes.
• Feature, player, group, command, and context access summaries.
• Player-to-player and group-to-group permission comparisons.
• Expected-profile checks plus broad wildcard and orphan-node scans.
• Passive denied-check recording and temporary live watch windows.
• GitHub-table and Discord-friendly Markdown exports for each diagnostic view.
• Strict owner-only access without changing permissions or player data.

Quick Start

1. Review the available checks above and confirm the tool belongs on the authorized test server.
2. Open the full reference for exact tester commands, permissions, output, and safety notes.

Commands

No public tester commands are listed for this plugin yet.

Examples

• Open the full reference below for exact permission-gated commands and examples.

Good To Know

• This is a permission-gated testing or development tool, not a normal player feature.
• Use it only on an authorized server and review the full reference before running diagnostics or exports.

Full Reference

The full synced PermissionProbe reference is available for exact technical details.