This is the message, it IS being sent to bnet & recieved by the regular SC client, but it isn't displayed, any idea why?  Maybe the » character?
[quote]
CrAz3D-»LIPOXAMGSF Added by:CrAz3D[xL][/quote]

Debugoutput() it, look for nasty low-ascii characters, because » is safe to use (I use it a lot).

[quote author=rabbit link=topic=10646.msg100751#msg100751 date=1108960385]
Debugoutput() it, look for nasty low-ascii characters, because » is safe to use (I use it a lot).
[/quote]low-ascii?

< 32

From what I see, my ascii characters range from 32 to 122.  Any other ideas on why the SC client isn't displaying the text?

[quote author=CrAz3D link=topic=10646.msg100808#msg100808 date=1109001495]
From what I see, my ascii characters range from 32 to 122.  Any other ideas on why the SC client isn't displaying the text?
[/quote]
Hmm, all of my characters are 32 & above.

EDIT:

» isn't safe to use.  When sending » from my REAL SC client to bnet, the bot client recieved ».  » is an invalid character for bnet now.  So, AFAIK, characters of 187 or higher are invalid for the SC client.  I haven't tested characters lower than 187 & higher than X, but I tested a few higher than 187.

Perhaps its just a bug in starcraft?

Its not a bug, its actually them fixing a bug. The reason color codes were ever avaiblie was from a bug. And that but also assisted in allowing those charactors.

In a stupid attempt to fix colors they screwed up some chars? Lol.

Isn't that AWESOME!  Go B.NET!

No, in a successful attempt to fix colors they require you to actually emulate the client a bit better now.  As was posted about several versions ago, Starcraft uses UTF8 coding of characters.  Sending a bare » is wrong.  You should be sending it encoded in UTF8, as Starcraft does.  That it worked at all since the switch to UTF8 is arguably a bug, which is now fixed.

[quote author=Kp link=topic=10646.msg101072#msg101072 date=1109110720]
No, in a successful attempt to fix colors they require you to actually emulate the client a bit better now.  As was posted about several versions ago, Starcraft uses UTF8 coding of characters.  Sending a bare » is wrong.  You should be sending it encoded in UTF8, as Starcraft does.  That it worked at all since the switch to UTF8 is arguably a bug, which is now fixed.
[/quote]How would I send my text as UTF8 code?

[quote author=CrAz3D link=topic=10646.msg101087#msg101087 date=1109114643]
[quote author=Kp link=topic=10646.msg101072#msg101072 date=1109110720]
No, in a successful attempt to fix colors they require you to actually emulate the client a bit better now.  As was posted about several versions ago, Starcraft uses UTF8 coding of characters.  Sending a bare » is wrong.  You should be sending it encoded in UTF8, as Starcraft does.  That it worked at all since the switch to UTF8 is arguably a bug, which is now fixed.
[/quote]How would I send my text as UTF8 code?
[/quote]

Assuming you're using Windows, MultiByteToWideChar() and WideCharToMultiByte().  Otherwise, if you're going to use Storm.dll you could use (If I remember correctly) Storm ordinal 912.

Thank you much, I will look into that.

EDIT: Would I have to send it differently for D2, W2, & W3?

[quote author=CrAz3D link=topic=10646.msg101090#msg101090 date=1109114919]
Thank you much, I will look into that.

EDIT: Would I have to send it differently for D2, W2, & W3?
[/quote]

No, they all use UTF-8

[quote author=iago link=topic=10646.msg101143#msg101143 date=1109130797]
[quote author=CrAz3D link=topic=10646.msg101090#msg101090 date=1109114919]
Thank you much, I will look into that.

EDIT: Would I have to send it differently for D2, W2, & W3?
[/quote]

No, they all use UTF-8
[/quote]Okely dokey!, Thanks