userlist

[Camel]

yes yoni, but that just helps my argument. i personally havn't even tried to emulate war3 yet; i've just recently gotten back in to botting, and am still working on getting my bot to not skrew up d2dv/d2xp open (it connects but i'm trying to get rid of the charactor@realm*account@server and make it totally transparent as with w2bn/star/sexp). if i were to attempt war3 login, i'm sure i would fail, for i would fall under the category of people who don't know enough about it to do it. there's no "idiot" label on my head, i simply havn't reached that point yet. an "idiot," imho, is one who is unable to reach such places (relatively).
if i were to attempty war3 login, i would probably even look in to bnls. hell, i might even use it. but what seperates the men from the boys is the willingness to ween one's self off of that dependancy. people who use bnls because they cannot do it any other way are idiots. people who use bnls because they're learning are not.

my $0.02

[tA-Kane]

Amen to that.

But, it would be better stated as "People who use BNLS because they don't know how to do it any other way are idiots."

I know *how* to login without using BNLS, but I cannot do so because I'm unable to get the creation date of the Starcraft application, (required for CheckRevision). I *could* hard-code the creation dates into my bot, or perhaps have it get sent over BotNet, but I don't like that idea.

[Zakath]

Incidentally, the easiest way to handle D2 users is to check usernames to see if they contain '*', and, if so, parse out anything that may appear before it. Not perhaps ideal for all situations, but it works:

Code Select Expand

if ( strrchr( name, '*' ) != NULL && name[0] != '*' )
            strcpy( name, strrchr( name, '*' ));

[Camel]

yes, but it's more complicated
it automaticly chops off everything before the * on all 0xF packets. that part works fine. the problem is that any function that whispers a user needs to re-add that *. i pretty much have it down, i'm just not sure if its buggy or not

[Zakath]

Oh, eww...don't get rid of the * - it IS part of the username for D2 clients.

I just get rid of the character name:
[15:39:28] *Mizzle is here using Diablo II: Lord of Destruction (Miztyk, a level 23 barbarian on realm USEast), with a ping time of 79ms and flags of 0.

That's much better than "Miztyk@USEast*Mizzle", don't you think?

[Camel]

it is not part of the username--it just designates what comes after it as a username rather than a charactor name. id sort of needs to be done, because of the way i have users and ranks set up. my bot is and always has been intented to be an ops bot. making it a good chat bot will always be secondary. it's amazing how many people try to tell the bot to "add charactor*user@realm" when the bot is clearly on starcraft.

[Zakath]

No, the * is part of the username. If you are not logged onto a realm (or the realm is lagged and isn't keeping up) you will show up simply as *Account.

[00:41:26] *GoddessLarissa joined the channel using Diablo II (Open character), with a ping time of -1ms and flags of 0.

However, for an opbot, that's a problem. The solution most use is simply not to have their opbots use D2 clients.

[Skywing]

No, the * is part of the username. If you are not logged onto a realm (or the realm is lagged and isn't keeping up) you will show up simply as *Account.

[00:41:26] *GoddessLarissa joined the channel using Diablo II (Open character), with a ping time of -1ms and flags of 0.

However, for an opbot, that's a problem. The solution most use is simply not to have their opbots use D2 clients.

Yes.  Not to mention problems with the server being inconsistant about including character name (and even asterisks) in ban/unban/kick messages.

[Camel]

The solution most use is simply not to have their opbots use D2 clients.

so what, you want me to do what everyone else is doing? i'll stick with my code, thx.

edit: and i wanna have ops as BNU-Bot*Camel[DA]@USEast