Alyrn_Grey wrote: »Whose is white knighting them. I'm just amused by the shear arrogance in assuming some persistent bug is easy to fix and that they just are ignoring it.
If you are that good at coding then clearly you can propose how to fix it.
The quest itself is not bug per say, it is more likely a phrasing issue. Quest starts to break down when the server is busy. Try again when it is not peek hours, many a quest work that way.
rager82b14_ESO wrote: »Alyrn_Grey wrote: »Whose is white knighting them. I'm just amused by the shear arrogance in assuming some persistent bug is easy to fix and that they just are ignoring it.
If you are that good at coding then clearly you can propose how to fix it.
I think you are a little full of yourself when being amused about some bug quests that was bugged since Beta. When quests that hinder major plot lines of the story. It should have been fix long time ago.
SO yes it could have been fixed. It is not about arrogance, it makes testers feel like they tested the game for nothing. You can disagree with me all you want, but to call it arrogance, you really need to step down.
Alyrn_Grey wrote: »Excellent then you will have no problem identifying the broken bit of code and having it fixed in an hour.
As a beta tester I feel we made significant impact on the games overall performance upon release. Yes they still have some issues with quests but since quests don't impact the game in a MAJOR way (Yes it is a story quest but there's still plenty to do outside of that quest) I would rather they fix a lot of quests at one down (AKA during server downtime) instead of releasing patches every day or every other hour to fix each quest individually. Patches cost money, servers cost money, game maintenance costs money, which results in issues like quests being fixed in chunks rather than slivers.
Some of these quests/objectives/lootables have had the same bugs since beta...I'm beginning to think I was the only one out of everybody actually reporting them and since it was only me, not enough to get recognized LOL
BlackSparrow wrote: »As a beta tester I feel we made significant impact on the games overall performance upon release. Yes they still have some issues with quests but since quests don't impact the game in a MAJOR way (Yes it is a story quest but there's still plenty to do outside of that quest) I would rather they fix a lot of quests at one down (AKA during server downtime) instead of releasing patches every day or every other hour to fix each quest individually. Patches cost money, servers cost money, game maintenance costs money, which results in issues like quests being fixed in chunks rather than slivers.
Truth is, a lot of the mid-to-high level quests didn't get played nearly as much in the beta as the low ones did, so the devs didn't have as much to work with bug-catching-wise. But now that players are hitting those levels, they'll know. So help them out with /bug, instead of posting a thread here that will fall off the first page in about an hour.
Alyrn_Grey wrote: »Whose is white knighting them. I'm just amused by the shear arrogance in assuming some persistent bug is easy to fix and that they just are ignoring it.
If you are that good at coding then clearly you can propose how to fix it.
rager82b14_ESO wrote: »While you guys are quick to defend. Let me remind you that some of the quests have been bugged since beta and have been reported. They have had ample time for some of these bugs.
dpayne83_ESO wrote: »99 little bugs in the code.
99 little bugs.
Take one down, patch it around.
127 little bugs in the code.