Currently, most modules register each channel (gc, pgroup, tell, tell2) individually. We're already discussed removing tell2, but how about removing all four command registrations and simplifying to a single handler?

With the new Security and Access Control modules, I think this would be a good change for 0.4. Access Control does one thing that I don't really like: it overrides the intentions of the developer.

For example, my the !apf module by default allows anyone to use the !apf command anywhere. That was by design. Access Control can completely change my intentions and restrict access.

Giving the user (the person running BeBot) control is excellent software design, but as we are not just creating a useful program we're also creating a development framework, we also need to empower the developer.

Here is what I suggest:
Add the ability to register a new command via a function call (ie: $this -> bot -> new_command("name")). This function should take care of registering the command for all channels.

Secondly, the Access Control module should provide functionality to allow the module developer to set the default access for the command. Instead of new command getting the default settings Access Control dictates, the new command should get the default settings that the module developer dictates.

Functionality similar to the create() function in the Settings module is what I'm looking for. The default access settings are created if they don't already exist, but if access settings do exist the stored values are used over the defaults the developer has set.

A single unified handler should be able to pass along the source of the message. There is currently a general output function in Bot.php that takes a channel parameter to determine if output should be sent via tell, pgroup, or gc.