2009-11-05, 02:04 AM
ArbalistMaster Wrote:I finally maxed snipe the other day and went to do some tests with another MM firing snipe as soon as it cooled down as a parameter.
I'm pretty sure that what happens is the server runs a "has your cooldown completed" routine every 5 seconds, so if you keep shooting them as soon as they become available, it'll take 10 seconds to cooldown. but if you wait 3-4 seconds after the cooldown and shoot again, it will only take 6 or so seconds to cooldown because you still shot it within the same "cycle"
proof is that even if we started shooting at different times, we'd end up with cooldowns completing at the same time after 1-2 snipes, and then we'd keep shooting at the same time. So there's a 4 second window where you can shoot snipe and it will still cooldown at the same time, regardless of at what point in this window you shoot it.
The way KMS "fixed" it by changing snipe to 4 second cooldown would allow us to "ride" this 5 second "cycle" provided you time it right.
in essence, with the current way the server handles cooldowns, no cooldown can be lower than 5 seconds regardless of what the skill actually says(assuming several uses of the skill, you could fire a 1 second cooldown skill twice in 3 seconds if you fire the first at the end of the cycle, but from then on it would take 5 seconds); and getting 4 second cooldown in the data is probably the easiest feasible way for us to get a real 5 second snipe. Otherwise it would require some re-coding by nexon to have cooldowns (at least those of skills with very short cooldown times) to be evaluated every second instead of every 5 seconds.
Having the skill have a delay upwards of 5 seconds would be the best solution. Cooldowns suck.