I just wanted to say you really have some awesome information here, thanks for the work. Is it true though Store TP is the new Haste?
I just wanted to say you really have some awesome information here, thanks for the work. Is it true though Store TP is the new Haste?
Stunning Spiders til they're 300 tp is rough /w Sickle being almost instant. Since
I'll need to repeat do a large number of tests to get an accurate precision on
rounding and it's location in the equation, I'm hoping to find something easy. Era
brought up Diremites too, those don't seem too bad. Another possibility are Crawlers
=x. I didn't wanna mess /w Euvhi cause they're kinda dangerous to mess around /w on
DRK... although I just rembered there's a T one near the zone into palace, that
might work nice for tests.
I don't think anyone knows if you can be slowed over 100%... You'd have to be
inflicted by some kind of slow over 50%, and then have elegy casted on you =x. I
can't think of a scenario where that would happen =x. Although if you mean max slow
from one source, 100% is probably it (and probably the euvhis.)
I think Era hit most of your questions. As for inconsistancies, I've personalliHow do you account for inconsistancies? For instance - When I have the same
setup with hasso/seigan + dread spikes, I've run into cases where the recast
'flip-flops' between two different recast values. Do you just take the lowest recast
value?
never seen any myself. I must have done well over 1,000 casts of dreadspikes and
never seen anything close. It's important you use the recast timer within the menu
as it's consistant. (Recast plugin can sometimes be a second off.) If you do find a
particular recast that 'flip-flops' you should definetly post your setup. An
inconsistancy would break down our current model of how recast timers work.
Worth noting is that during my fastcast testing /w fractional recast timers, there's
strong evidence to support that a 34.9 second recast time and a 34.0 recast time are
equivalant. Both would register as a 34 second recast for 1 second, before switching
to 33 seconds. This would exclude the possibility of a fractional recast causing a
'flip-flop' in recast times.
Since I'm not sure what youre testing, I can only give you general advice. Having
consistant returns will always work out the best. But if thats not possible, then
look for reducing your margin of error with repeated tests and taking an average.
Purposely create tests which predict where changes occur and see if your model holds
up. Getting lots of data and plotting it always helps. And I guess last, read up on
current models of game mechanics. Haste, Store TP, Enmity, Attack, Magic Damage
Taken, Magic Attck Bonus, Damage Calculations, etc... Understanding those equations
will usualli help you in desiging your own models.
Fastcast is the new haste. SE is going to release a ton of equipment /w fast cast on it, and give fastcast rolls to COR!I just wanted to say you really have some awesome information here, thanks for the work. Is it true though Store TP is the new Haste?
There's realli a lot of discussion that could be brought up on this topic. For the most part my tests ended up with the best possible approximations for the stuff that wasn't testable /w recasts~
EDIT: Was having troubles posting =x. Apparently it was the >.> in Tricen's quote =x.
IIRC weakness from death puts you at 100% slow, if you can be slowed while weakened there should be a pretty high cap, if any
OK this has been bugging the CRAP out of me for weeks now. I mean no disrespect and truely appreciate the work you've done and the info you've been able to find out for us, but...
really
personally
finally
graphically
actually
originally
mmmkay? mkay!
Toks, trust me, you're infinitely more annoying than a little bit of cutesy typing.
Spider's don't have a self buff but you should just enlist a BST to help you. Have them charm a pet and have the pet attack until it has 300 tp. Release and watch for the tp move. Since you can check on pet tp, you can say be sure it has 300 tp when it performs a ws.