The CreativeParkour plugin is no longer maintained and this website will close in 2019. Please click here for more information
Thank you for your understanding.

Custom rewards

CreativeParkour can be configured to give custom rewards to players that finish some parkour maps. Available rewards are items (enchanted if you want), XP, commands and money (if you have a Vault-compatible economy plugin, see below).
These rewards are configured in the rewards.yml file, in the <your server>/plugins/CreativeParkour folder.


Open rewards.yml and you will see these examples: example1:
  type: ITEM
  map: 2
  once: true
  amount: 1
  itemname: IRON_HELMET
  itemdata: 0
  - OXYGEN:1
  type: XP
  map: all
  once: false
  amount: 10
  type: MONEY
  map: 0,6
  once: true
  amount: 150
  cooldown: 60
  type: COMMAND
  map: all
  once: false
  command: effect @player REGENERATION 10 1
  displayname: Regeneration II for 10 seconds

The file is divided in 4 sections, 1 for each reward. You have to choose an unique name for each reward (here example1, example2, example3 and example4) and write separate sections for each reward. You can create as many sections (and rewards) as you want.
You can copy and rename these examples and change their properties to create your custom rewards (these examples are ignored by the plugin).

Reward properties

Each reward has several properties to choose what to give to players and when. Here is a list that explains these properties:

Property Value Description
type ITEM/XP/COMMAND/MONEY The type of the reward. Use ITEM to give items to players, XP to give experience, COMMAND to execute a server command or MONEY to give money with an economy plugin.
map Map IDs separated by commas or all IDs of parkour maps where you want players to get the reward when they reach the end of them. These IDs can be found with /cp getid or /cp managemaps. Write a comma-separated ID list (like in the example3 section above) or a single map ID (like in example1).
If you want to give the reward in all the maps, set this property to all.
once true/false Set true if you want to give the reward only once for each player that finishes the map(s) or false to do it each time they finish it.
amount Number For ITEM rewards: amount of items given to players (for example, write 64 to give 1 stack).
For XP rewards: number of XP points given to players (these are not levels, see the Minecraft Wiki for details).
For MONEY rewards: amount of money deposited in player's account.
cooldown Number Minutes players have to wait before obtaining the reward again. "once" must be set to false if you use this property.
itemname String Only for ITEM rewards.
Name of the item you want to give to players. Exact item names from this list must be used.
itemdata Number Optional and only for ITEM rewards.
Item data value.
itemenchants List Optional and only for ITEM rewards.
List of enchants to put on the item. Each enchant should be written like this: <enchant name>:<enchant level> (see the first example above). Exact enchant names from this list must be used. Enchant level must be between 1 and 5.
command String Only for COMMAND rewards.
Command to execute when the player claims the reward (it must be a console command, without the first /). Every @player tag in your command will be replaced by player's name.
Use COMMAND rewards with care, they can be dangerous!
displayname String Required for COMMAND rewards.
Short text displayed to players to describe the reward when they get it.
Never indent YML files with tab, only use spaces like in the example.
It is always safer to copy examples and change names and properties.

Using MONEY rewards

MONEY rewards use third-party economy plugins. They must be compatible with Vault and you have to install the Vault plugin on your server.
These plugins are compatible with MONEY rewards if you install Vault: iConomy, BOSEconomy, EssentialsEcon, 3Co, MultiCurrency, MineConomy, eWallet, EconXP, CurrencyCore, CraftConomy, AEco, Gringotts.

You can customize the way CreativeParkour displays money amounts with the currency option in configuration.yml.