Post: #21

(03-17-2014 07:35 AM)karma Wrote:  Great! It works with EC! Many thanks Xun!
Do you (or anyone) know if RunUO has better packet support or should i create a trial account on EA?

(03-17-2014 07:59 AM)XuN Wrote:  AFAIK RUO has support to almost all packets.

RunUO currenctly support every classic client packet from 3.0.6 to the newest (but not the new movement F0/F1) (also support 3.0.5 and older, but does need core mod to not send OPL packets)
There is a guy on RunUO that is working on EC client.
Once you get basic support, you get everything. There are about 15 packets that are slightly different from classic client. The main changes are the slot-based containers, character creation, some macro requests and status info

If anyone is interest on seeing what changed in terms of packets:
http://www.runuo.com/community/threads/e...st-3981943

Post: #22

Well, some of you are softcoding these packets (and speedhack control) and helping a lot in the proccess so i'm more interested on the rest of the packets, i've sent yesterday the new animation's packet and i'm checking out now the boats packets so step by step we can improve Sphere, any help with packets will be more than wellcome

Post: #23

For the "dclick and equip weapon" bug: when dclicking the weapon from ground it seems to be equipped but it remains on the ground, as said previously. Dragging it on the paperdoll instead of dclicking result in the appropriate behavior, making the weapon disappear from ground. Analyzing the traffic, it seems to me that, after dclicking the object, the packet F3 (world object) is not sent (in the other situations it is), maybe is it to cause the bug?

Also, i noticed that saying things with RUO sends the unicode packet, instead of the ascii one sent by Sphere.
SAYU Sphere command shows a violet-purple sysmessage, and, while the language of the RUO unicode message shown by SpyUO is ENG, the language of the Sphere unicode message is not shown, it's a blank string, so may the error lie here? May the language specified in the packet be invalid?

@Feeh, do you know how to say colored things or show colored effects (like with the EFFECT function in Sphere) in game with RUO? Just to make some tests

Post: #24

(03-18-2014 12:38 AM)karma Wrote:  Also, i noticed that saying things with RUO sends the unicode packet, instead of the ascii one sent by Sphere.
SAYU command Sphere shows a violet-purple sysmessage, and, while the language of the RUO unicode message shown by SpyUO is ENG, the language of the Sphere unicode message is not shown, it's a blank string, so may the error lie here? May the language specified in the packet be invalid?

@Feeh, do you know how to say colored things or show colored effects (like the EFFECT function in Sphere) in game with RUO? Just to make some tests

RunUO does use the unicode packet by default, it also supports the ascii one, but you kinda have to force it.
The language should be used by the client's internal translator, which seems to be removed from the game (RunUO send ENG\0 and Sphere send \0\0\0\0 // there is no invalid language, here I get PTB\0 )
About the messagle color, RunUO send it 0x3b2 hued by default and (AFAIK) sphere send the 0 hue . Either check your client options for some violet-hued message or it may be a internal sphere glitch

Since RunUO does not have any (script/code)-parser, you cannot use .effect/.say command in RunUO as you do with Sphere. The best you can do is create those commands & test em OR if you are used to C# and RunUO coding style, you can create the parser to call the code (time consuming)

(03-17-2014 07:32 PM)XuN Wrote:  Well, some of you are softcoding these packets (and speedhack control) and helping a lot in the proccess so i'm more interested on the rest of the packets, i've sent yesterday the new animation's packet and i'm checking out now the boats packets so step by step we can improve Sphere, any help with packets will be more than wellcome

The new boat moving packet can be found in RunUO, I suggest you to look at RunUO source and see how they've implemented it. The boat control packets are not present, but it should not be any hard to implement them
If needed I can try to describe how these packets works on RunUO

Post: #25

(03-18-2014 02:53 AM)Feeh Wrote:  About the messagle color, RunUO send it 0x3b2 hued by default and (AFAIK) sphere send the 0 hue . Either check your client options for some violet-hued message or it may be a internal sphere glitch

Therefore i'll try to compare in more detail the two packets sent.

Quote:Since RunUO does not have any (script/code)-parser, you cannot use .effect/.say command in RunUO as you do with Sphere. The best you can do is create those commands & test em OR if you are used to C# and RunUO coding style, you can create the parser to call the code (time consuming)

I know a little about C# but nothing about RUO.. Can you link me a guide to write the simple command i need, or if it's a fast work can you write me the code (and the file where should i put it)? I think PMs are more appropiate for this things, unless XuN or others say it is ok.

Post: #26

For RUO code you should use PMs, there's no need on showing it here.

About EC and DClick items, theF3 packet may be the issue since it's a newer packet and i'm almost sure it's not used in the DClick() hardcoded function.

For Ascii/Unicode I don't feel like touching it right now, maybe Ben can take a look over it.

And for the color, is there a base packet for text? Any new one being used? Or just an old packet tricked to show color?

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

Post: #28

This 'problem' is related to the fact that sphere is only sending text, the client speech color is handled by client and not by server so there's no way to make sphere sending text with the color of your speec because its automatically handled by your client and not ever sent to the server.

And for the mode:

Post: #29

And for the mode byte?
(I have edited the post above to add something few seconds ago lol)

EDIT: ok, but why with mode 00 the text is like speech, over the char, and with 03 it sends a sysmessage?
I can be wrong but this is what i found with spyuo and some testing

Post: #30

(03-18-2014 02:53 AM)Feeh Wrote:  The new boat moving packet can be found in RunUO, I suggest you to look at RunUO source and see how they've implemented it. The boat control packets are not present, but it should not be any hard to implement them
If needed I can try to describe how these packets works on RunUO

Some help with this would be nice, at least a point on where should I look.