CommandsEX
CommandsEX - modular plugin architecture
Notice
Development builds of this project can be acquired at the provided continuous integration server. These builds have not been approved by the BukkitDev staff. Use them at your own risk.
Jenkins (#6 and beyond for 1.5.1)
What's Inside?
- Teleportation commands
- Warping
- Spawning
- Items and Inventory
- Mobs Related
- Homes management
- Banning
- Jailing
- Common Administration (kick, freeze, mute)
- Time Control
- Weather Control
- Informative Commands
- Fun Commands
- Translations
- Join and Leave Messages Grouping
- XMPP (Jabber) Chat Relay
- Chat Text Replacements
- Chat Spy
- Message Of The Day
- Custom Player Commands
- Custom Console Commands
- Play Time-based Player Promotions
- Economy-based Player Promotions
- Death Group
- TNT Kamikaze!
- NanoSuit
- Weather Forecast
- Explosion Control
- Shutdown Custom Kick Message
- Update Alerter
- Custom Death Messages
- Coloured Signs
IMPORTANT INFORMATION (25. June 2012)
This project has now been taken over by iKeirNez, who will continue work on CommandsEX in the same fashion I did - and even better! It was a pleasure to create this tiny little thingy for you guys. Have some great Minecraft days in there and see you all in another life :) zathrus_writer
Build your very own plugin set - Lego style!
If you ever needed a single function but had to download a massive plugin that contained it, you will probably know the feeling. It could be hard to pick up the right plugin-set for a server with all the plugins currently in existence. Especially since many of them conflict with each other.
That is the idea behind CommandsEX project - to allow server administrators to choose which commands and functions they really need and let them trash all the rest.
More information
- Official Wiki
- CommandsEX Builder - create your very own CommandsEX build!
- CommandsEX Test Server - play about with the latest features not yet available to download!
Configuration
CommandsEX uses standard config.yml file, located in CommandsEX folder in your plugins directory. Options in the configuration file are clearly commented and their list is also present in the Configuration section of the plugin Wiki.
Additionally, CommandsEX allows anybody with the permission to access the /cex command. Some options from the config file are retrievable and can also be updated via this command.
Need help?
- Create a Ticket - if you have a feature request or a bug to report
- BukkitDev Forum - support, questions, suggestions and general chat regarding CommandsEX
- Leave a Comment - if you need a question answered or have a word of praise
Donations
Donations help keep CommandsEX alive, updated and improved. If you use CommandsEX and would like to help the authors continue working on CommandsEX then you may want to consider donating. You can donate whatever amount you like by using the PayPal donate button below.

