Post: #1

hello im using a version of sphere 56c 10 apr.
my old 56b have

SpeedScaleFactor=30000

without speedera and damage era.

now im trying to set the same speedfactor but it doesnt work, i try to set argn1 in @hittry for force it but dont work, i only see the decimal count

this is the 56c ini format

// Damage calculation formula to use on physical combat
// 0 = pre-AOS (Sphere custom)
// 1 = pre-AOS
// 2 = AOS
CombatDamageEra=0

// Swing Speed formula to use on physical combat
// 0 = pre-AOS (Sphere custom) // Recommended SpeedScaleFactor = 15000. Old Sphere 0.55 custom formula. Not compatible with Swing Speed Increase property, and uses DEX instead STAM
// 1 = pre-AOS // Recommended SpeedScaleFactor = 15000. Not compatible with Swing Speed Increase property
// 2 = AOS // Recommended SpeedScaleFactor = 40000
// 3 = SE // Recommended SpeedScaleFactor = 80000
// 4 = ML // Doesn't use SpeedScaleFactor. Only compatible with ML speed format (eg. 0.25 ~ 5.00 seconds instead 0 ~ 50), uncomment TAG.OVERRIDE.SPEED on all weapons to enable ML speed format
CombatSpeedEra=2

// Speed scale factor for weapons
SpeedScaleFactor=30000

do u know some solutions? i also try differents 56d builds, and if i put the 56b into the new folder updated to 56c (scripts + .ini) it works fine.

Post: #2

I don't understand, what's the output of argn1 in @hittry?

Post: #3

the problems is: my weapons have the same speed hit time, and i dont understand why.

Post: #4

Here u got all u need to understand how it works and what are u doing bad. Not tested

Post: #5

nothing. the swing is always the same.
i put different say and they ruturn the value but the attack speed dont change. :| .
how it is possible? there are another triggers for do the same? i check all my hittry and they are ok.

Post: #6

The only thing I can say is that u are doing something bad. I would need to see ur scripts to detect it.

wait a moment... Which client are u using? 7.++?? Lastest client will have the same speedscale factor. But the timing between hits will change. So if you are using last clients u will need a different scale factor to let i work properly. lastest client dosnt slow the hit animation.

Post: #7

i use client 6.0.9.2 btw,
my shard is open from 98, and i have a folder with 25mb of script it is impossible search on it, anyway, with the 56b the speedscalefactor works, and with a nightly build of 56d of december work it too.
i think is a problem of sphere 56b april now.

Post: #8

i solved it with LOCAL.AnimDelay=xxxx
i dont understand why, but sphere 56c set animdelay as 2 secs, i put the speedscalefactor time and now works correctly :|

Post: #9

if you want replicate old formulas, just change sphere.ini to use these old formulas


then just set your custom SpeedScaleFactor again

Post: #10

dont work. is a problem of animdelay