| Author | Message | Time |
|---|---|---|
| Freeware | Ok here is all the text colors. Use them with caution, they will probably be the next thing disabled (and maybe banned) by battle.net. Public Const BNETGreen = "ÁR" Public Const BNETGrey = "ÁQ" Public Const BNETYellow = "ÁZ" Public Const BNETRed = "ÁY" Public Const BNETBlue = "ÁV" | September 3, 2003, 10:15 PM |
| Kp | [quote author=Freeware link=board=17;threadid=2568;start=0#msg20013 date=1062627318]Ok here is all the text colors. Use them with caution, they will probably be the next thing disabled (and maybe banned) by battle.net. Public Const BNETGreen = "ÁR" Public Const BNETGrey = "ÁQ" Public Const BNETYellow = "ÁZ" Public Const BNETRed = "ÁY" Public Const BNETBlue = "ÁV"[/quote]Perhaps you should think and/or read back before posting? The ability to color chat appeared because of flawed UTF8 decoding in SC/BW. The other clients do not implement UTF8, and are therefore unaffected - they see exactly the characters you pasted. IIRC, this was discussed in some depth when it first came out. I don't see why they'd bother banning you for sending those codes - seems like a waste of effort. As for 'disabled', that will likely happen when/if they fix their decoding in the client. | September 3, 2003, 10:20 PM |
| St0rm.iD | [ot] and on a side note...your sig sucks. | September 4, 2003, 12:17 AM |
| UserLoser | [quote author=St0rm.iD link=board=17;threadid=2568;start=0#msg20032 date=1062634677] [ot] and on a side note...your sig sucks. [/quote]it's totally incorrect! | September 4, 2003, 12:33 AM |
| Camel | Not only is it incorrect, but he didn't even bother to indent or cast Header as a specific type! | September 4, 2003, 5:58 AM |
| kamakazie | [quote author=Camel link=board=17;threadid=2568;start=0#msg20101 date=1062655103] Not only is it incorrect, but he didn't even bother to indent or cast Header as a specific type! [/quote] Then Header is a variant? | September 4, 2003, 6:15 AM |
| Camel | Yes; an unused variant. | September 4, 2003, 6:22 AM |
| iago | Not to mention he uses an incorrect c-style hex variable, 0xFU. | September 4, 2003, 9:45 AM |