Common Issues

Common Issues

Command Book

Command book seems to try and override some commands that it shouldn't (From what I understand). So, XtenDvas has pointed out:

CommandBook/config.yml
low-priority-command-registration: true
This option solves that problem for me.

This should fix it

Use Another Plugins Command Instead

Some people want to use different plugins for other commands, possibly for compatibility reasons. Commands usually include /mute, /warn, and some others. Here's how you can stop MaxBans using those commands (Or, if MaxBans commands are being overriden, force those commands to make MaxBans run it instead)

Using Bukkit's bukkit.yml, from the Wiki: http://wiki.bukkit.org/Bukkit.yml#aliases you can remap commands. Example, to use Essentials mute instead of MaxBans mute for the /mute command:

aliases:
    canihasbukkit: version
    # And this will execute both "save-all" and then "stop" when you type "savestop"
    savestop: [save-all, stop]
    mute: [emute] # Runs /emute whenever someone does /mute instead.
    unmute: [emute] # Runs /emute whenever someone does /unmute instead.
    ban: [mbban] #Runs /mbban whenever someone does /ban 
    unban: [mbunban] #runs /mbunban whenever someone does /unban

Essentials commands all have aliases that start with e. So eMute = EssentialsMute. MaxBans does the same, except with mb. Example, /mbmute, /mbunmute, /mbrangeban will use the MaxBans commands always, if you need a more unique name.

No other issues yet


Comments

Posts Quoted:
Reply
Clear All Quotes