Maintenance for the week of December 2:
• PC/Mac: NA and EU megaservers for patch maintenance – December 2, 4:00AM EST (9:00 UTC) - 9:00AM EST (14:00 UTC)
• Xbox: NA and EU megaservers for patch maintenance – December 4, 6:00AM EST (11:00 UTC) - 12:00PM EST (17:00 UTC)
• PlayStation®: NA and EU megaservers for patch maintenance – December 4, 6:00AM EST (11:00 UTC) - 12:00PM EST (17:00 UTC)

Why are the Kill 20 Cyrodiil quests now broken the way you broke Kill 40?

ioResult
ioResult
✭✭✭
For a couple of patches now, ZOS you've broken the Kill 40 Players quest. If you're in a group with one or more other players, you can do a bunch of damage to an adversary and even get the killing blow on them, but when they die and release you don't get credit for the kill in your Kill 40 Players. Only one person in the group is able to get credit for each kill. Get the killing blow? Doesn't count. Burn them down from 100% to 5% health but then another group member gets the killing blow on them? Doesn't count. The ONLY way the kills are guarantted to count for your quest is to leave your group and play truly solo.

Now with the Necrom patch, the exact same thing is happening for the Kill 20 XXXX quest. If one member of your group has Kill 20 Players and you have Kill 20 Nightblades and you both hit the enemy nightblade repeatedly, and the group member with the Kill 20 Nightblades gets the killing blow on the enemy nightblade, that kill frequently does NOT count towards their KIll 20 Nightblades quest but DOES count for the other group members Kill 20 Players quest.

WHY?

ZOS you broke Kill 40 a couple patches ago and now you've broken all the Kill 20 quests. All your changes have done is DISCOURAGE group play in Cyrodiil if you want to do those quests.

Can you please fix them?

Or at least explain why one can be in a group and do a bunch of damage to an enemy and even get the killing blow on them but it doesn't count towards the quest? What are the parameters now for it to count when you're in a group?
But yeah ZOS...Cloak is the problem.
--
sudo rm -rf /
don't try this at ~
Sign In or Register to comment.