There haven't been too many bugs after the rewrite but there were some. So here's what's been discovered thanks to our new testing and static analysis procedures

Version 1.7.1
=============
New major version.

Fixed:

• /aa_mutecommand could attempt to modify server classes twice when ran for the first time after a server restart and there are some commands muted already
• /aa_addperm did not show confirmation message on successful permission creation
• /aa_addperm did not check for existence of the command we are adding permissions for
• /aa_addredirect did not check for existence of commands
• /aa_fixcommand and /aa_addredirect will now correctly add commands to overrides/redirects lists when these commands are provided with strange letter case.
  Example: /aa_addredirect GoD help -> is now same as writing /aa_addredirect god help (would not allow to remove the GoD redirect before, as it wouldn't find it on the server)
• removed some forgotten debug lines from AdminAnything's output

Added:

• missing features added to the configuration, so you can enabled/disable them as all the others. Added were config options for /aa_actions, /aa_reload and /aa_version commands.
• new configuration section "banIpCommands" was added that holds list of all commands used on the server to IP-ban players. This is used when the "kick after IP-ban" feature is enabled, so AdminAnything knows after which command(s) to kick a player out.
• on old servers (prior to Minecaft 1.6), all of the clickable chat link features will be auto-disabled on first run to prevent showing unnecessary warning messages, since these features will never work there
• new configuration section "pluginsWithFullWriteAccessViaAPI" with an appropriate enabling config option "features.apifullaccess.enabled" was added (disabled by default). What this does is it allows other plugins to access custom events of AdminAnything that are used to update lists of fixed, muted, disabled... commands. In other words - when this is enabled, other plugins that you allow in this config section will have the ability to alter AdminAnything's fixed, muted, disabled... commands lists completely. Use with care and only when strictly necessary. Always consider what this can cause to the stability of AdminAnything and subsequently your server if a plugin's author asks you to add their plugin into this list.

Updated:

• the second parameter of /aa_fixcommand can now be the plugin name itself - no need to write the full "PluginName.commandName" crap if we know we're fixing "god" to "Essentials:god"
  Example: /aa_fixcommand god Essentials -> this now is the same writing /aa_fixcommand god Essentials.god