NULLED CommandConditions | Execute Commands with REQUIREMENTS [1.8-1.12] 2.2.6

Tested Minecraft Versions:

• 1.8
• 1.9
• 1.10
• 1.11
• 1.12

What can I do with CommandConditions?
This plugin allows you to create specific requirements to execute different kind of commands. For example, you can create a condition for the command "/warp end" to teleport the player to The End. But the command will not execute, if the player doesn't have an enderpearl called "Ender Teleporter" with enchantment FIRE_ASPECT 1

Currently, there are 13 specific conditions but you can combine them. You can set a player level condition, a world condition, and even a condition for NOT executing commands if there are certain entities nearby the player!

NEW: Execution Mode
Now you can check if a player has accomplish one condition and if so, then it will execute a command (or multiple commands) from the console to that player. This feature is similar to the/testfor command.

This plugin also allows you to create commands with cooldowns and delayed commands. There are many other things that you can see below in detail.

- ✓ 21 Conditions:

• Item Required
  
• Level Required
• Permission Required
• Add Warning Message (Before executing the command, with GUI option too!)
• Money Required (Vault)
• Player must be on specific world
• Player must be on specific location (coordinates)
• No specific Entities nearby
• Time played on server required
• No in specific Gamemode
• Add Cooldown to a command
• Add Delay to a command
• Jobs Level/Job Required (JobsReborn)
• Factions Conditions

- Percentage of Members Connected on the Faction
- Members of the Faction
- Power

• Players Connected
• Health Condition
• BattleLevels level required
• WorldGuard region
• No Items in Inventory Condition
  
• More Conditions soon...!

- ✓ Execution Mode (Constant check if the player accomplish conditions)
- ✓ Editable Error Messages
- ✓ Editable Success Messages
- ✓ Messages with variables
- ✓ Easy to use (Tutorial below)
- ✓ Works with 1.8+

TODO:
- Add sounds for error and success events.
- error-command: Same as error-message, but instead of sending a message it will execute another command.
- More Conditions!



To start creating your own conditions, you need to go to the config. You'll see a lot of default conditions. You can remove all of them but make sure not to delete the Commands section.

IMPORTANT: If you want to test some conditions first you need to /deop yourself, because OP users bypass all of this conditions.

The commands conditions config follow this structure:
Code (Text):
Commands:
<section-name>:
command: "<command>"
conditions:
condition1
condition2
....
error-message:
- '<message-line1>'
- '<message-line2>'
- ...
success-message:
- '<message-line1>'
- ...
<section-name>:
This is not the command, is just the name of the section, you can name it as you want. Just be careful not to have sections with the same name.

<command>:
Here you need to put the command that will have the conditions. If you want to add a condition to the command "/warp" you can, but this means that all warps will have that condition. (/warp end, /warp survival). If you want to create a condition for specific one warp, use:
command: "/warp <arg>"

You can add the same condition for multiple commands by adding a ";" before the next command like this:
command: "/home;/tpa;/spawn;/warp"

If you want to set the condition below for ALL COMMANDS, just put:
command: "all"
(Why I would want this?)
For example you can add the condition of no enemies nearby. So, the player will not be able to execute ANY commands if there are Zombies, Skeletons... near him (radius editable).

error-message and success-message:
The error message will be sended to the player if he doesn't have the necessary requirements. The success message instead, will be sended to the player when the command is executed correctly. Here you can add multiples lines, so the message is fully editable.

You can delete the success message if you want, there is no problem with that.

There are specific variables you can use in the message. Each of these variables will be replaced with its corresponding value:

Conditions:
Of course, the most important thing of the plugin. Here you can find a tutorial of each of the created conditions.

Execution Mode:
This part is a little different to use, but is simple. With this feature, the plugin will check if the user accomplish one condition, and if so, a command will be executed from the console.

For example: If the player enters a certain location, you can define a command to teleport the player to another location. Or if the player reached level 30, you can give him money, send a specific message and whatever command you want.



Files:




COMMANDS:
-/coc info Shows plugin info
-/coc reload Reload the plugin config

PERMISSIONS:
Just one: coc.admin






Please avoid posting bad ratings before asking. If you have problems or bugs with the plugin contact with me or post on the plugin discussion and I will take a look at it.

Terms & Conditions
By purchasing CommandConditions you agree to the following Terms & Conditions:
1) You can't resell/redistribute this plugin.
2) There are no refunds.
3) You can't decompile this plugin.
4) You can't claim this plugin as your own.
5) You can't post bad reviews before asking for help or contacting with me.
6) Only use this plugin on your server/network.
7) I can change the price of this plugin anytime.