It all started with a simple request:
At first, I though - why not? Sounds simple enough.
Well.. 4 days and some hardcore hacking of Java Virtual Machine later, I'm banging my head against the table just before I finally got a working solution for this. Takeaway: never ever promise anything to be released with the next version.

Version 1.2
============
New major version.

New features:

• /aa_fixcommand and /aa_disablecommand now also work for plugins that use event listeners to register their commands as opposed to the standard CommandMap registration, which was ignoring our command cancellation method
  
  
• added /aa_mutecommand and /aa_unmutecommand to mute output of your commands (i.e. the command will still do its job but nobody will see any message in case it will try to send one)
  PLEASE NOTE that this functionality is somewhat experimental, since it involves hacking both CraftBukkit and Minecraft server while it is actually running (all modifications are done in memory, your JAR files remain intact). Although highly unlikely, it might be incompatible with custom CB, Spigot, PaperSpigot and other builds that modify any of the "sendMessage()" methods found thorough CB and MC code. Please send any errors this plugin might generate as a consequence, so I can fix them promptly
  
  
• ability to fix, disable or mute commands of AdminAnything itself was disabled, as it could lead to inability to revert these changes in-game
  (i.e. if you disabled /aa_reload and /aa_unfixcommand, you wouldn't have a way to restore fixed commands without editing the config file manually and restarting your server)
  
  
• added /aa_playerperms which will list all permissions of a currently online player and group them by first permission prefixes (i.e. aa.* permissions will be displayed together as well as towny.* ones and factions.* ones etc.)
  
  
• added /aa_playercommands which will list all commands available for the given online player
  
  
• added permission descriptions for WorldEdit and WorldGuard plugins
  
  
• added /aa_ignorecommand and /aa_unignorecommand to add conflicting commands into an ignore list, so you won't see them in the output of /aa_checkcommandconflicts output.
  This can be useful in cases when a plugin on your server is already overriding other plugins for a certain command (let's say /ping) and thus the wanted functionality is there. In such case, AdminAnything will still list those commands as conflicting.
  By using /aa_ignorecommand, you will be able to suppress these commands from showing up in the list of conflicts.

Fixed:

• moved /aa_fixcommand code to its own thread, so it will not potentially lag the server if many plugins are installed
  
  
• fixed output of /aa_disablecommand, /aa_enablecommand & /aa_unfixcommand for instances when the same command was given as a parameter multiple times
  
  
• fixed /aa_disablecommand for 1.6 server versions
  
  
• fixed incorrect permission check for permissions essentials.tpdeny and essentials.kit.others
  
• removed /cc alias for the /aa_clearchat command - I didn't realize it's so close to /ccc (/aa_checkcommandconflicts)

Possible breaking change:

• all permission nodes changed to lowercase (i.e. clearChat changed to clearchat)