McProgression documentation

McProgression adds configurable skills, General XP, ranks, rewards, and progression based item and world rules to Paper servers.

Built by Origami.Vision for the Dardroo community.

Start with the server admin guide to install the plugin, choose a preset, and review the main configuration files. The files shipped in src/main/resources/ are the source of truth for current defaults.

Set up your server

• Server admin guide — first setup, presets, configuration files, and common changes.
• Configuration and compatibility — configuration contracts, audit behavior, and supported versions.
• Commands and permissions — player commands, staff roles, and LuckPerms examples.
• Performance and scaling — persistence, notification volume, and staged capacity checks.
• Publish the documentation site — Cloudflare Pages setup and local preview instructions.

Configure progression

• General XP — advancement, daily join and streak rewards, active play, and rank conversion.
• Progression rewards — rewards for Global Rank tiers and per-skill rank subtiers.
• Death penalties — PvE/PvP categories, XP-loss modes, and defaults.
• Agility discovery and jump XP — exploration and movement settings.
• Player display preferences — player controls for XP feedback and notices.

Operate and troubleshoot

• Progression storage — YAML/SQL setup, legacy import, backups, and database limits.
• Discord webhooks — XP, level, rank, and moderator event notifications.
• Moderator progression controls — resets, statistics sync, and history-import limits.
• Display integrations — PlaceholderAPI, TAB, LuckPerms prefixes, and troubleshooting.
• Translations — locale selection and message catalog maintenance.

Technical references

• Item action coverage — event adapters, policy matrix, and known enforcement boundaries.
• Actorless automation policy — furnace, Crafter, inventory transfer, brewing, and dispenser rules.
• Local server playtest guide — development server setup and manual checks.

Older planning and deliberation records under .ai/plans/ are historical references, not current setup instructions or implementation guarantees.