bug: odd delay issues

[tummychow]

I bumped into a kobold archer today in 3.2.0. My base delay factor is 75, movement delay 0. Every time the archer fired an arrow at me, the game would freeze, showing the slash symbol directly on top of my @, and it would lock up for a bit before returning control to me as normal. What's going on here?

[fizzix]

I bumped into a kobold archer today in 3.2.0. My base delay factor is 75, movement delay 0. Every time the archer fired an arrow at me, the game would freeze, showing the slash symbol directly on top of my @, and it would lock up for a bit before returning control to me as normal. What's going on here?

try setting base delay much lower, to 5 or so.

[Hariolor]

+1 to fizzix's solution...

out of curiosity, why would you set the base delay so high?

I set it to 7 or 8, which for me is just on the verge of annoyingly slow when there's a pack of breathers or archers. But I like seeing the trajectories, so I bear with it.

[Timo Pietilä]

I bumped into a kobold archer today in 3.2.0. My base delay factor is 75, movement delay 0. Every time the archer fired an arrow at me, the game would freeze, showing the slash symbol directly on top of my @, and it would lock up for a bit before returning control to me as normal. What's going on here?

75 delay means several seconds for each animation. Go look at the delay again to see what it really means. 75 should say "(5625msec)". I use 3 which is 9msecs. That's slow enough to see the animation.

This is a UI issue, you should see the actual msec before you accept, but you only see what it is currently, not what it will be with the change.

[takkaria]

I bumped into a kobold archer today in 3.2.0. My base delay factor is 75, movement delay 0. Every time the archer fired an arrow at me, the game would freeze, showing the slash symbol directly on top of my @, and it would lock up for a bit before returning control to me as normal. What's going on here?

I've just changed things so that for 3.3, this confusion can't arise, and now you just input the time in milisecs. Thanks for raising the issue.

[tummychow]

I thought it was just straight milliseconds, but that clearly explains what the problem would be. Thanks for that explanation.

[Derakon]

Relatedly, could we make the default delay be something nonzero? Probably in the 5-10ms range. I say this mostly because I had some friends who had played the game for years without knowing that they could actually see spell animations, because they didn't know about the delay factor setting.