Post: #27

About the say/unicode/blahblah issue: i downloaded the latest sphere svn build and the text encoding for speech is not ascii anymore but unicode.
So, i looked for the differences from the speech (visualized correctly, in yellow) and the SAYU command related packets:

Speech ("test")

SAYU (".sayu test")

The main differences i noticed are:
Speech -> "mode" byte: 00
Speech -> "color" word: 00 34
SAYU -> "color" word: 03 B2
SAYU -> "mode" byte: 03 which is, huh? i don't find it in the packet guide.
The modes which i found are:
(0x00 = say, 0x01 = system, 0x02 = emote, 0x06 = label, 0x07 = focus, 0x08 = whipser, 0x09 = yell, 0x10 = spell, 0x13 = guild, 0x14 = alliance, 0x15 = GM, 0xC0 = encoded commands)

Is this useful?


EDIT: a question, it might not be a problem but is just to have a clearer vision.
In order to have a visual effect, i use the c0 packet, and it works:
sendpacket 0c0 02 D(00) D(00) W(i_fire_column) W(<p.x>) W(<p.y>) B(<p.z>) w(0) w(0) b(0) 00 b(16) w(00) 00 00 d(04) d(1)
The last dword is the render (though i don't see this in any packet guide, if i don't write it the client would block), the penultimate dword is the color.
Why with spyuo i see the render as a byte instead of a dword?
If i use
sendpacket 0c0 02 D(00) D(00) W(i_fire_column) W(<p.x>) W(<p.y>) B(<p.z>) w(0) w(0) b(0) 00 b(16) w(00) 00 00 d(04) 01
treating the render as a byte, client freezes. Same happens omitting the render.

Re-EDIT: oh, nothing, it is just because the most significant byte is on the right