WoW:ValidChatMessageCharacters - Revision history

Move page script: Move page script moved page ValidChatMessageCharacters to WoW:ValidChatMessageCharacters without leaving a redirect

2023-08-15T04:49:16Z

Move page script moved page ValidChatMessageCharacters to ValidChatMessageCharacters without leaving a redirect

← Older revision

Revision as of 04:49, 15 August 2023

WoWWiki>Corwin MacGregor: /* Allowed Characters */ byte 124 causes disconnects in patch 3.1.3

2009-07-31T05:59:08Z

Allowed Characters: byte 124 causes disconnects in patch 3.1.3

← Older revision		Revision as of 05:59, 31 July 2009
Line 31:		Line 31:
	\| 32 - 123 \|\| ''standard ASCII'' \|\| ok (don't forget the character sequences '%t' and '%f': they will be replaced by your target's / focus's name or something like "<no target/focus>" - or a localized equivalent)		\| 32 - 123 \|\| ''standard ASCII'' \|\| ok (don't forget the character sequences '%t' and '%f': they will be replaced by your target's / focus's name or something like "<no target/focus>" - or a localized equivalent)
	\|-----		\|-----
	\| 124 \|\| <nowiki>\|</nowiki> \|\| ERROR "invalid escape code in chat message"		\| 124 \|\| <nowiki>\|</nowiki> \|\| ERROR "invalid escape code in chat message" (causes DISCONNECTs in patch 3.1.3)
	\|-----		\|-----
	\| 125 - 126 \|\| ''standard ASCII'' \|\| ok		\| 125 - 126 \|\| ''standard ASCII'' \|\| ok
Line 39:		Line 39:
	\| 128 - 255 \|\| ? \|\| ERROR "chat message must be UTF-8 text" possible		\| 128 - 255 \|\| ? \|\| ERROR "chat message must be UTF-8 text" possible
	\|}		\|}


	== Notes ==		== Notes ==

WoWWiki>Ohklus at 15:10, 29 September 2008

2008-09-29T15:10:21Z

← Older revision		Revision as of 15:10, 29 September 2008
Line 29:		Line 29:
	\| 14 - 31 \|\| ? \|\| ok		\| 14 - 31 \|\| ? \|\| ok
	\|-----		\|-----
	\| 32 - 123 \|\| ''standard ASCII'' \|\| ok		\| 32 - 123 \|\| ''standard ASCII'' \|\| ok (don't forget the character sequences '%t' and '%f': they will be replaced by your target's / focus's name or something like "<no target/focus>" - or a localized equivalent)
	\|-----		\|-----
	\| 124 \|\| <nowiki>\|</nowiki> \|\| ERROR "invalid escape code in chat message"		\| 124 \|\| <nowiki>\|</nowiki> \|\| ERROR "invalid escape code in chat message"

WoWWiki>Charibot: catfix, Replaced: {{wowapitype}} → {{wowapitype}}

2008-07-15T00:56:01Z

catfix, Replaced: {{wowapitype}} → {{wowapitype}}

← Older revision		Revision as of 00:56, 15 July 2008
Line 1:		Line 1:
	{{wowapitype}}		{{wowapitype}}<br>

	[[API SendChatMessage\|SendChatMessage]] cannot send all characters (or better call it 'bytes')!<br>		[[API SendChatMessage\|SendChatMessage]] cannot send all characters (or better call it 'bytes')!<br>

WoWWiki>Ohklus: Page created

2007-12-28T14:33:19Z

Page created

New page

{{wowapitype}}

[[API SendChatMessage|SendChatMessage]] cannot send all characters (or better call it 'bytes')! 
Of course normal text - you would type in a custom channel - is supported, but some characters you might want to send by an addon can cause an error or - even worse - disconnect the player. 
 
These are the characters that appear to be allowed for "msg" in [[API SendChatMessage|SendChatMessage("msg"{,"type"{,"lang"{,"channel"}}})]].

== Allowed Characters ==
 
(use [[API strchar|strchar(charID)]] to construct a char out of its decimal representation and [[API strbyte|strbyte("text" [, index])]] to do the reverse thing) 
 

{|
|-----
| width="120" height="17" | '''ID'''
| width="320" | '''Printout''' [by ChatFrame1:AddMessage(strchar(ID))]
| width="400" | '''Note'''
|-----
| 0 || ''none'' (terminates string) || complete message ignored (not sent)
|-----
| 1 - 9 || ? || ok
|-----
| 10 || ''new line'' (line feed) || DISCONNECT
|-----
| 11 - 12 || ? || ok
|-----
| 13 || ''new line'' (carriage return) || ok
|-----
| 14 - 31 || ? || ok
|-----
| 32 - 123 || ''standard ASCII'' || ok
|-----
| 124 || <nowiki>|</nowiki> || ERROR "invalid escape code in chat message"
|-----
| 125 - 126 || ''standard ASCII'' || ok
|-----
| 127 || ? || ok
|-----
| 128 - 255 || ? || ERROR "chat message must be UTF-8 text" possible
|}

== Notes ==

I tested each character by sending it to a custom channel named "test". Then I converted the received character to its ID and compared it with the original ID. 
Especially on a byte-per-byte basis [[API SendChatMessage|SendChatMessage]] has its restrictions (beside the 255 character - better say byte - thing). 
 
Be very careful with splitting a UTF-8 text! You can end up with unexpected UTF-8 errors. 
 
According to UTF-8: the error described above is not a big problem if your addon doesn't split a UTF-8 character into its byte-parts (I had the problem while automatically splitting messages that exceeded the maximum of 255 bytes!) 
 
[[API SendAddonMessage|SendAddonMessage]] does not have any of those byte problems (except 0000 0000 and forbidden "\t" in prefix).