ethebubbeth.9140

I did another DS meta and made sure I was mounted after Mouth of Mordremoth was defeated and the cutscene played, since that was brought up as a potential issue in this thread. I properly received weekly credit this time.

I'm pretty sure they mean successfully. It definitely could use some clearer language. It would also be nice to consistently grant credit for the weekly when you get the meta choice chest from the end after defeating the Mouth of Mordremoth. If there's some additional criteria beyond that, they should to be stated.

I'm not privy to how the loot tables from those chests are fashioned, but per the wiki they are affected by your magic find. From an Anet dev's description of how magic find works: My best guess is that the items you want are in a lower rarity category and boosting your magic find kicks you up into higher loot categories more often where they aren't present.

Add my voice to this. I had 140% participation. Got plenty of damage in on Mouth of Mordremoth. I looted the end chest and received the meta choice chest. No weekly wizard vault credit. Screenshot proof of successful meta completion with no weekly credit. In my screenshot here, you can see the glow of the looted end chest.

So it took me nearly two hours to get credit for one defense event today for dailies. For the longest time no group I was in could hold back an assault on a tower/keep/stonemist. I started roaming and would kill people trying to take camps, and received no credit. Reading through this thread... I had to let them kill NPCs at the camp first before killing them to get defense credit? In what world is that a sane metric. Sorry guard, I had to let them kill you before I could fight back.

This just happened to me... The "Mech Arm" enemies on the left side couldn't have their shields removed and the event stalled. Just sitting here with Kestrel Aoi and Kyung-Hee attaching an invincible Mech Arm https://i.imgur.com/NtmMczj.jpeg

This is STILL broken after the June 7 Dragon Bash release.

+1 here. I experienced the exact same behavior since EoD release.