Bukkit

@Ivanpro

It's registering the command in console, for when I do /hub it says in console, "mycmd...1 issued" but for some reason it says no command found, and when I do /server lobby normally it works fine

It says no command found when I try this, and I simply replaced an example's information: http://pastebin.com/BkQyE3hy

Can ANYONE create a working command on a Stone pressure plate and not have to be set to System Operator to activate it? Also are you using PermissionsEX? If so, can you please post an example of both your Command and your permissions nodes so I may look at them? This entire plugin needs to have all of its documentation cleaned up to reflect the working code as it now stands. Do I need to send in another donation to Ivanpro to get an answer about why this has and is failing? I can not tell if I am making some bonehead mistake or if the plugin is failing.

@ZeriyaGaming

I was using the latest and it failed, you suggested for someone else with the same problem to try the Dev build.. it fails also...

@RednecksFTW

It's semi possible. If you want pages that will be a problem, but making a custom /help is 100% achievable.

@ScagexCraft

Reason why they aren't working is because they both are assigned the same number command. Try changing /hub to '2':

@PresidentBacon

If you want to disable /pl for ops as well, do what I did.

'8':
  command: /pl
  type: text
  text:
  - $redThis Command has been Disabled by the owner!
  runcmd:
  - /help $arg1
  cost: 0
  delaytimer: 5

That will send a text in chat instead of listing plugins. Works for ops and console. Sudo bypasses the command.

@Sarham

That's probably because you're using a DEV file. With DEV files you will always come across bugs. Use the latest file on here and it should work just fine.

@Jokerwitz

If you get an answer to this please let me know too.. I am using the Latest Dev and it still fails.

STONE_PLATE fails with no permission to interact, and WOOD_PLATE fails to even be a viable block to set a command on. Yes I am running the Dev 5.0.0dev01 version

When I try and disable a command, I've set up:

'pl':
  command: /pl
  type: ADDPERMISSION
  permission-node: mycommand.disable
  permission-error: '§bUnknown command'

and negated the permission "mycommand.disable" from everyone (including ops). Non ops get the correct error message but ops can still use it. I want to disable this for ops too. I'm not sure if I am going about this in the correct way but it seems to work for non ops.

I am using the latest 5.0.0 dev version.

Thanks.