-
View User Profile
-
Send Message
Posted Sep 14, 2012@eubie67 @eubie67
Thanks for reporting this, the reason I was not replying was that I was unavailable yesterday but I am back today full steam ahead.
We have fixed this issue and added a way to change it in the config via the node "promoteSet", we may change this in the future to allow server owners to have promoteSet at false for ecoPromotions but true for timedPromotions.
Here is a GitHub commit with the fix, this fix will be included in the next version of CommandsEX. https://github.com/iKeirNez/Minecraft-CommandsEX/commit/6f8ce7ea6e9b32541caff0b716efef7fd1bee8fe
-
View User Profile
-
Send Message
Posted Sep 14, 2012@eubie67
iKeirNez is looking into this issue as we speak!
-
View User Profile
-
Send Message
Posted Sep 14, 2012There was a flurry of activity and quick responses for a couple days - now questions seem to be hanging out there a bit.
It would be really helpful for me to be able to set group with ecoPromote instead of just adding groups. That's one of the final issues that's holding up my release of 1.3.x on my server.
I know there may be other things going on, so if I'm going to have to find a workaround for the time being, I just need to know that.
Thanks, eubie
-
View User Profile
-
Send Message
Posted Sep 12, 2012At the moment I have a critical bug with any user being able to access anyone else's home which is being abused heavily by some users. I can understand if it takes a while to fix and I really appreciate your work however this is a critical bug, server/game breaking almost, so I would love a quick fix. Thanks!
LINK: http://sourceforge.net/userapps/trac/zathrus-writer/ticket/161
-
View User Profile
-
Send Message
Posted Sep 11, 2012@eubie67
Ok - I've discovered a couple things.
1. When I update the config.yml, a Reload is not enough to make everything sync up. I have to restart the server, then the econ checks work as expected.
2. It appears that ecoPromote works by checking a player's dollars, then adding any groups (ranks) that a player qualifies for to their existing list of permission groups. If more than one group is added at one time, these groups are added in what appears to be random order.
This is ok if the player gradually earns money and works his way up through the ranks one rank at a time. Other than that, it can create problems in a couple of ways.
First, if the player earns a bunch of money all at once, qualifying for a rank that is two or more ranks above his current rank, all of the new groups are added - the highest group earned and all those in between, but not in rank order. So that the permissions.yml may not list the highest ranking group at the top of the list of groups for that player. This messes up the player's name prefix because PEX displays the prefix for the first group on the list in the permissions.yml file. This prefix is the primary indication of the player's rank on the server.
Second, if the player gets demoted for any reason, then even if the groups were in the proper order to begin with, the order gets all out of whack.
Third, once the group orders are out of whack, subsequent promotions are wonky because it appears to the player that he is one rank because of the name prefix, when he is actually a different rank.
On my server, players ascend through the ranks and earn different permissions with each rank-up. Permissions are inherited from lower groups so that ranking up does not result in the loss of any permissions - they are cumulative. Thus, each player should only be in one permission group - the highest one they qualify for based on the number of dollars they have.
All this to say, it would be very helpful to me if there was a way to set a flag that would cause CEX to check the player's dollars, then set the group to the highest qualifying group rather than add all the qualifying groups to the current list of groups. Like what happens when you issue a "/pex user <playername> group set <group> [world]" command. I can see why some would want groups added, so I wouldn't suggest the existing functionality be eliminated, but I'm hoping this replacement functionality can be added.
Thanks, eubie
-
View User Profile
-
Send Message
Posted Sep 11, 2012@kezz101
Was thinking of saying that but decided against it haha
-
View User Profile
-
Send Message
Posted Sep 11, 2012@iKeirNez
'yet' :P
-
View User Profile
-
Send Message
Posted Sep 11, 2012@kezz101
I am! Loving the new features you have added, no regrets yet about adding you to CommandsEX!
-
View User Profile
-
Send Message
Posted Sep 11, 2012@Ferkswe
Yes, the seconds are not exact, it depends on your TPS (ticks per second) which come from how fast the host computer is. So sometimes it might be less, and sometimes it might be more. But there shouldn't be a BIG difference.
-
View User Profile
-
Send Message
Posted Sep 11, 2012@Ferkswe
What about the /time issue? If that persists then please send me your JAR file, it could be another issue with the Builder.
-
View User Profile
-
Send Message
Posted Sep 11, 2012Anyone excited for the new update coming soon? I sure am :) Great stuff is on the way! Thank you all for you continual support!
-
View User Profile
-
Send Message
Posted Sep 11, 2012@iKeirNez
Some additional info. About an hour after I left the previous comment, the auto promote process executed and the player was promoted to the appropriate level. I'm going to do some additional testing and see if maybe the ecoPromoteTaskTime setting is picky. I have it set to 30 seconds, and maybe there's something going on with a cycle time that's longer than 30 that's getting in the way. I'll try some different settings and let you know what happens.
BTW - I used to use iConomy and it was great, but I jumped to BOS when the iConomy page went inactive. Now I see that it has been picked back up and a new version is out in alpha.
Thanks, eubie
-
View User Profile
-
Send Message
Posted Sep 11, 2012@iKeirNez
No need, the permissions issue resolved itself. :D
-
View User Profile
-
Send Message
Posted Sep 10, 2012@Ferkswe
Please private message me your bPermissions and CommandsEX jar! Thanks!
-
View User Profile
-
Send Message
Posted Sep 10, 2012@iKeirNez
In that case, an easy and clean permissions list is coming right up.
Disregard this. Fixed itself suddernly. Also, I noticed but I'm not sure if it's due to your plugin or my permissions handler but (haven't gotten all the way) banning and Ranks&Groups's permissions doesn't work. I added them but I get a white (which is strange, it's usually red) message saying I lack permissions. I'm in the group admin which has all the permissions listed on http://sourceforge.net/p/commandsex/wiki/Banning/ and http://sourceforge.net/p/commandsex/wiki/Ranks%2C%20Groups%2C%20Promotions/ Any ideas why? So far everything else has worked fine.
Oh and also, the time command is broken. [CommandsEX] Couldn't handle function call 'cex_time'
And, the localization page the wiki points to is broken. http://dev.bukkit.org/server-mods/commandsex/localization/
I think that was all for now. Thanks for a great plugin!
Edit: Oh right, using a build from last night, made with the builder. Latest rCB and bPermissions.
-
View User Profile
-
Send Message
Posted Sep 10, 2012@Ferkswe
Here's the best I can do, it has some extra info like default: op and children. Some permission nodes may be missing also. We will try adding a wiki page or something in the future with a list of all permission nodes.
EDOT: Forgot link haha http://pastie.org/private/axxwnvnsgvmykcsyve3og
-
View User Profile
-
Send Message
Posted Sep 10, 2012@eubie67
That is odd, can you try testing with another economy plugin like iConomy. The problem is that I am not the original author and have the not used the ecoPromote function nor did I code it. Please let me know of the results and we will try and fix this asap.
-
View User Profile
-
Send Message
Posted Sep 10, 2012You guys don't happen to have a list of all permission nodes laying around? Like in one list that is.
-
View User Profile
-
Send Message
Posted Sep 9, 2012Is there a trick to making ecoPromote work? I feel like I've got the setup right, as best I can tell from the instructions in the wiki. Strangely, I have gotten a couple successful promotions based on dollar amounts at random times, but 95% of the time it doesn't seem to work.
Here are the relevant lines from config.yml
I'm using PEX, Vault and BOSEconomy. Everything else seems to work. I can add, set, pay, etc. in BOSEcon. I can promote, demote and set groups in PEX. But when a player crosses a dollar threshold, the econPromote doesn't kick in. Like I said, strangely, it actually did promote two or three times during testing, but they were pretty random. Like when I gave a player money to get them to 5000, it would promote them, then I'd give them 5000 more to get them to 10000, and nothing would happen.
Are there any permission nodes to set up for ecoPromote? I couldn't find any mention of them.
Anything else I should be checking?
Thanks! eubie
-
View User Profile
-
Send Message
Posted Sep 8, 2012Incorrect Version Issues
We have recently had reports of incorrect version being reported by CommandsEX using the /cex command and in the server log on the server startup. This issue was traced back and it was due to a small, idiotic mistake I made. We have now fixed this and it is awaiting approval on BukkitDev. We will shortly be releasing this fix across SourceForge and the CommandsEX Builder.
Thanks for you understanding.