3 replies to this topic

[bergjasper]

Hi,

 

Multiple times I've encountered players stacking skills (mostly raiders) when attacking in such way that they do dmg of (for example) 3 skills in 1 attack. This allows for killing in 1 hit. I assume the developers are aware of this bug but didn't see any report so figured I'd make it. Please fix this because it's quite an advantage to do 3 skills in 1 attack, especially vs non tanky types...

 

Best regards.

Edited by bergjasper, 06 September 2016 - 05:44 AM.

[Feuer]

It's a timing issue between the server and game clients. On the server side, they're close enough to cast the skill, on your client side, you're too far away to hit/or be hit by the skill, but you'll still see the CD timer start. Once that happens, you can cast the next. It's not really unfair so far as it is just something you need/should be aware of. 

[bergjasper]

Actually this seems not the be the case (it being fair), I just had a similar thing accidentally with my cleric. I had my cleric on a fair distance with my other char (way too far away to be able to heal) and yet when I hit 2 heal skills they both simultanously were fired on my char. Even though my cleric was still way to far away from my other char. So I'm pretty sure this really IS a bug, and I've encountered it also many times in wars, "1 hit" draining 100% HP at once (and whatever the reason for this may be, it's not fair because this causes the player not to be able to respond before being hit by 3 skills at once). So whether it's a timing issue, or another, it is a bug and does occasionally bring inbalance in fairness.

Edited by bergjasper, 08 September 2016 - 05:23 AM.

[Feuer]

The way to maximum hit limiter works, it's not possible to legitimately 1 hit someone. The only way for it to 'seem' like a 1 hit, is for you latency between the server and the other players client to be so great, that multiple skills have triggered server side [even if you don't see your CD starting, they've been 'fire'] layering up until the server forces a client sync and all of the data is sent at once. 

 

There used to be a 'lag switch' tactic like this many many years ago, but with how ROSE works now, if you lag for more than a certain amount of time [the client side lag, not server lag, totally different] You'll just instantly DC from the server. However, this 'issue' can still happen through natural ping latency and odd core coding. 

 

I've seen it hundreds, if not thousands of times throughout ROSE's history. Many variants of it in fact, and it's always down to lag and forced syncing.