I've rewritten the private group module. It relies completly on the access control management for access rights. And I've added settings for join/leave notifications. Personally I think those should be in the module managing the private group, not somewhere else. The location of the notifications can be set by settings. In addition to this the whole private group can be disabled by an setting.

The join/leave notification are done by parsing the settings strings Privgroup.Joinstring and Privgroup.Leavestring. The parser replaces any tag of the format #!FIELD!# correlating to an field name of the return of the whois cache with the information of that field, as well as replacing #!BOTNAME!# with the name of the bot.

.phps file rename to .php

Note: if you use this module with the current relay version, you should disable the join/leave notifications in one of the modules to avoid double spamming.

Commands:

• join invites the caller to the chat group
• chat same as join
• leave kicks the caller from the chat group if he joined it
• invite same as join
• inviteuser name invites name to the chatgroup
• kick same as leave
• kickuser name kicks name from the chatgroup
• kickall kicks all from the chatgroup

The configurable join/leave strings are a nice feature, but I'm not sure it's neccessary. We don't want to create an "inner platform effect" (thedailywtf.com) where, in the end, we impliment so much configuration and stuff that we could just aswell eval() everything coming in on the chat.

It's definitly debateable. Personal I just got sick of having to have different notify files for my different bots just because some people want more or less information. This way now I can just change it at runtime.

Looks nice. I'll play around with it some today or tomorrow.