Post oper bugs or any unexpected behaviour here. Try to provide as much information as possible in your report.
quick question. when loading the oper plugin and then reconnect or whatever is the plugin suppose to make the oper.cfg, user.txt and the other things or are you suppose to make it?
cause if its suppose to make it its not making it for me :(
all i get is an error in the logs of the folder it created by itself saying
Quote[20:11:38] Loading config...
[20:11:38] Error loading config!
[20:11:38] Loading database...
[20:11:38] Error loading users!
Quote from: Retained on October 16, 2004, 10:14 PM
quick question. when loading the oper plugin and then reconnect or whatever is the plugin suppose to make the oper.cfg, user.txt and the other things or are you suppose to make it?
cause if its suppose to make it its not making it for me :(
all i get is an error in the logs of the folder it created by itself saying
Quote[20:11:38] Loading config...
[20:11:38] Error loading config!
[20:11:38] Loading database...
[20:11:38] Error loading users!
You create them. Documentation explains how.
k thanks for the info i got it working and all and was testing protect. it turns on when i do the command but wont turn off when i do .protect off (my trigger is .)
Quote
[20:52:52] <Retain> .protect on
[20:52:52] <Infinity> Channel protection enabled by Retain
[20:52:55] Retain[iN]@Lordaeron left the channel.
[20:52:55] Retain[iN] was banned by Infinity (channel protection).
[20:52:57] <Retain> :O
[20:52:59] <Retain> .protect off
[20:53:02] <Retain> >_<
[20:53:05] <Retain> Bad bot!
[20:53:09] <Retain> .rejoin
[20:53:09] Infinity left the channel.
[20:53:11] Infinity joined the channel using Starcraft.
[20:53:11] User update: Infinity now has flags 2.
[20:53:19] <To: Retain[iN]@Lordaeron> ^join op infinity
[20:53:19] Retain[iN] was banned by Infinity (channel protection).
[20:53:19] Retain[iN] was banned by Rage (Ban Evasion).
[20:53:22] <Retain> ouch :(
[20:53:22] * /clearqueue
[20:53:24] <Rage> HAHAHAHAH Woops? :D
[20:53:27] <Retain> Hater!!! :D
[20:53:36] <Retain> why wont u turn OFF!
[20:53:39] <Retain> .protect off
[20:53:43] <Retain> .find Retain
[20:53:44] <From: Infinity> retain => Retain: ACDFJLMNOQS
[20:53:47] <Retain> i have every important flag why wont u turn off!
as you can see teh bot hates me :) and doesnt want to turn off protect. either that or i messed up somewhere :D
Quote from: Retained on October 16, 2004, 10:53 PM
as you can see teh bot hates me :) and doesnt want to turn off protect. either that or i messed up somewhere :D
You have to wait a little over a minute before toggling on/off channel protection. This is to prevent people from quickly toggling it on/off/on/off in disagreement.
thanks for the info ;D
my next problem >_< (Sorrie)
the bot doesnt feel like quitting when i tell it to
Quote[21:14:59] <From: Infinity> retain => retain: ACDFJLMNOQS
[21:15:02] <Retain> .quit
[21:15:05] <Retain> I Order you TO QUIT!
[21:15:06] Voyage left the channel.
[21:15:07] <Retain> :(
[21:15:08] * /clearqueue
[21:15:14] <Retain> .quit
[21:15:15] <Retain> .say hi?
[21:15:15] <Infinity> hi?
according to the doc it says quit needs flag Q and i have flag Q
Quote from: Retained on October 16, 2004, 11:15 PM
thanks for the info ;D
my next problem >_< (Sorrie)
the bot doesnt feel like quitting when i tell it to
Quote[21:14:59] <From: Infinity> retain => retain: ACDFJLMNOQS
[21:15:02] <Retain> .quit
[21:15:05] <Retain> I Order you TO QUIT!
[21:15:06] Voyage left the channel.
[21:15:07] <Retain> :(
[21:15:08] * /clearqueue
[21:15:14] <Retain> .quit
[21:15:15] <Retain> .say hi?
[21:15:15] <Infinity> hi?
according to the doc it says quit needs flag Q and i have flag Q
I disable quit command in the public testing builds.
I've been torturing the bot and found 0 bugs..GJ lol
I know this is the wrong place, but I have a "request"...Perhaps you could add an IPBan?
Not interested in feature requests yet, unless they are to do with improving the way the plugin internally operates. The base design is nearing completion, so opened public testing to find any bugs with it before I go on and implement all the other automoderation that I'm planning on doing.
[00:45:04] <LW-Falcon> trigger
[00:45:07] <LW-Falcon> ?trigger
[00:45:08] <LW-Falcon@Azeroth> The Bot's Current Trigger is: '`' (ALT+96)
[00:45:10] <LW-Falcon> [trigger
[00:45:10] LastWarriors@Azeroth:2:47 whispers: Bot trigger is [ (alt 0091)
That kind of defeats the purpose of the trigger command if you need to know the trigger to do the command.
Quote from: Falcon[anti-yL] on October 19, 2004, 12:46 AM
[00:45:04] <LW-Falcon> trigger
[00:45:07] <LW-Falcon> ?trigger
[00:45:08] <LW-Falcon@Azeroth> The Bot's Current Trigger is: '`' (ALT+96)
[00:45:10] <LW-Falcon> [trigger
[00:45:10] LastWarriors@Azeroth:2:47 whispers: Bot trigger is [ (alt 0091)
That kind of defeats the purpose of the trigger command if you need to know the trigger to do the command.
QuoteThe bot has many different built in commands. Commands must be prefixed with a trigger (a dot by default) if spoken outloud, but if whispered, just the command name should be given.
What OS's are you people using when you're testing this plugin?
XP
Quote from: Spht on October 19, 2004, 12:25 PM
Quote from: Falcon[anti-yL] on October 19, 2004, 12:46 AM
[00:45:04] <LW-Falcon> trigger
[00:45:07] <LW-Falcon> ?trigger
[00:45:08] <LW-Falcon@Azeroth> The Bot's Current Trigger is: '`' (ALT+96)
[00:45:10] <LW-Falcon> [trigger
[00:45:10] LastWarriors@Azeroth:2:47 whispers: Bot trigger is [ (alt 0091)
That kind of defeats the purpose of the trigger command if you need to know the trigger to do the command.
QuoteThe bot has many different built in commands. Commands must be prefixed with a trigger (a dot by default) if spoken outloud, but if whispered, just the command name should be given.
He's asking why the command
?trigger doesn't work (or doesn't exist it seems). It seems a bit retarded to have a
<trigger>trigger command (ruins the purpose of the command), and whispering the bot
trigger is redundant.
Quote from: Newby on October 20, 2004, 06:09 PM
He's asking why the command ?trigger doesn't work (or doesn't exist it seems).
That will only work if your trigger is set to '?'.
Quote from: Newby on October 20, 2004, 06:09 PMIt seems a bit retarded to have a <trigger>trigger command (ruins the purpose of the command), and whispering the bot trigger is redundant.
How is whispering the bot
trigger redundant? It is redundant if you already know the trigger, yes. Otherwise, it's a very effective way of finding out what the trigger is set to.
Quote
[15:11:49] Info: xA_Samurai was banned by LW-Falcon (RepeatBan).
[15:13:47] <LW-Falcon> [unban xa*
[15:13:47] LastWarriors@Azeroth:2:47 whispers: No one to unban
[15:13:58] <LW-Falcon> [unban xa_*
[15:13:58] LastWarriors@Azeroth:2:47 whispers: No one to unban
[15:14:10] <LW-Falcon> `u xa*
[15:14:10] Info: xA_Samurai was unbanned by LW-Falcon.
I thought banned users are kepted in memory for 24 hours?
Quote from: Falcon[anti-yL] on October 26, 2004, 03:15 PM
Quote
[15:11:49] Info: xA_Samurai was banned by LW-Falcon (RepeatBan).
[15:13:47] <LW-Falcon> [unban xa*
[15:13:47] LastWarriors@Azeroth:2:47 whispers: No one to unban
[15:13:58] <LW-Falcon> [unban xa_*
[15:13:58] LastWarriors@Azeroth:2:47 whispers: No one to unban
[15:14:10] <LW-Falcon> `u xa*
[15:14:10] Info: xA_Samurai was unbanned by LW-Falcon.
I thought banned users are kepted in memory for 24 hours?
Oper only pays attention to bans/unbans that it did. This is because sometimes Battle.net does not append a gateway tag in someone else's ban/unban notification, so it would be a bad idea to have the bot rely on that.
Also, having a channel with more than one active database-aware client that isn't designed to share a channel is generally a bad idea!
quick question how come when soemone does .say /unloadplugin oper.dll the bot quits and shuts itself down :(
and yes he has the required flag to use the say command ;o
Quote from: Spht on October 20, 2004, 09:20 PM
Quote from: Newby on October 20, 2004, 06:09 PMIt seems a bit retarded to have a <trigger>trigger command (ruins the purpose of the command), and whispering the bot trigger is redundant.
How is whispering the bot trigger redundant? It is redundant if you already know the trigger, yes. Otherwise, it's a very effective way of finding out what the trigger is set to.
How are you supposed to find out what the trigger is, if you have to know the trigger to access a command that tells you the trigger?
Quote from: Newby on November 06, 2004, 01:35 PM
How are you supposed to find out what the trigger is, if you have to know the trigger to access a command that tells you the trigger?
Whisper the bot "trigger". The trigger shouldn't even be changing much anyways. I always see people in channels saying "?trigger", ".find <your name>", why?
simple solution add this line somewhere in oper.cfg
Quote
&5&&<insert required flag for using this command here>&&"?trigger"&:reply Current trigger is [insert trigger here ;)]
or if you don't want the bot to whisper you the trigger do
Quote
&5&&<insert required flag for using this command here>&&"?trigger"&Current trigger is [insert trigger here]
Note: remove the < and > when u do add a flag
Quote from: Retained on November 06, 2004, 05:23 PM
simple solution add this line somewhere in oper.cfg
Quote
&5&&<insert required flag for using this command here>&&"?trigger"&:reply Current trigger is [insert trigger here ;)]
or if you don't want the bot to whisper you the trigger do
Quote
&5&&<insert required flag for using this command here>&&"?trigger"&Current trigger is [insert trigger here]
Note: remove the < and > when u do add a flag
Yup, good thinking! I used this in a channel I run an oper in since so many people try "?trigger."
Quote from: Retained on November 06, 2004, 01:27 PM
quick question how come when soemone does .say /unloadplugin oper.dll the bot quits and shuts itself down :(
and yes he has the required flag to use the say command ;o
Oops. You can re-download oper.dll. It previously processed all commands issued by "masters" through "say" as internal commands. This has been fixed. It now sends everything directly to Battle.net.
Thanks.
Spht:
Is there a command that can be used to process commands internally?
For example:
&5&&Q&&".play"&/play
If it's not available, please consider it.
&5&&Q&&".play"&:internal /play
i got another problem/question.
when i give soemoen the Flag "A" i cant kick them / ban them for some reason any ideas why? and in the operdoc.txt it didnt say anything about flag A being a Safelist flag :(
Quote
[10:08:15 AM] <Retain> .add Cura F
[10:08:15 AM] <From: Retain[iN]@Lordaeron> Cura => Cura: F
[10:09:48 AM] <Retain> .kick cura
[10:09:48 AM] Cura was kicked out of the channel by Retain[iN].
[10:09:49 AM] Cura@Lordaeron left the channel.
[10:09:50 AM] <Presence> LOL
[10:09:50 AM] Cura@Lordaeron joined the channel using Warcraft III: Reign of Chaos (level 0, best race random, icon peon).
[10:09:51 AM] <Retain> .add cura +A
[10:09:52 AM] <^^CooL_GuY^^> <~~ 1 if ny bew ukks
[10:09:52 AM] <From: Retain[iN]@Lordaeron> cura => cura: AF
[10:09:52 AM] <Presence> RAPPER NICE
[10:09:53 AM] <Presence> lol
[10:09:53 AM] <Retain> .kick cura
[10:09:54 AM] <From: Retain[iN]@Lordaeron> cura is safelisted
Quote from: Fyre on November 11, 2004, 04:29 AM
Spht:
Is there a command that can be used to process commands internally?
For example:
&5&&Q&&".play"&/play
If it's not available, please consider it.
&5&&Q&&".play"&:internal /play
I'm pretty sure it sends commands in the action field of a script through the bot's command processor already.
Quote from: Retained on November 11, 2004, 12:12 PM
i got another problem/question.
when i give soemoen the Flag "A" i cant kick them / ban them for some reason any ideas why? and in the operdoc.txt it didnt say anything about flag A being a Safelist flag :(
Quote
[10:08:15 AM] <Retain> .add Cura F
[10:08:15 AM] <From: Retain[iN]@Lordaeron> Cura => Cura: F
[10:09:48 AM] <Retain> .kick cura
[10:09:48 AM] Cura was kicked out of the channel by Retain[iN].
[10:09:49 AM] Cura@Lordaeron left the channel.
[10:09:50 AM] <Presence> LOL
[10:09:50 AM] Cura@Lordaeron joined the channel using Warcraft III: Reign of Chaos (level 0, best race random, icon peon).
[10:09:51 AM] <Retain> .add cura +A
[10:09:52 AM] <^^CooL_GuY^^> <~~ 1 if ny bew ukks
[10:09:52 AM] <From: Retain[iN]@Lordaeron> cura => cura: AF
[10:09:52 AM] <Presence> RAPPER NICE
[10:09:53 AM] <Presence> lol
[10:09:53 AM] <Retain> .kick cura
[10:09:54 AM] <From: Retain[iN]@Lordaeron> cura is safelisted
A and N also make you safe. These are user management attributes which can both add and remove the S flag from an entry anyway. Users with attribute A inherit all flags which they have permission to (BFLS).
Why would you want to boot someone who has user management access over your bot??
Quote from: Spht on November 12, 2004, 02:00 PM
I'm pretty sure it sends commands in the action field of a script through the bot's command processor already.
That would be my fault. I'm running my own BCP supported bot. Basically the queue function was queueing the data to be sent directly, instead of being queued to be sent through the command parser.
Also, quick question: What is the variable for messages received through battle.net, so that a ping feature could be used. I noticed you changed some of the old NBBot variables.
&5&&&&".getlag&/m %3 <ping>
&10&<ping>&&&%1's ping is: %2
This is probably way off, but I think you're getting me.
Also, something useful could be a variable representing the trigger. Instead of the user going through the program and changing all the "." to "?" or whatever, you could use $t or something to represent the assigned trigger.
http://www.madzlair.net/ffs/oper.JPG
-_-
Quote from: Falcon[anti-yL] on November 13, 2004, 10:27 AM
http://www.madzlair.net/ffs/oper.JPG
-_-
Don't clear queue or make bot send messages >= 57 in length. Also, tell Spht to listen to me about some things friends and I researched~
Quote from: Falcon[anti-yL] on November 13, 2004, 10:27 AM
http://www.madzlair.net/ffs/oper.JPG
-_-
That issue would be related to SphtBotv3 for not having the most up-to-date implementation of flood protection. Oper just tells the client what to send, the client then decides when to send each message.
SphtBotv3 was designed as a chatter bot, so the old protection mechanism sufficed. But yes, when using oper with it there could be some problems. If it's a big concern, I suggest trying a client which supports BinaryChat plugins and has implemented flood protection in a way you are satisfied with.
The only bots I know of that supports BinaryChat plugins is FyreChat and SphtBotv3. Could you make it so that when oper is loaded it switches to the "up-to-date" flood protection? Or do you know of a bot that can load oper and has better flood protection?
Quote from: Falcon[anti-yL] on November 13, 2004, 04:09 PMCould you make it so that when oper is loaded it switches to the "up-to-date" flood protection?
No, that is part of the reason why I made this plugin. The plugin just implements the logic, while the hosting client worries about getting on Battle.net and sending messages. This way, the plugin will be forever useful even when changes are made to Battle.net.
Quote from: Falcon[anti-yL] on November 13, 2004, 04:09 PMOr do you know of a bot that can load oper and has better flood protection?
You won't have many problems with the current implementation if you follow the guidelines UserLoser posted.