CommandMineRewards

When a player breaks a block, if the block broken is found in a list defined in the configuration file, it will run through each reward. The rewards work in the way that if a random number falls in a certain percentage, then a list of commands will be run.
- Unlimited rewards: You may define as many rewards in the config as you want, and you may name them whatever you like, as of version 1.2. You can also define multiple reward sections so you can have multiple block lists.
- The Multiplier: The Multiplier, either a whole number or a decimal number, multiplies the chance of getting each reward by its value. For example, if the config said that a player has a 25% chance of getting $300, and the multiplier is 3, then the player will have a 75% chance of getting $300, or if the config gives the player a 50% chance of getting $50, but the multiplier is set to 0.1, then the player has a 5% chance of getting $50. The multiplier is set by default to 1, so the chances of getting rewards are not affected. Please don't set this to 0 to disable it!! Instead of disabling the multiplier, it will disable all rewards because all chances will be multiplied by 0, meaning everything has a 0% chance of a reward! Simply set it to 1 to disable it.
- Player name placeholder: Anytime "%player%" is found in a command to run, it will replace "%player%" with the name of the player that broke the block.
- In-game setup: Most options in the configuration can be modified in-game, no configuration editing required! You can choose command-style or GUI-style!


Here's how to get started with CMR:
1. In-game, run /cmr gui to open the CMR GUI configuration menu. Here you can see each reward "group" and some global settings, including global reward chance modifier and world restrictions.
2. Click on an existing "group" (of rewards) or create a new one by clicking the emerald block. The rewards in a reward group share a list of blocks they can be activated by. They can also share other settings, such as world restrictions.
3. Click on the grass block to change the list of blocks that trigger the rewards. Clicking on a block in your inventory adds it to the list. Clicking a block in the list deletes it. When you're done, click back.
3. Click on an existing "reward" (list of commands) or create a new one by clicking the emerald block. Each reward has a list of commands that's executed when the reward is triggered. Each reward also has a certain chance of executing each time the player breaks a block. You can use some basic math to figure out (on average) how frequently a reward will be triggered. If the reward chance is 20%, it will trigger every five blocks on average. (100 / 20 = 5).
4. In this menu, you can left-click an existing command to add a command after it, or right-click a command to delete it from the list. The commands are always triggered in order. To refer to the player who triggered the reward, use %player%.

And you're done! Be sure to delete the example rewards if you don't want them.

In my opinion, the command list and information looks much nicer in-game, but it is also slightly less detailed in-game.
Important commands:
/cmr: Gives plugin information.
/cmr help: Gives a list of sub-commands for the command /cmr.
/cmr reload: Reloads the multiplier, the list of blocks that trigger the rewards, and the rewards themselves and their properties (the chance of getting the reward and the commands to run upon triggering).
/cmr gui [player]: Opens the CMR configuration GUI. If a player is specified, you can attach to their editing session where you effectively have the same permissions they do while in the GUI, and you can click on things for them.
/cmr debug: If you're experiencing an issue, run this command to enable debug mode and debug logging. The console will receive a huge amount of information whenever CMR is working, which should help you troubleshoot. If you need additional help, you can find a log containing all the debug info at <server root>/plugins/CommandMineRewards/debug.log. Debug mode is automatically disabled when the server restarts.
Read the full description