[BUG] Burning Retreat and RtL are bugged
nice try cowboy, you had almost 300 ping in that video
previously rank 2 on old leaderboards
EG.secret.OG.NAVI.sorrychief
No problems here.
nice try cowboy, you had almost 300 ping in that video
And? Is every Oceanic player to be punished because of Anet’s horrible code?
Both of these skills are bugged.
But wouldn’t this also mean burning speed is also bug? I mean that the coding for retreat and speed should be similar.
But wouldn’t this also mean burning speed is also bug? I mean that the coding for retreat and speed should be similar.
they’re not, because virtually every other similar skill in the game does not show this position snapping.
this is exactly why it’s a bug.
it’s also worth mentioning that neither of these skills lagged at release.
Burning Retreat became bugged like this when they overhauled it.
Well I’ve only ever seen this happen when i’m lagging so…
Gandara
No problems here.
no problems? there’s no damage at either the animation endpoint nor the final character position. there’s supposed to be 180 range AOE damage and RtL should only be going on a 20sec CD.
Not to mention other skills don’t suffer from this problem, even with an oceanic ping.
Not to mention no other MMO I play shows this level of sloppy animation/position desyncing.
It’s clearly broken.
(edited by scerevisiae.1972)
But wouldn’t this also mean burning speed is also bug? I mean that the coding for retreat and speed should be similar.
they’re not, because virtually every other similar skill in the game does not show this position snapping.
this is exactly why it’s a bug.
it’s also worth mentioning that neither of these skills lagged at release.
Actually every skill that was a leap or moved you quickly (ie burning retreat and ride the lightning) did this at release (or worse). It was so bad people didn’t use them.
It is Anet’s horrible code. Try doing Sanctum Sprint with an Oceanic ping…
I have no problem with these 2 skills. They work for me as they should. If I hit target with RTL,cd of it is cut in half,just as description says.
Can you even stow weapons with that ping? I imagine you’d try to cancel cast (not of RTL or Burning Retreat),but skill would still go through and you’d stow after it was cast.
Example for stowing skills…earthquake,fire grab,fgs,etc.
I can copy both the Burning retreat and RtL bug with 30-40 ping – though I have to admit that they only appear randomly for me. The effect is also less noticeable with a better ping.
But, as said beore, RtL has been bugged for ages, so that isn’t really news.
oceanic ping has nothing to do with code. They don’t house servers from over there so its only natural some of the packets get lost or take awhile to ping back to you.
Bad Elementalist
Ahh, yeah. I’ve had that snapping happen to me. It’s a little annoying but it’s not gamebreaking for me.
oceanic ping has nothing to do with code. They don’t house servers from over there so its only natural some of the packets get lost or take awhile to ping back to you.
It is entirely to do with their code. This does not happen in other games. These skills, and all of sanctum sprint, cannot handle the higher ping. Their code sucks.
Just fyi, RtL doesn’t do its small aoe-blast at the end unless you hit the person targeted. If you use it into even a million people but have no target you get no damage and full CD.
In your rtl test, you didn’t have any of the dummies targeted.
oceanic ping has nothing to do with code. They don’t house servers from over there so its only natural some of the packets get lost or take awhile to ping back to you.
It is entirely to do with their code. This does not happen in other games. These skills, and all of sanctum sprint, cannot handle the higher ping. Their code sucks.
yep, i’m afraid this is the right answer. It’s bad implementation. The proof is that other MMOs have skills that perform similar slow projectile-like movement that animates smoothly and doesn’t snap positions twice as it’s currently doing.
The fact it snaps position twice as shown in the video is evidence enough of a bug. The second clue is that the position snaps are more than 200msec apart, so the network latency aspect is being amplified.