Example:
I have a command nfo <dirname> which get's information about a scene dirname.
However, the same can be triggered by a dirname in irc.received.privmsg parsed by RegEx:

<hashworks> !nfo Rayman.Legends.MULTi13-PROPHET
<Phergie> Here is some information about Rayman.Legends.MULTi13-PROPHET.
<hashworks> Check out Rayman.Legends.MULTi13-PROPHET!
<Phergie> Here is some information about Rayman.Legends.MULTi13-PROPHET.

The problem is that the plugin needs to determine duplication by itself, otherwise it will react on both command.nfo and irc.received.privmsg:

<hashworks> !nfo Rayman.Legends.MULTi13-PROPHET
<Phergie> Here is some information about Rayman.Legends.MULTi13-PROPHET.
<Phergie> Here is some information about Rayman.Legends.MULTi13-PROPHET.

I solved this by avoiding PRIVMSGs with nfo in the message, however this isn't the best solution.

Instead of listening on irc.received.privmsg one should be able to listen to a event that indicates that no command event was emitted, f.e.:

• no.command
• no.command.privmsg
• no.command.notice

This plugin could use the plugin.all event to get access to the full list of plugins and check the return values of their getSubscribedEvents() implementations to see what commands are supported and which plugins support them.

It could also use the Command plugin to implement an actual "help" command, which could fire a command.COMMAND.help event that plugins implementing commands could listen for and respond to, allowing Command plugin developers to maintain their own documentation inline with plugin code.