Aetherblade catche - Goemms lab fall bug
I can port you from the cuatl waypoint, just message me in game and guest to blackgate server, easy peasy. I also hate that bug, as well as the rest of my guild. Porting helps.
I’l hit you up ingame. I’ve made it to the Stormy area, but 6 more times…got bugged and fell all the way down and died.
happened to me twice yesterday. only happened when i was in the storm section.
i have had it happen in windy and stormy. I’ve tried holding forward, I’ve tried not holding anything down and have fallen all the way down both ways.
Edit: I finally made it. If a Dev is reading, I fell a few times in the Chilly section and it didn’t bug, and in the last section is didn’t fall at all.
(edited by HappyDale.5398)
I completed it yesterday. I fell a bunch of times without hitting the bug. Then once I fell all the way through the world, landed in the inquest lab in the NE, and amazingly enough took 0 falling damage and did not lose my attunement for the puzzle.
I’ve been having this problem almost every single time I fall. Really annoying.
I hope they fix this soon.
Hell’s Disciples [HD] – Commander
Henge Of Denravi since beta
This is Anet. Doubtful.
Edit:
Yep, just fell at stormy station, bugged POS, back to the start I go.
(edited by GuzziHero.2467)
It happened to me more than one time both yesterday and today. Actually, all the time I fell through the jp I landed with zero damage on the very top of Metrica Province in areas that are not supposed to be reachable.
In attachment there are some screenshots from the most interesting “landing” I got so far.
You do know that you can talk to the golem outside the entrance to the puzzle and he will take you to the furthest section you’ve reached, right?
Just happened again… but before the last update (as you can see from the screen-shots). Because of the update I am pretty sure the small golem will not keep my advancement in the JP so I decided to give a look around.This time I landed on the top of the Luminates Plates Inquest Facility.
I am not doing in on purpose, of course.
ArenaNet Communications Manager
We are all over this bug!
Communications Manager
Guild & Fansite Relations; In-Game Events
ArenaNet
This bug frustrated me so much because I was losing the “attunement” buff while making me restart from scratch. Though I finally did it in one run without falling or dying in the end.
Really annoying and glad to know you guys are on it!
The strangest thing is that it restart me at the asuran gate correctly when falling, then put me back to where I was when falling and then SPLAT on the ground. Seems like the trigger is working but something else puts me back in the falling position…
We are all over this bug!
Please fix this before the end of the event so we can get our Cache achievement!!!!
You just have to not fall
This bug really frustrates me. To get my jumping puzzle achievement eventually a friendly mesmer portalled me across all the jumps as I couldn’t fall without being kicked all the way out and having to restart.
3 months later I tried it again for the cache achievement…and same thing! I can’t face asking the mesmer to take me again.
If it is a known issue, why put a cache there?
We are all over this bug!
Hi Gaile, Glad to hear that the team is looking in to this.
But I have to add and emphasize that this bug has been around for a very long time, and till today, has yet to be fixed. Admittedly, I am really bad at JPs and I do fall often, and this bug of falling to my death miles away from where I was supposed to be ported is honestly really ANNOYING (for emphasis) and wasting me alot of gold (well about 2s for porting everytime I fall).
I just spent about 20 silver, porting back to the WP just coz I kept falling, and I keep being bugged and glitched to my death. I still have not gotten my cache yet.
As much as I enjoy the luxury of being ported, nothing beats the satisfaction of beating a jumping puzzle, esp when one sucks at it as much as I do.
(edited.. my grammar has fallen off the roof)
PMS|H2O Guild Wars 2 Division Co-Leader
(edited by revx.4378)
Agreed, old bug.
This cache should never have been placed near the end of a buggy JP. Should have placed it closer to the beginning, or fixed the JP. This is NOT a new bug.