Disabling of commands (not listed in config)

Discussion in 'CommandBook' started by Ceress, Mar 1, 2015.

  1. Ceress

    Ceress New Member

    Greetings!

    I know that I can move components in the config file into the "Disabled" list to deactivate them, but what about those very few that are not in the "Enabled" list to begin with? Here's what I am trying to do:

    I currently use a plugin called "AcknowledgeRules" to ensure that newcomers to the server I'm administrating have no claim that they didn't know something was against the server's rules as set by the owner. Unfortunately, that plugin also uses /rules for it's listing.

    I tried using CommandBook's setting that makes it register it's commands with a lower priority than other plugins, hoping that would remedy the issue, but it caused a number of new ones by making all of the other commands I use frequently (/gamemode, /tp, and a few others), cease to function without lengthening to /commandbook:gamemode, etc.

    All I really need to disable is CommandBook's own /rules command, but placing "- rules" in the disabled list did not have the desired result. :(
  2. wizjany

    wizjany Administrator Developer

    It's part of StoredMessagesComponent, which includes /rules and /motd
  3. Ceress

    Ceress New Member

    Awesome! Thank you very much!