Solved Block /plugins and /pl and /?

Discussion in 'Bukkit Help' started by PapiDimmi, Feb 26, 2013.

Thread Status:
Not open for further replies.
  1. Offline

    PapiDimmi

    I took away /plugins from Resident, but all my players say that they can still do /plugins! And I tried PluginList, but that plugin didn't work!

    Please help me! I don't want douchebags to copy my plugins D:
     
  2. Offline

    Abusivee

    I believe installing a permissions plugin will take care of this problem. I had the same issue, but since I re-installed Group Manager, users cannot do /pl or /plugins.

    You may want to try in Essentials...

    Code:
    # Disabled commands will be completely unavailable on the server.
    # Disabling commands here will have no effect on command conflicts.
    disabled-commands:
      - plugins
      - pl
    Also, for a guarantee... You can use WorldGuard.
    Simply do:
    /rg flag __global__ blocked-cmds /plugins,/pl,/
     
    PapiDimmi likes this.
  3. Offline

    PapiDimmi

    Thanks!
    1. I have Essentials GroupManager, and it's updated to newest version.
    3. I did that! It worked! Thanks <3
     
  4. Offline

    Abusivee

    ;)
     
    PapiDimmi likes this.
  5. Offline

    Necrodoom

    bukkit.command.plugins and bukkit.command.help are given by bukkit by default, you need to negate them.
    thats is ONLY for essentials commands, /plugins isnt one.
     
    PapiDimmi likes this.
  6. Offline

    PapiDimmi

    necrodoom
    Ops, my bad! I removed the essentials.plugins from them!

    Edit: Ops, NOT my bad! They hadn't bukkit.command.plugins!

    Edit2: Why reply to this thread? It's already solved :)
     
  7. Offline

    Necrodoom

    i said bukkit.command.plugins and bukkit.command.help are given by bukkit by default, you need to negate them, they dont need to be given first on the permission plugin.
    trying to give you a different solution because this isnt a single case, so you know what to do incase you face other default: true nodes
     
  8. Offline

    PapiDimmi

    They don't have essentials.plugins, essentials.help, bukkit.command.help or bukkit.command.plugins
     
  9. Offline

    Necrodoom

    i said, negate them, - -bukkit.command.help, - -bukkit.command.plugins
     
  10. Offline

    PapiDimmi

    What that means?
     
  11. Offline

    Necrodoom

    prefix a permission node with '-'
    EG: -bukkit.command.plugin instead of bukkit.command.plugin
    this takes away a permission node if it was available previously, either by inherited permissions, or by default: true nodes such as here.
     
  12. Offline

    PapiDimmi

    I don't understand :(

    It's like this:
    permissions:
    - essentials.tp
    - bukkit.command.tp
    - exampleplugin.examplepermission
    - example.example.*
    - exampleplugin.examplepermission.examplepermission
     
  13. Offline

    Lolmewn

    PapiDimmi
    permissions:
    - You.Can.Do.This
    - -You.Cant.Do.This.Because.-
     
  14. Offline

    PapiDimmi

    So I put in in two -s? What does that make?
     
  15. Offline

    Lolmewn

    Makes it negative. AKA, not giving you permissions for it (while normally a normal node DOES give permissions for something).
     
  16. Offline

    PapiDimmi

    But isn't that the same as NOT having in the permissions list?
     
  17. Offline

    Lolmewn

    No, because some permission nodes are defaulted to everyone. (aka, everyone has them, except if you explicitly don't give them).
     
    PapiDimmi likes this.
  18. Offline

    PapiDimmi

  19. Offline

    Necrodoom

    basically, bukkit.command.plugins is a permission node that is defaulted to everyone, so you can negate it if you want.
     
    PapiDimmi likes this.
  20. Offline

    PapiDimmi

    necrodoom
    Thanks! Now this thread is....uhm... double solved! :p
     
Thread Status:
Not open for further replies.

Share This Page