Illein, on 11 January 2013 - 10:58 AM, said:
Or do you just want to see heads roll because some people couldn't help themselves but to enrichen themselves illegitimately and now have to face the recoil?
I don't really care to see heads roll on either side of this issue. It was a minor mistake on Anets part, that given the timing was allowed to snowball into a larger issue. They would have been better served quietly putting it to rest.
Illein, on 11 January 2013 - 11:20 AM, said:
And give everyone a free pass to abandon personal responsibility in the process.
This is paying lip service to that concept. They can't be selective in the application of the ban hammer, using "potential economic harm" as the guiding principle. Ban all exploiters or ban none. After reading the thread about the guy who was refunded his gem purchases after being banned for this, I can only assume that they determined banning for HotW would be too expensive in terms of refunds to be worthwhile. They're obviously weighing the potential loss in gem sales against the potential loss due to refunds, so to say this was about stopping exploiters is ridiculous.
It was just a ban wave that Anet felt didn't cause them much economic harm. That criteria can be easily abused. Like an exploit.
Illein, on 11 January 2013 - 05:07 PM, said:
But what is it you think would mean for that Dev to take responsibility beyond actually fixing the issue asap as he/she/they did?
But they didn't fix it ASAP. They waited something like ten+ days to fix it, ten+ days they also failed to address it on the forums, despite it being public knowledge to the point where people were on the forums asking if it was an exploit.
I understand that it was the holidays, and perhaps even that too many staff were on vacation to effect a tiny change to one recipe. But surely someone from Anet could have chimed in and stated that they were aware of the recipe, and that they would monitor it and consider banning accordingly (and I understand banning a guy who made 2000+ globs with this), some time in the first few days it was available.
Failing that, they could have accepted that the failure to promptly address this resided in their own choice to vacation. That's not to say we should harp on them for fixing the recipe or leaving it in for so long, but that they shouldn't take it upon themselves to blame the players.
As it is, it sounds like the threshold for this was fairly low. I know the numbers banned are allegedly low as well, but for how long the recipe was available, you didn't need to spend 8+ hours a day abusing it to qualify for the ban.
I would have been satisfied if they came in and fixed the recipe and otherwise left the issue alone. The alternative is to ban for every exploit, but it's clear they won't do that because it's way too costly (partially because exploits are still way too common).
pumpkin pie, on 11 January 2013 - 06:18 PM, said:
not only did they not report the bugs they posted in on a forum.
Historically, that's the quickest method for getting a bug addressed.
D3 offered a great example with the wizard's perma-Archon bug; reported regularly and only quietly known for two months, it was hotfixed inside 24 hours once it became public knowledge on the forums.
Meanwhile, am I the only one who thinks the game has much bigger issues, and that other than fixing the recipe, this really didn't warrant any more developer attention? And yet, this seems to be the most attention I've seen Anet give any issue.
Edited by Millimidget, 11 January 2013 - 09:35 PM.