Well a seperate table for rooms for people modifying this chat system would be a lot easier for them, however it means extra queries, and i push myself to the limit when it come's to reducing server strain to a minimal, this chat system is extremely optomized and i have yet to see it crash my server, or even make it a little slower. So unfortunatly the serialized array will stay in place, you can still do everything, but it does make things a little more difficult.
Admin's are allowed to dis-allow usergroups from accessing certain rooms? Sounds good to me, i'm guessing as default any rooms created by members would be accessible by all? If so it sounds good, i may wait untill v2.3 for that though.
The issue with that is very easy to fix, i'll just make it so when a room is deleted via ACP or the auto prune, it just prunes that room's messages with it
Changing straight to chat room, sounds good to me, no need to change the program, notice that if "nojoin=1" is within the URL, the message to say they have joined will not occur
Permanent change in ACP control, yes that should of been in, it completely escaped my mind. I'll do that for v2.2
A change log, hmm, i sometimes change the same thing 3 or more time's, i think what would be better is a program to differentiate the differences between the 2 files, many use it on here to see what changes vBulletin made to upgrade to the newest version, one program i know of is here:
http://www.araxis.com/, or if you want the direct .exe file link:
http://www.araxis.net/files/merge60_win32_evl.exe
I hope that will help you, i believe it would make things easier for you and me in that respect
Time to start on v2.2 i believe...
- Zero Tolerance