Bukkit

'changeprefix': command: /prefix type: RUN_CONSOLE permission-required: false runcmd: - manuaddv $player $arg1 prefix cooldown: 1 This is what I wrote down and its not working, Im using group manager as a permissions plugin. Can someone please help?

I need some help here.
If I type /sudo <player> <anymycommand> it will not work.
Also, if I put a mycommand in the commands.yml in the root of the server, the command will not work.
So
How does the server recognize my command?
Is there anything, like, cmd.<thecommand> or something like that?

<<reply 2618191>> JohOply

Well, I can not create a command to be executed twice a day, but you sure can put a 12 hour delay on it.
It would be convinient to change the command name, so it does not affect you.
Here, a example of what you can do:

'tptwice':
  command: /telep
  type: RUN_AS_OPERATOR
  permission-required: false
  runcmd:
  - tp &arg1
  cooldown: 43200

Maybe, instead of cooldown you want to add a cost? Just change cooldown for cost, like:

  cost: 300

The player will execute the command /telep <player>

@Leuggim

@boushwa

Well, I know a way you can do this. Will require the "serversigns" plugin - http://dev.bukkit.org/bukkit-plugins/serversigns/pages/commands/

So, all you need to do:

• Create your command.
• Get track of your command number (for permissions)
• create the sign
• Execute the command /svs grant add mycommand.cmd.1 (the number you change for your actual command number in your commands list)
• Right click in the sign to apply
• Execute the command /svs add /<thecommandyoucreated>
• right click the sign again.

<<reply 2627605>>
You don't need a plugin for this, if you use mycommand.
Witch permission plugin do you use?
I will assume that you use PEX (PermissionsEx)
An advice, I don't know what kind of server you run, but maybe you want to put a cost for this. Players can do a lot of annoyng abuses if they can freely change prefixes. Maybe a cooldown too.
Note: This will also may change the colour of the nick, if the player does not have a custom nickname.
So, if you use pex, and want cost and cooldown, do this:

'changeprefix':
  command: /prefix
  type: RUN_CONSOLE
  permission-required: false
  runcmd:
  - pex user $player prefix $arg1
  cost: 250
  cooldown: 60

Would anyone like to help me with an issue im having? I need to create a plugin so when players do /prefix they can change their own prefix and only their own prefix ex: /prefix [Dark] Im using groupmanager by the way. Thanks in advanced.

I have a question can you add that $args working in item menu that can be usefull von ban menu you typing /banmenü playername and click on the item and the items is banning for examble $arg1

I am likely overlooking something very obvious here however is there a way to set a shared cooldown?

So a CD on /fix which also triggers the cooldown on /repair, /efix, /erpair.

Thank you for this plugin using it in place of my paid for plugin because I need a 10 minute delay to do a final step on a command.

Hi guys !

I want to create a command (TP, already exist) which can be used only 2 times per days by each player. Someone could help me to do that please ?

Thanks in advance :)

Yeah add NPC support to plugin. When I create a Command I can add this command to NPC

@boushwa

Use a signs plugin, like ServerSigns.

Greetings,

I want to create a simple command that displays text in the chat window when a sign is clicked. Easy enough. However, I want all players to be able to use the command but only by clicking the sign. I don't want them to be able to type in the command manually and use it that way. I need it done this way to ensure players will have to come to the sign to get the information from the command.

Unfortunately, I have to enter the command onto the sign and all players will know what it is. Even if they know the command, I can't seem to prevent them from manually entering the command without preventing them from clicking the sign as well.

Is there a way to set it up so that A) I don't have to display the actual command on the sign or B) the players can't run the command manually but they can access it when clicking the sign?

Thanks in advance.

boushwa

MyCommand is inactive

@Leuggim

Yeah, would have liked to see the dev fix some of the bugs, especially with scripting logic and the difficulty in the interaction processes between the variables, players, and the text arguments. For the simple commands it's less time consuming to just make something through this plugin than make a standalone plugin for it, yet even simple things cannot be logically created sometimes due to the strange interactions.

@ThgilFoDrol

Thank you very much for your atention and support! You gave me a very better understanding of this plugin.

But, after all, I was able to do what I want using the spigot Commands.yml file :P

As simple as this, witch was my previous logic:

mt: - mute $$1 $$2 - af announce &6&l[ChatControl] &f&lPlayer&e&l $$1 &f&llost the right to use chat! - af announce &6&l[ChatControl] &f&lTime - &e&l $$2 - af announce &6&l[ChatControl] &f&lCheck out the &e&l/rrules &f&lof the server!

@xDizasterCYx

Not sure if you mean for the plugin to print command outputs in chat as well as on the screen. Shouldn't be too hard, just replace the places where you send the player the output via a chat message with the title. Or you could just have the command run the /title command too.

There's a problem with outputting to title and subtitle though- peoples' screen resolutions might not be big enough to display a full output message- though 1080p is fine for most simple/short outputs.

@Leuggim

Leuggim: I did some testing with your command- this is the setup I used:

'testmute':
 command: /testmute
 type: RUN_COMMAND
 runcmd:
 - '/mycmd-playerdata set $player lastMuteTargetCached $arg1'
 - '/mycmd-playerdata set $player lastMuteDurationCached $arg2'
 - '/testmutetechnical'
 permission-required: true
 register: true
 permission-node: thgilfodrol.isawesome
 require_all_arguments: true
 permission-error: '&cInsufficient permissions.'
 error-message: "&cMute a player and broadcast it to everyone. \nCorrect usage: /testmute <player> <datediff>"

When this command finished saving the PlayerData, it would execute the command /testmutetechnical:

'testmute_technical':
 command: /testmutetechnical
 type: RUN_COMMAND
 runcmd:
 - '/mute $PlayerData%lastMuteTargetCached% $PlayerData%lastMuteDurationCached%'
 - '/tellraw @a {text:"Player $PlayerData%lastMuteTargetCached% lost the right to use chat!"}'
 - '/tellraw @a {text:"Time - $PlayerData%lastMuteDurationCached%"}'
 permission-required: true
 permission-node: thgilfodrol.isawesome
 permission-error: '&cInsufficient permissions.'
 register: true

Basic explanation of what I did:

Testmute is a simple command to create the variables lastMuteTargetCached and lastMuteDurationCached, which store the target player and the time to mute, respectively. When it finishes creating them, it then executes the command testmutetechnical, which accesses the player's private variables and runs the mute command with the variables previously declared and set. It then attempts to output the variables in the text format you used in an announcement to everyone with tellraw (I didn't have that plugin you were using to make an announcement).

However, while testing it I encountered an odd bug (I'm running a build of spigot from july 6 2015, would paste the /ver output but I spoofed it to say hmod alpha1.1, etc to deter script kiddies), where the $arg2 variable isn't interpreted correctly- it only works properly if you use it in the same line as $arg1- for example:

runcmd:
 - '/mute $PlayerData%lastMuteTargetCached% $PlayerData%lastMuteDurationCached%'
 - '/tellraw @a {text:"Player $PlayerData%lastMuteTargetCached% lost the right to use chat for $PlayerData%lastMuteDurationCached%!"}'

To simplify it so you can use it without my overcomplicated setup, you would simply paste in:

runcmd:
 - '/mute $arg1 $arg2'
 - '/tellraw @a {text:"Player $arg1 lost the right to use chat for $arg2!"}'

This discovery is a fix to the (at this stage, unless I'm missing a glaring error on my part) issue where $arg2 is not interpreted correctly if on a line after usage of $arg1.

By using /testmute individually and removing the 3rd line of runcmd where it attempts to run /testmutetechnical, you can see that the mycmd-playerdata debug output shows that even when used in the playerdata commands, the input is still saved erroneously- $arg1 is saved as the username, but $arg2 is saved literally as $arg2.

Testmute screenshot: http://i.imgur.com/273EwsC.png

If this is a bug, hopefully the plugin author sees this and fixes it, took an hour or two of testing on my part to work out how everything functions (commands went through perhaps 5 or 6 variations) as well as to write this documentation.

@pj100600

Thank you very much I did what you told me to, but i still get this, in the broadcast:

run cmd: /mt pl_sample 1m

(Player example gets muted for 1 minute, ok)But in the broadcast i have this:

Player pl_sample lost the right to use chat! Time - $arg2

What I mean, the particle $arg2 is understood in the third command as text entry. But the $arg1 works fine in both commands. It was the same problem with the command I used in the first mesage...