Configuration¶

For: intermediate admins. Start at Settings.

The plugin creates config.yml in its data folder. You can find it in plugins/JManhunt/config.yml.

See the individual configuration pages for detailed documentation:

Sections¶

• Settings: match start and end, compass, roles, win conditions, and game boosts.
• World Engine: grid-based world engine setup, cell pre-generation commands, world border, and troubleshooting.
• Modifiers: named command bundles, behaviors, and the JMHScript tag reference.
• Game Rules: built-in game-state actions applied at match start and end.
• Statistics: career statistics database and placeholder configuration.
• Sounds: sound configuration for game events.

What Settings Cover¶

Settings modify the game flow. This includes things like:

• autostart when enough players join
• starting the game only when a speedrunner hits a hunter
• adventure mode during the pre-start window
• compass tracking rules and distances
• friendly fire rules for hunters and speedrunners
• delayed respawns and per-role lives
• head starts for either side
• alternate win conditions (exit End, survive time, acquire item, reach advancement)
• custom bartering loot tables for higher ender pearl pulls

The built-in challenges (no-jump, one-heart and lucky-blocks) come from the companion plugin JManhunt-Challenges.

Core Settings¶

Messages in messages.yml use MiniMessage formatting. Classic & color codes (like &7 or &6) still work anywhere: they convert automatically. Placeholder formatting in config.yml follows the same rules. Changes apply after /manhunt reload.

Set any message in messages.yml to an empty string ("") to disable it: it will never be sent. (A single space still counts as a message.) Each role's color lives under role-colors: as one key per role, used by role headers and every message that names a role; & codes work there too. The top-level error-color: key recolors every engine error line at once, including the <perror>, <gerror>, and <rerror> behavior tags. Built-in error templates use the {error-color} placeholder, so they follow the key.

Update Checker¶

JManhunt compares the running version against the latest GitHub release (never a pre-release) and tells admins when an update is out. The check runs once, shortly after the plugin enables; admins who join later hear about a pending update when they log in. Only players holding jmanhunt.admin (default: op) see the notice.

update-checker:
  enabled: true
  releases:
    major: true
    minor: true
    hotfix: false

Each severity toggles separately: with the defaults, new major and minor releases notify while hotfixes stay silent. Failed checks (no network, GitHub down) log one warning and never affect startup.

Upgrading¶

Settings paths were regrouped for consistency: match settings gained start, headstart, gameplay, and leaving groups; compass signal options moved under holder, target, terrain, climate, and policy groups; players settings gained identity and combat groups; server announcements moved under announce; the file version plus anonymous-statistics toggle moved under advanced.plugin; match end settings moved under finish; lobbies gained general, join, and bounds groups; and world-engine settings gained general, search, scripts, style, and wave groups. Old paths are dropped: affected values reset to fresh defaults, and startup logs a warning naming the stale blocks. Re-apply your tweaks under the new paths after upgrading; each settings page shows the current layout.

Anonymous Statistics¶

JManhunt collects anonymous usage statistics through bStats, which helps guide development. This is enabled by default and can only be changed directly in config.yml.

advanced:
  plugin:
    send-anonymous-statistics: true

Set it to false and restart the server to opt out.