Configuration
Every option in config.yml — database connection, dev token, metrics and effects.
Where to find the file
Open your server's file manager, go to ~/plugins/ParkourProject/, and open config.yml. This
file holds core plugin settings. Movement tuning lives in moves.yml and style bonuses live in
bonuses.yml — both covered under Reference.
Full default config.yml
database:
table:
prefix: parkour_project
username: root
password: password
early-bird: false
dev-token: none
allow-metrics: true
external-effects: trueDatabase
Parkour Project persists player data — such as which moves are unlocked and which cooldown UIs are enabled — in an SQL database. It ships with an embedded database so it works with zero setup; these settings control the connection.
| Option | Default | Description |
|---|---|---|
database.table.prefix | parkour_project | Prefix applied to every table the plugin creates. Change this if multiple plugins or instances share one database. |
database.username | root | Username for the database connection. |
database.password | password | Password for the database connection. |
The plugin does not currently support external databases
Plugin behavior
| Option | Default | Description |
|---|---|---|
early-bird | false | Opts into early access to feature-flagged functionality before it is generally rolled out — notably the addon API. Leave false for normal play. |
dev-token | none | Developer token for development builds / privileged features. Keep none for normal use. |
allow-metrics | true | Sends anonymous usage statistics that help improve the plugin. Set to false to opt out. |
external-effects | true | Allows Parkour Project to apply external effects tied to movement and flow (e.g. potion / visual / audio feedback). Set to false for purely mechanical movement. |
Applying changes
After editing any config file you can reload without a full restart:
/parkour reloadThis re-reads config.yml, moves.yml and bonuses.yml. See
Commands & Permissions for details.
Not everything reloads
A reload does not re-apply every value. Database-connection settings need a full restart, and
so do some move and bonus settings — including all the max_streak_time values. If a change
doesn't seem to take effect, restart the server.