These are very simple public triggers. I doubt you wouldn't find them on the web. Public commands such as lolz tools would be able to fulfil your requirements.Stupidman wrote:all outdated, i'm not that stupid why would i ask without looking first im just stupid enough
I don't think it is hard to write these type of scripts, in which the proc only consists of a 2-3 lines, heh. Nonetheless, here is an example op script:!op (Gives Op @ Sign)
!deop (Takes away Op +o Sign)
!voice (user) (Gives the Voice +v symbol)
!devoice (user) (Takes away the Voice + Symbol)
!halfop (user) (Gives the Halfop % symbol)
!dehalfop (user) (Takes away the Halfop % symbol)
!kick name reason (kicks the user from the channel)
!ban nickname (bans the nickname from the channel but doesnt kick)
!bk nickname reason (bans and kicks together the nickname)
Code: Select all
bind pub - "!op" op:user
proc op:user {nick uhost hand chan text} {
putserv "MODE $chan +o $nick"
}
This could pose a problem, since there are only a few ways to check who can and who can not use the commands with eggdrop. 1 by checking if the person is oped, halfoped or voiced on the channel. 2 by checking if the person has a serton flag in the bots userfile. As well as a few that will use a login system, just depends on how secure you want the script to be. But going from a channel access (ChanServ sop,aop,hop,vop list(s) ...access) could be a problem for the bot, since it has no way of knowing who is actually on the channel's access list, not to mention what level they have. I would really take Alchera Advice and search for a command script that suits your needs best.The tcl should allow only ops with chanserv access (aop, sop, etc) to have access to the commands
The only thing that limits someone use of scripts from the TCL Archive is the bot version, this is due to it using commands that are only available in newer version of eggdrop irc bots.all outdated
For this you can use the ChanServ WHY command (as available in DALnet services). It shows if a user has access on a channel (if he has access, shows the access level FOUNDER/SOP/AOP), if he doesnt it returns NO.TCL_no_TK wrote:Yo!This could pose a problem, since there are only a few ways to check who can and who can not use the commands with eggdrop. 1 by checking if the person is oped, halfoped or voiced on the channel. 2 by checking if the person has a serton flag in the bots userfile. As well as a few that will use a login system, just depends on how secure you want the script to be. But going from a channel access (ChanServ sop,aop,hop,vop list(s) ...access) could be a problem for the bot, since it has no way of knowing who is actually on the channel's access list, not to mention what level they have. I would really take Alchera Advice and search for a command script that suits your needs best.The tcl should allow only ops with chanserv access (aop, sop, etc) to have access to the commandsThe only thing that limits someone use of scripts from the TCL Archive is the bot version, this is due to it using commands that are only available in newer version of eggdrop irc bots.all outdated
My services have no such command for chanserv, I think that only applies to Auspice services (which is only one of many).awyeah wrote:For this you can use the ChanServ WHY command (as available in DALnet services). It shows if a user has access on a channel (if he has access, shows the access level FOUNDER/SOP/AOP), if he doesnt it returns NO.