This is extremely useful, except I am clueless on how to implement it.SaveGame wrote:Nah, it's the default MSU that deals with it. Thanks for pointing this out, this means that 'skill usage type' must have been introduced in C2 (I have first observed it on C4 due to reasons related to my testing methodology).RogerSmith wrote:Sorry to Hijack your thread, but it seems like you know what you are doing -
I am looking to fix swoop cannon skills 5110 and 5111. I can do the geometry calcs server side, but I have a problem with direction the animation (never goes to target, always to one place in the map, always same direction).
I am curious - have you ever came across any special packet in regards to these animations? I suspect their physics is done client side, then information regarding flight path and collision are sent to server and maybe other clients in proximity. I assume this because cloak simulation is done client side, you can supposedly tamper with this?
Here's an example (in front of Gludio castle, Gracia Final server)
Code: Select all
48 79 C5 10 48 79 C5 10 48 F6 13 00 00 01 00 00 00 D5 4E 00 00 04 29 00 00 CC B8 FF FF 5A C2 01 00 28 F5 FF FF 00 00 01 00 E7 B5 FF FF D0 BC 01 00 28 F5 FF FF CC B8 FF FF 5A C2 01 00 28 F5 FF FFNote: caster/target OID is always the Swoop Cannon, regardless of what you have targeted (most likely because it shoots the way it is facing; though it first rotates to face the player).Gracia Final wrote:Received on: 20:28:35.458
Caster OID: Swoop Cannon [NPC] (1209058681)
Main target OID: Swoop Cannon [NPC] (1209058681)
Skill: Cannon Fodder (5110)
Cast time: 20 seconds, 181 milliseconds (20181)
Reuse delay: 10 seconds, 500 milliseconds (10500)
Caster X: -18228
Caster Y: 115290
Caster Z: -2776
i_fatal_blow: No (0)
~~~~ Empty loop ~~~~
Usage type: Target point (1)
Ground target X: -18969
Ground target Y: 113872
Ground target Z: -2776
Main target X: -18228
Main target Y: 115290
Main target Z: -2776
I do have some questions:
What is MSU?
What is OID?
Why are the last pairs of XYZ different? I assume main target is the calculated point of destination, and the Ground is geodata? So, even though there is further path to travel it gets caught on geodata where the loop is terminated.