MeTroiD wrote:If you can list some of ChanServ's functions like that SOP, AOP thing and some other functions it has and show me the output it gives on those things. for example
/msg ChanServ SOP #channel
-ChanServ- SOP List for #channel
-ChanServ- User
-ChanServ- User
-ChanServ- End of list.
I have no idea how it looks like really :p
If you give me all those things, i might just make a simple version of a chanserv.
This is complicated, however it requires keen skills. For instance take, we would define our own custom user flags, +F for founder, +S for sop, +A for aop.
Now say we make a proc, let it bind on msg, notc trigger /chanserv <aop|sop> #channel <add|del> whatever you want. We would do say 3-4 checks on the user flag and go ahead and instruct chanserv todo the following.
Remember now the msg or notc bind will trigger when you add and delete a user. If matchattr is F, chanserv can add|del aop|sop. If matchattr $hand is S chanserv can add|del aop. If matchattr $hand is +A chanserv cannot add|del anything on that channel.
Now the difficult part is, to create user lists, maybe write to a text file and read from there, or add seperate user levels for each flag. For the chanserv aop|sop list. Or they can create arrays and store nicks and hostmasks and display chanserv aop|sop lists in those and check users access from those arrays when a trigger is activated, wheter chanserv can execute it or access is denied.
Like for each user level there would be a bind join, to op them, and for AKICK the bind join would kick/ban those users.