History Made: Dredgehaunt Cliffs event for Chuka and Champawat bug FIXED FINALLY after 2+ years!!!

First off, I'd like to commemorate the 70+ players that participated in this historical moment, probably the greatest moment in history of gw2. You all know who you are, few free to post below if you were here for the event today.

Now: This event has been bugged since HoT release sources tell me and today commanded by Quintessential Evil and 4 other commanders, we managed to flood the map and create a new instance. It was incredibly difficult because no one ever barely steps foot on Dredgehaunt Cliffs. That's why those who were willing to spend time outta their day to come to this historical event will be forever remembered and ingrained into this forum. The thousands of players who couldn't craft Chuka and Champawat for days, weeks, months or even years can now have peace in mind. Same goes for those who are planning to craft it in the future, know that we payed the way for yall.

So again to everyone who participated today: From the bottom of my aging heart and many others, Thank You.If you were part of this today, post down below to show anything is possible.

Screenshot: https://ibb.co/f6xUXG

\o/ It was glorious.

Having not experienced the bug from when I made it, what was the actual bug itself?

I confess to being completely unaware of the bug, but now being on tier 3 for the precursor of this weapon I am very pleased to hear your news! :)

Creating a new map instance happens every time there is a patch. The common advice given for stalled events is to try to change map IPs (by guesting, finding a friend in another map IP, etc.), or wait for a patch (which is common at, and after, a Release).

If you had to force a new map to spawn in order to progress then the appropriate conclusion would seem to be that the bug isn't fixed.

As Inculpatus noted, there’s a new map instance with each patch (December alone had 6 patches) so unfortunately your efforts didn’t fix it. If it’s bugged the bug will reoccur when enough time has passed.

I don't think that short bow has been out for 2 years.

Me and my wife did all the Chuka and Champawat achievements with 0 problems, I guess we were lucky?

^Good point. It’s been less than 2 years.

Chuka and ChampawatThe name of the weapon was first announced on March 25th 2016.

That was indeed a clever way to generate a new instance. But let's be clear: plenty of people have completed the event and successfully made the bow during the time. Sure, ANet should fix the issue so this doesn't keep happening, but it's always been possible to complete the event; it's just harder than it ought to be.

It also doesn't mean ArenaNet didn't 'fix' the issue, and it ended up broken, again. Sometimes, fixing a bug will cause another, even more difficult to fix, bug. Sometimes, as well, the exact cause of the bug can not be determined, and thus, no fix is possible. /shrug

@Inculpatus cedo.9234 said:It also doesn't mean ArenaNet didn't 'fix' the issue, and it ended up broken, again. Sometimes, fixing a bug will cause another, even more difficult to fix, bug. Sometimes, as well, the exact cause of the bug can not be determined, and thus, no fix is possible. /shrug

They introduced new ways to achieve legendary collections with the defense of Orr and what not. Not sure why this one is a problem since I don't know the SB collection, but it seems silly that this is a problem at all. If it's causing problems, just make a random skale give you the collection piece rather than lock people out of the weapon.

Who knows? Maybe it only stalls, some times. Maybe it's active more often than not. It's certainly true that many players have finished the Chupa & ... Legendary Weapon.

If you talk about Jotun champ, I got my Chuka item last Sunday. I saw no issues with the event or noticed any bugs. I am on EU server though.

@Randulf.7614 said:Having not experienced the bug from when I made it, what was the actual bug itself?

This......

For those wondering, Chuka and Champawat needed an event completed, but the event was bugged for many people, including myself. While this may not have fixed the overall issue with the event itself, it did allow a bunch of people to finally continue with the weapon, so I consider it pretty awesome that players themselves came together in order to circumvent the issue.

Thanks Lunno.1862 for explaining the bug. Around 100 players were on the map to fix it, it was truly a sight to see.

@ZenithaL.2475 said:Thanks Lunno.1862 for explaining the bug. Around 100 players were on the map to fix it, it was truly a sight to see.

You didn't fix the bug, though. You just organized to create a new instance of the map, which is great teamwork, but the bug still exists. The old instance will still be bugged. And the new instance you created, if it somehow stayed around long enough, would eventually become bugged, too.

Players fixing bugs by playing the game. When did they patch that? I must have missed it. ;)

Ah event is stuck again with tiger under the snow..............

Just fyi, some of the legendary events are disabled/bugged without a fix date so anet put vendors in place to sell the needed items. Hope this helps.

@Ze Dos Cavalos.6132 said:Me and my wife did all the Chuka and Champawat achievements with 0 problems, I guess we were lucky?

I finished mine too but today I was in Caledon for the JP daily and the C&C event there was broken as well.

I feel the need to mention that you spelled “Dredgehautn” in your photo title.

Glad you could get that far into the legendary journey... just getting past the tiger hunt in stage 1 is now impossible due to the tigers incessant need to go tree hugging... with no acknowledgement of the issue from ANET and likely no fix any time soon.