TriggerCmds
With tcmds you can link any type of craftbukkit or plugin commands to buttons/levers/plates It's simple too use and it has persistence so you can reboot your server without loosing anything
Features
- Simple way to link cmds to triggers
- Works (in theory) with almost any command
- Uses persistence to save all the triggers
- Has permissions ("triggercmds")
- Batch triggers where several commands can be executed in succession.
Tutorial
Make a trigger
- /tcmds edit TriggerName - Opens/creates the trigger edit
- /tcmds set $me:/tp $ply $me - Makes you teleport the player that presses the button to you
- Left Click on the switch - Regs the switch and closes the edit
Make a batch trigger
There are now two ways to create batch triggers. All in one go or one command at a time.
All in one go
- /tcmds edit TriggerName - Opens/creates the trigger edit
- /tcmds set $ply:/spawn & $me:/time day - Makes the player that presses the button teleport to the spawn AND change the time. The spaces around the & are important here. You can list as many commands as you can fit.
- Left Click on the switch - Regs the switch and closes the edit
One command at a time
- /tcmds edit TriggerName - Opens/creates the trigger edit
- /tcmds set $ply:/spawn - Makes the player that presses the button teleport to the spawn
- /tcmds add $me:/time day - Change the time after making the player teleport.
- Left Click on the switch - Regs the switch and closes the edit
Delete a trigger
- /tcmds edit TriggerName - Opens/creates the trigger edit
- /tcmds del - Deletes the trigger from the db
Delete a Link
- /tcmds edit TriggerName - Opens/creates the trigger edit
- Right Click on the switch - Deletes the switch and closes the edit
Executors
- $me: - The cmd will be executed by the trigger maker (only if is online)
- $ply: - The cmd will be executed by the player that pressed the trigger
- $con: - The cmd will be executed by the console
Variables
- $me & $ply - Used inside the command you want to declare
@agentpaco
What runner are you using $me or $ply?
Sorry about the ambiguity in the description its copied from the old developer's page. The permission of "triggercmds" is just for the plugin commands i.e. "/tcmds" - I expect this to be a runner issue either on your part or my part. Can you run your own buttons?
@XeonG8
That, don't worry next version will be JRE6 compatible if you cant upgrade to JRE7. If you can then just do that!
nobody can execute the command with the trigger because they dont have permission. You said this has permissions.....what are they?????
Only difference I can think of is Java 7 and Java 6
Doesn't work at all with this error
It worked fine locally though, only with this error: