Post: #11

so the problem is just the animation speed, not the swing speed?

in this case you can use LOCAL.AnimDelay to simulate the old animation speed which takes the full swing delay instead fixed 0.7s + waiting the remaining delay

the correct behavior is this new style, because this timer of 0.7s match all weapon animation movements, so the damage will be always taken exactly when the weapon movement hit the target, and it will keep waiting the remaining time. OSI use this style since almost 20 years ago on AOS age (2003) or maybe even earlier

on the other hand, using the old style it will adjust the animation speed to be the same as the full swing delay, it will always hit at the end of the timer, and this can cause weird animations sequence (eg: damage being taken some milliseconds before/after the weapon animation hit the target)

but anyway some ppl still like this old style, so you can change it using a few lines:

Post: #12

(03-17-2017 01:41 PM)Coruja Wrote:  

Code:

[EVENTS e_add_this_event_on_all_chars]
ON=@HitTry
LOCAL.AnimDelay=<ARGN1>

i fix like that few days ago now works good, and if i change speedscalefactor change the animdelay.

Btw, i upgrade my old 56b nighly 2006 to 56c april and im fixing a lot of things (i try 56d but it is too much hard than 56c), the problem is the compatibility with older versions,there are in .ini, but dont works. And it is funny becouse my server is up from 1999 and im the only sphere server in my country, and top ranking, reopened 2 weeks ago. For my opinion, run sphereserver is too hard now for beginners and old shards. I survive becouse i learn the job from furio. But without him my server was closed.

Post: #13

56c have many new features on sphere.ini, but most of these features are better and more stable on 56d

so maybe it's better go with 56d instead keep using 56c trying to fix things that are already fixed on 56d