Good. Please use this as a lesson and review the entire reporting and punishment process to ensure that the next time an issue like this comes up, it won't even come to false bans in the first place.
The raid group that got banned for reporting that exploit simply because they ended up looting the boss they could have killed without the exploit anyway also should not have received such a disproportionate punishment.
While I do understand your intention here, I have to point out:- yes, while addons are "use at your own risk" they are not third party "programs." They are third party, ZOS takes no responsibility for them, but they are not programs. They are scripts which use an API made available by ZOS, and they can only use what is available, and made available, by ZOS. If an addon broke something, then it wasn't just "made badly,"** and the responsible code in the API should be fixed, made private, or made unusable.I would like to highlight that addons are third party programs, which use - in theory - is at our own risk and for which ZOS has no obligations in case of troubles resulting from using them. So, personally, I find ZOS very fair to care about an issue caused by an addon, because from the moment the cause was identified as being an addon, they could have decided to ignore the issue.
Now on the other hand, fact is that some of the addons are so deeply integrated into game content, that the related activities rely on using those and wouldn't work without them. Trading is a typical case. This puts ZOS in a grey zone regarding limit of responsibility.
I'm not sure about the possible implications in case of bigger troubles. Maybe that ZOS will need to give a thinking about fully taking over and integrating some of the addons, to get back to a clear scope of responsibility.
I would like to highlight that addons are third party programs, which use - in theory - is at our own risk and for which ZOS has no obligations in case of troubles resulting from using them. So, personally, I find ZOS very fair to care about an issue caused by an addon, because from the moment the cause was identified as being an addon, they could have decided to ignore the issue.
Now on the other hand, fact is that some of the addons are so deeply integrated into game content, that the related activities rely on using those and wouldn't work without them. Trading is a typical case. This puts ZOS in a grey zone regarding limit of responsibility.
The addon boogeyman strikes again.
Please, stop relying on general ignorance of how addons work to scapegoat. If you actually want to be transparent, please tell us the full details of what part of your restricted public API caused your anti-cheat systems to fire. Because it sounds like an incredibly suspect claim.
AddOns aren't viruses, you can't blame them for everything wrong in your game, geez.
The addon boogeyman strikes again.
Please, stop relying on general ignorance of how addons work to scapegoat. If you actually want to be transparent, please tell us the full details of what part of your restricted public API caused your anti-cheat systems to fire. Because it sounds like an incredibly suspect claim.
AddOns aren't viruses, you can't blame them for everything wrong in your game, geez.
Even without any other info on the issue, I'd say it's actually quite a reasonable claim. It's relatively common knowledge that godsend can get you a social ban. Dressing room et al. can get you kicked if you spam change builds. An add-on doing something is generally indistinguishable from any other method of doing things. So it's not difficult to imagine an add-on tripping up other automated systems. General knowledge of how add-ons work does not actually make it more difficult to believe the claim
As far as more info on it, we've asked the Zos add-on person but BC it's anti cheat stuff no idea how much they'll be able to say.
Hvíthákarl wrote: »Acknowledging the error is a good sign indeed, but from what I've been investigating about this, the issue that needs to be improved the most on your behalf is how (and how often) you engage with the community when something like this happens. There has been a clear lack of communication on your end and by simply addressing it properly, most of the drama generated around this could've been avoided.
Still, I'm glad to see ZoS owning its own mistakes!
The addon boogeyman strikes again.
Please, stop relying on general ignorance of how addons work to scapegoat. If you actually want to be transparent, please tell us the full details of what part of your restricted public API caused your anti-cheat systems to fire. Because it sounds like an incredibly suspect claim.
AddOns aren't viruses, you can't blame them for everything wrong in your game, geez.
The addon boogeyman strikes again.
Please, stop relying on general ignorance of how addons work to scapegoat. If you actually want to be transparent, please tell us the full details of what part of your restricted public API caused your anti-cheat systems to fire. Because it sounds like an incredibly suspect claim.
AddOns aren't viruses, you can't blame them for everything wrong in your game, geez.
Lady_Lindel wrote: »Well when I first saw this on Reddit, I was gobsmacked by the arrogant response to the player. Now we have the apology. So I see people thinking it is so cool they have apologised, all is forgiven. How about we ask if the apology is because they are losing players at a rapid rate. Remember this game is owned by a billion dollar company. It is a publicly listed company who expects profit. [snip] They are not your friend. They did not apologise because they saw the error of their ways. Think about the number of pvp players who have left, the Xbox players who can't play currently (but don't worry, the fix will be out Oct 6th) The ridiculous housing furniture caps, while they push out larger and larger houses. And now the slap in the face to loyal Eso+ players. This game is hemorrhaging players and they know it.
Looking at the Steam player charts you can see it. Now while Steam doesn't reflect the real player numbers, it does reflect trends. This game is losing players at an alarming rate.
The addon boogeyman strikes again.
Please, stop relying on general ignorance of how addons work to scapegoat. If you actually want to be transparent, please tell us the full details of what part of your restricted public API caused your anti-cheat systems to fire. Because it sounds like an incredibly suspect claim.
AddOns aren't viruses, you can't blame them for everything wrong in your game, geez.
If you read some of the comments (moreso on reddit) by a couple of the affected players, you'd see that this was their guess before ZOS said anything publicly. The affected persons all realized they seemed to have one addon that was the most likely suspect in common. ZOS just seems to have confirmed their theory.
We don't want an event every other week
We don't need new content four times a year.
And we sure as hell don't want you to act like you gave us (your ESO+ customers) something great when you announced the free copy if the Deadlands DLC as your grand mystery prize
What we want is a game that's reliable and that's thoroughly bug tested on all platforms before a patch goes out. That's it.
I sure hope they know they're losing players at an alarming rate.
@Schiffy And that one addon was...?
anitajoneb17_ESO wrote: »@Schiffy And that one addon was...?
I could not find that info written black on white anywhere (I haven't researched for ages either but I, too, was curious). But it's an add-on with auto-loot for mail. So unless another addon that I don't know of can do that, I'd say it's Dolgubon's lazy writ crafter. Seems like this option of autolooting mail attachments is misbehaving, or, better said, causes ZOS logs to misbehave if they are used in conjunction with a full inventory. Not Dolgubon's fault in any way.