CmdControl - Developed by Simon_Flash (firstname.lastname@example.org)
Current Version: 1.1.0-pr1
Current Stable Version: 1.0.1
Status: Active -> New features and updates are in development
Note: CmdControl is built on API 6 (1.11.2), but is also confirmed working for API 5 (1.10.2). API 7 has not been tested.
CmdControl provides additional options for working with commands, primarily through it’s scripting functionality. Scripts can allow you to:
- Combine multiple commands into a single command
- Create multiple aliases for commands
- Accept arguments for commands
- Add cooldowns to commands
- Add costs to commands
Additionally, it is intended to have various utility commands for common actions (such as delaying commands, requiring a player to be online, etc.) in the future.
CmdControl has a very readable, user friendly configuration system that does not require any form of coding experience to use. Errors are printed out both to the console, as well as place directly above the configuration node that caused the issue.
Additionally, CmdControl verifies the type of arguments before any commands are actually executed, which many other alias/scripting plugins do not. This prevents a situation where a portion of commands execute properly while others fail, which can lead to issues like players receiving only half of a kit. With CmdControl, this problem virtually disappears!
Learning CmdControl is going to take a bit of trial and error, but I’ve done the best I can do document it’s main functionality with a bunch of examples on the wiki (linked above). Additionally, you’ll be able reference some default scripts when the plugin is first installed to help you get set up. I’m working on getting a stronger tutorial up for CmdControl, so keep an eye out for that!
After creating your first script, you’re going to need to address permissions. Each script has it’s set of permissions, which match the following:
cmdcontrol.scripts.<script-name>.base: Base permission to run this script
cmdcontrol.scripts.<script-name>.nocooldown: Bypasses the cooldown (if set)
cmdcontrol.scripts.<script-name>.nocost: Bypasses the cost (if set)
All scripts may able be run using
/script, like below. This permission is separate from individual script permissions.
/script <script-name> [args...]: Executes
<script-name>with the given
Questions & Issues
If you need support for any aspect of CmdControl and you have already checked the wiki page, simply ask below or join the support discord above and ask in
#cmdcontrol. Please include any information relevant to your problem such as the Sponge version, the CmdControl version, the script’s config file, and so on. I’ll do my best to respond to any of this quickly, but please be considerate and know that these things aren’t instantaneous.
Suggestions & Feedback
If you have a suggestion for CmdControl or would just like to provide some feedback, feel free to get in contact with me in any of the ways above. I’d love to see what kind of creative thing you can figure out with scripts - one of my first was a google bot script, so see if you can beat that!
- This plugin has been in development since March
- It was created because I hated Skript
- It’s name has been changed 4 times
- The first working form confused basically everyone
- It was used to fix the
/back -fissue in Nucleus
- The current form was programmed in 4 days
- It is the only know plugin like it to type-verify arguments