NULLED ConditionPerms 2.0.3

Tested Minecraft Versions:

• 1.8
• 1.9
• 1.10
• 1.11

More then 3900+ placeholders/variables from different plugins

Please make sure to read the entire description before buying especially requirements and limitations.

Use FreshDesk for support. I will not respond to reports in the description or PM.

ConditionPerms is a plugin that allows you to use my large collection of placeholders to check for specific conditions. The plugin uses javascript to evaluate the conditions and depending on the result it will allow you to execute commands or give permissions.

The plugin also allows the opposite, meaning when the condition is no longer met you can either choose to revoke the permissions again and execute different commands, or you can just do nothing and make it work as a one time thing.


What makes this plugin worth $2.5:
- 5000+ Placeholders you can use in conditions or commands on grant/revoke
- Good performance and continueous research for better performance
- More placeholders are being made ~monthly
- This plugin is for the more advanced server administrators. There is a smaller audience to attract


Well, my name is Maxim Van de Wynckel but most people know me as Maximvdw. I live in Belgium (the Flemish part) so my timezone is GMT+1 (KEEP THIS IN MIND). I started creating a few plugins on Bukkit >3 years ago after hMod got discontinued. I've been programming for around 11 years (since I was 8y/o) where 6 of them are in Java , C# ,.. . After some public plugins on DevBukkit I started to create free private plugins for people that asked for it. I created a lot of plugins back then but due to the lack of respect on dev bukkit (death threads, no 'ty' for plugins I made, etc...) I left bukkit and started to spend more of my time into making custom quality plugins on my site. I became an owner of a server I loved that was left abandoned but it lacked high performance resources so I became extremely worried about performance. At first I tried to limit my ideas to limit the use of resources but that wasn't the way to go since No fancy things means No fancy players. I started to spend 90% of my time on a plugin on testing performance (and 10% on coding and testing the features).

Now I am a busy developer, I still get around 5-6 plugin request a day (but can only handle 1 or 2 a day). In my free time,.. I created plugins I love and think others will love (like this one <3). Some servers may find it bad that I ask money for most of my plugins, but I think for servers that even do not make a lot of money the features and coolyness of this plugin will be worth the money , if you have a problem you can always skype me, email me, leave a comment, PM me or ... find another way to contact me.



The idea of ConditionPerms started in December 2014 but back then it was just a small idea of a little feature. The first alpha release was ready in July 2015 and has been under testing since that day to increase performance and stability.

A lot of (true/false) placeholders were made specifically for this project since 2014 to create cool but simple things.



The plugin has been through a long testing period to increase performance. Javascript evaluating is not the most performance friendly task in the world especially when you have to do a lot of checks for a lot of players.

But after research, optimizing the placeholders and providing the right tools to help you get best performance you can change the performance as good as you want.

This is a list of examples of performance friendly tasks. 1 = most performance friendly. This doesn't mean that when you use placeholders with fast changing data it will be bad for the performance, this is just a scale rather then a grade.

1. Conditions that only contain a true/false placeholder
   These conditions will not be evaluated by javascript and are extremely fast.
2. Conditions with placeholders that do not change often
   The conditions are not evaluated when the expression with the replaced placeholders is the same as before. This is useful for expressions that for example make use of numbers for levels, etc... since levels do not tend to change every second.
3. Conditions with fast changing placeholders
   Conditions with placeholders that change often (such as positions ,...) have to be checked every check interval.
4. Conditions with Javascript libs. such as Math ,..
   These take a bit longer because the Math lib. has to be loaded and evaluated/calculated as well
5. Conditions with custom placeholders
   This is a generalization and may not be true for all custom placeholder. A lot of custom placeholders added through the API do not make use of caching causing them to sometimes contact a MySQL server every time the condition is checked.