It's not listed on BnetDocs :*(
Does anybody have it at Ladder HC?
Quote from: R.a.B.B.i.T on January 27, 2004, 07:25 PM
It's not listed on BnetDocs :*(
Does anybody have it at Ladder HC?
Explain what you mean any maybe we (Atleast, I) can understand you
HAH. I got it with some help from Andy (or rather, he just told me). I meant the byte that would allow my bot to recognize a ladder character from a non-ladder during stat-string parsing.
(As it turns out, Byte 26 value 0x40 is a ladder character.)
Quote from: R.a.B.B.i.T on January 28, 2004, 09:53 AM
HAH. I got it with some help from Andy (or rather, he just told me). I meant the byte that would allow my bot to recognize a ladder character from a non-ladder during stat-string parsing.
(As it turns out, Byte 26 value 0x40 is a ladder character.)
I'm pretty sure it's not _value_ 0x40, it's the bit, i.e: (byte && 0x40) != 0
Quote from: K on January 28, 2004, 12:09 PM
Quote from: R.a.B.B.i.T on January 28, 2004, 09:53 AM
HAH. I got it with some help from Andy (or rather, he just told me). I meant the byte that would allow my bot to recognize a ladder character from a non-ladder during stat-string parsing.
(As it turns out, Byte 26 value 0x40 is a ladder character.)
I'm pretty sure it's not _value_ 0x40, it's the bit, i.e: (byte && 0x40) != 0
Right, considering it's also used for detecting a hardcore character.
Quote from: K on January 28, 2004, 12:09 PMI'm pretty sure it's not _value_ 0x40, it's the bit, i.e: (byte && 0x40) != 0
Correction: byte
& 0x40 /* single ampersand for bit test, double ampersand for truth evaluation */
BAH! It works for me. It might have been 0x80, I didn't look at it for a while when I posted (I still haven't).
Quote from: Kp on January 28, 2004, 03:28 PM
Quote from: K on January 28, 2004, 12:09 PMI'm pretty sure it's not _value_ 0x40, it's the bit, i.e: (byte && 0x40) != 0
Correction: byte & 0x40 /* single ampersand for bit test, double ampersand for truth evaluation */
Righto -- what was I thinking? I actually went back and replaced the single amperstand with a double after I finished writing.
Quote from: R.a.B.B.i.T on January 28, 2004, 05:46 PM
BAH! It works for me. It might have been 0x80, I didn't look at it for a while when I posted (I still haven't).
I told you it was a bitwise And comparison. :)
Shhh...I've forgotten about it completely by now and moved on to other problems...