Alright, now this is downright annoying. What is it?

[Net_Creator]

Arright. I had a topic a good while ago about my bot trying to do SOMETHING in accordance with a user. Usually when I connect it or join a channel. Well, while I was gone, it spammed an attempt to do this something. And thus, I disconnected. =/ And I only had my back turned for a minute! >_>

[Joe]

I'm guessing that the first section of red text is caused by a bug. Obviously this happened very fast.

The blue section is an unhandled packet, notifying you that you're about to be disconnected for flooding off of battle.net. The next red section is another error, which is handled.

Can you post further backlog to see what all happened?

[Warrior]

Man you guys print out ugly errors.

[Net_Creator]

That was it. The rest of the stuff before that was people in the channel talking. =/ Though, the bot always gets that one error, the one at the top - the one I need some help figgerin' out what the heck is goin' on - whenever I join a channel. Yeah. That one that spammed the screen. The really quick one. The blue text I understood, and the handling error (red text at bottom) I've had happen enough that I understand.

But I can't figger out why it did that. >_>

[Joe]

That's weird. What plugins do you have enabled?

[Net_Creator]

For this one in particular, all of them except advertisements.

[Bud]

the first set of errors that you refer to about the user not being logged on is the same error i get from my greeting plugin.  it seems that the plugin is attempting to message a user using just their name and not name@realm, that is my theory at least after having tested different ways to message people using my bot in my channel.  but  i am at a loss as of how to fix it

[iago]

It almost seems like it's trying to message people for no reason, though. It looks like something is acting weirdly, it might be some of the plugins conflicting with each other or something equally odd.

In terms of your name@realm problem, I actually think it's messaging "name" instead of "*name". Maybe Joe will look into fixing that, he said he's going to work on it this weekend.

[Joe]

Yeah, the *name (aka, D2 name manglings) are on the to-fix list. Not sure if I'll get to it this weekend (prom + end-of-semester drinking), but I'd like to get it fixed sometime soon!

[Bud]

It almost seems like it's trying to message people for no reason, though. It looks like something is acting weirdly, it might be some of the plugins conflicting with each other or something equally odd.

In terms of your name@realm problem, I actually think it's messaging "name" instead of "*name". Maybe Joe will look into fixing that, he said he's going to work on it this weekend.

i have tested the following whisper/message methods using my bot

method                          work
/w (user)                         no       <-works with LOD
/w *(account)                  yes
/w (user)@realm            yes
/m *(account)                 yes
/m (user)@realm            yes
/m (user)                        no       <-works with LOD
/m *(user)                      no       <-doesnt work at all for diablo
the above info is purely for reference for those of you who do not play Diablo II LOD

be advised my bot is using only a classic key not LOD
BUT, the greeting plugin problem happens regardless if using both keys or just 1.  to understand this problem we must discover how the bot is trying to message, whos up to the challenge^^?  i cant seem to find it in the greeting plugin source :(

[Joe]

It's not really hard to find -- http://www.javaop.com/javaop2/src/Greeting/src/PluginMain.java

I'll get on this pretty soon.

[Net_Creator]

My thoughts on this is a function to get such and such data. Log whether the bot is D2 or D2 LoD, and whether it's an Azeroth or USEast (in the case of USEast server, otherwise Lordaeron/USWest and so on) client. LoD and D2 would come back as the Starcraft-style server realms, while only Warcraft III: RoC and Warcraft III: TFT would come back as the Warcraft-style realms. AKA: If the bot is not WC3 or W3XP, then it counts as the SC-style, and if it is, it'll be logged as WC-style. Then the plugin could check if the joining person is WC- or SC-style, and message accordingly. If the bot is SC-style and the joiner is SC-style, it uses a realm void. If they're opposite server styles, it uses the appropriate realm (by calling data from the bot's login plugin on which server it's on) and messages. Only with D2/LoD bots would it require to use the asterisk before a whisper message.

And, yeah, I have no idea how to write that in Java. >_> Darn my downfalls.

[Camel]

That's not how it works; you need to add an asterisk if you've logged in with D2. It doesn't matter how the person you're whispering is logged in as.

The solution I've always used is to rip the asteris out of the username (if on d2) in SID_CHATEVENT recieve, and add them back in to SID_CHATCOMMANDs. I also infer user namespaces (@USEast, @Azeroth), so that the users in the database don't change format when changing products.