Plugin category: Admin Suggested name: Executor A bit about me: I'm a server owner; I've owned a server for well over 8 months, and I've recently created a whole new world - completely based off RPG. What I want: I'd really like a VERY simple plugin (requires permissions) that allows you to do the following: (Before you panic about the seeming complexity of the plugin, PLEASE read on BELOW the things I would like for it to do) 1. When you execute a command, let's say, "/chooseclass demon", it sends another command and moves this player into the respective permissions group called "daemon". 2. Once this player is moved into the group "daemon", Executor will run another command that is configurable by the user (such as "/spawn"). Now, that's just an EXAMPLE of what I want it to do. I don't know if it's easier for a dev to make it specific or general, but I'd prefer that the plugin is fully configurable. Let's say the config goes like this: 1. User types "/chooseclass daemon". 2. I edit the config to execute a command through the console: / pex user player group set daemon [world](PermissionsEx example.) 3. After the user is moved into the group, it has an option to execute ANOTHER command, such as: /give player 64 diamonds. 4. There can be multiple layers of commands that follow each other. --------------------------***------------------------ I really don't know if it's possible to make it so that player will be the respective player who's typing the command (refer to #2 in "Let's say the config goes like this:") Ideas for commands: A text GUI would be good, a few commands being: /execute <input> <command1> <command2> <command3> ... <command40> ^ that would make it so that after the user types the <input> (/chooseclass daemon, as an example), the <command1> would be executed, then the <command2> would be executed, and so on so forth until the admin decides that there's enough commands to execute. To clear THAT ^ up, basically, an admin can type: /execute </chooseclass daemon> </pex user player group set daemon world> </give player diamonds 64> And that would set the config so that when someone types "/chooseclass daemon", those commands would follow right after. Ideas for permissions: For permissions, it should just be a simple: execute.admin ^ That would allow an admin to use the command: /execute <input> <command1> When I'd like it by: ASAP - even if that means in a couple weeks. Similar plugin requests: I don't believe there are any plugin requests like this. Devs who might be interested in this: N/A
Well for your idea as a command I don't think it will be fully possible. The chatline can only be so long. Also for the teleporting you would need a teleport plugin that takes the players name + location. Cause if the normal teleport command is based on /warp cordx, cordy, cordz and you let the console execute it you will be trying to teleport the console to that location. Which also means they would need a permission for it OR the plugin also takes up the teleport function itself. Seeing it is a RPG server I think a command way of ranking someone wouldn't really fit if I am honest. But that might just be me. There is a plugin that can do what you want by hitting signs, buttons, pressure plates, etc. The plugin is called serversigns (http://dev.bukkit.org/server-mods/serversigns/) You can just put any text on the sign if you are using signs and add commands with /svs add (for a player level command) and /svs add <server> for a command that will be executed by the console. The <player> tag will be replaced with the player who hit it their name. Also you can grant people are short time node. So for example if the player normally can't use /warp from another plugin you can use: /svs addpermissiongrant pluginname.warp You can also set custom permissions per group on what signs to allow by making a custom permission (node built up looks like this for it: serversigns.custom.namehere) and put it on the sign by /svs setpermission namehere If you use the custom node they will only be able to hit signs that have that custom node. so even if you dont set a permission on the sign they wont be able to use it. But you can solve this easily by making a serversigns.custom.all and making sure every group has that and put that permission on the signs you want to be used by everyone
Thank you! You have successfully made my day! Is it possible to make it so that certain signs cannot be used by certain groups? EDIT by Moderator: merged posts, please use the edit button instead of double posting.
Yes there is a way to do that. the node for it is serversigns.custom.nodenamehere the command to add it is /svs setpermission nodenamehere remove the serversigns.use node and just hive them custom node. Also using custom nodes means they cant use a blank permission sign. Just make a custom node serversigns.custom.all and give it to all groups and add that permission to the signs you want to be used by everyone
