While well-intentioned, that advice is more likely to get people banned for disseminating information about the exploit. Unknowingly exploiting and coming to the forum to broadcast how they got it to happen are two very different things. You may or may not get banned for the former, while you will almost certainly get banned for the latter.JoeCapricorn wrote: »I encourage anyone who does find what triggers it to issue a similar PSA, to spit in the face of the automated banbots.
Finedaible wrote: »Lets play roulette then. Certainly our odds are good, right?
... Right?
Zenimax is not playing roulette. They would be looking for specific behavior to determine who they banned up front.
I completely agree!we understand some people will unknowingly run into this through normal play
For those of us who want to actively avoid being banned, do you have any guidelines on what not to do? "don't do writs in auridon on a khajiit between 8 & 10 GMT" or whatever? Sure, people could theoretically take that information and choose to exploit it, but you've already said you'll ban them.
I don't pay close enough attention to endeavors to notice if I'm getting them more than once, and now, like the poster above, I feel like I have to be paranoid.
OtarTheMad wrote: »Just disable the endeavor system on all platforms until it’s fixed so more innocents don’t get banned, simple.
Hi all. Just wanted to follow up here based on some of the feedback. Our intention with highlighting the Endeavor reset issue is to be proactive with the community, noting we are aware of the issue and working toward a solution.
We do not expect players to be monitoring their endeavors in fear of accidentally encountering the exploit, and we'd like to highlight the Endeavor resetting is not a widespread issue and is pretty rare to trigger. In addition, we have a better understanding of the issue and have set up systems on our side to see when someone is specifically exploiting. So if you accidentally run into the issue, you don’t need to worry about having your account actioned.
We are not looking to punish anyone who accidentally stumbles into this, but rather inform the community about an issue we discovered and warn that we will take action on those who take extreme advantage of it (which, again, is not accidental.) We hope this helps to clear up any concerns here. Thanks for your patience and understanding regarding this.
@ZOS_Kevin I think the controversy stems from the temporary banning that happened. Last year, there was an exploitable bug that allowed people to claim daily login rewards multiple times. In that case, there was no temporary ban. Last year, you investigated, found the people who exploited egregiously, and banned them, without ever subjecting innocent bystanders to a temporary ban.We are not looking to punish anyone who accidentally stumbles into this
@ZOS_Kevin I think the controversy stems from the temporary banning that happened. Last year, there was an exploitable bug that allowed people to claim daily login rewards multiple times. In that case, there was no temporary ban. Last year, you investigated, found the people who exploited egregiously, and banned them, without ever subjecting innocent bystanders to a temporary ban.We are not looking to punish anyone who accidentally stumbles into this
A temporary ban, even if it is reversed quickly, appears to be what people are concerned about, esp. since this wasn't something that you had used in the case of the previous high-profile exploitable bug.
@ZOS_Kevin I think the controversy stems from the temporary banning that happened. Last year, there was an exploitable bug that allowed people to claim daily login rewards multiple times. In that case, there was no temporary ban. Last year, you investigated, found the people who exploited egregiously, and banned them, without ever subjecting innocent bystanders to a temporary ban.We are not looking to punish anyone who accidentally stumbles into this
A temporary ban, even if it is reversed quickly, appears to be what people are concerned about, esp. since this wasn't something that you had used in the case of the previous high-profile exploitable bug.
Dagoth_Rac wrote: »@ZOS_Kevin I think the controversy stems from the temporary banning that happened. Last year, there was an exploitable bug that allowed people to claim daily login rewards multiple times. In that case, there was no temporary ban. Last year, you investigated, found the people who exploited egregiously, and banned them, without ever subjecting innocent bystanders to a temporary ban.We are not looking to punish anyone who accidentally stumbles into this
A temporary ban, even if it is reversed quickly, appears to be what people are concerned about, esp. since this wasn't something that you had used in the case of the previous high-profile exploitable bug.
The immediate disabling of accounts was because currency was involved. A rather rare and limited currency, which people could spend on items in the interim. Then you have the mess of not only needing to claw back seals, but potentially claw back the items bought with exploited seals. It is kind of like how a bank might be concerned if someone was exploiting and getting multiple free toasters when they open an account. They will look into it but it is not a critical emergency. But the bank will be in an absolute panic and start disabling checking accounts and ATM cards left and right if people are getting more money in their accounts than they are supposed to. Currency is a very, very different beast than potions or scrolls.
kringled_1 wrote: »
Except that in the case of the effected PS-EU players, it wasn't immediate, banning happened weeks after the primary event where endeavors were resetting. And just as problematic is the messaging around it. I'd guess that at least for some of the affected players, if the messaging were more along the lines of "unfortunately, we have to lock this account while we remove excess currency that was earned inappropriately due to a bug at our end" rather than the very accusatory initial messages, and the rather backhanded "well, you got your account back but be better at avoiding exploits in the future" for those that were restored, that the situation would not feel as heartless as it does.
Hi everyone, before the weekend starts, we want to provide an update on the current issue where daily Endeavors are sometimes resetting more often than intended. We are aware this is happening, and we are currently investigating solutions for this. While the investigation continues, we would like to remind everyone they should not exploit this issue. While we understand some people will unknowingly run into this through normal play, we will be monitoring and banning those who take extreme advantage and exploit it. Once we have additional information on a fix, we’ll follow up on those next steps. Thank you for your understanding here.
kringled_1 wrote: »Dagoth_Rac wrote: »@ZOS_Kevin I think the controversy stems from the temporary banning that happened. Last year, there was an exploitable bug that allowed people to claim daily login rewards multiple times. In that case, there was no temporary ban. Last year, you investigated, found the people who exploited egregiously, and banned them, without ever subjecting innocent bystanders to a temporary ban.We are not looking to punish anyone who accidentally stumbles into this
A temporary ban, even if it is reversed quickly, appears to be what people are concerned about, esp. since this wasn't something that you had used in the case of the previous high-profile exploitable bug.
The immediate disabling of accounts was because currency was involved. A rather rare and limited currency, which people could spend on items in the interim. Then you have the mess of not only needing to claw back seals, but potentially claw back the items bought with exploited seals. It is kind of like how a bank might be concerned if someone was exploiting and getting multiple free toasters when they open an account. They will look into it but it is not a critical emergency. But the bank will be in an absolute panic and start disabling checking accounts and ATM cards left and right if people are getting more money in their accounts than they are supposed to. Currency is a very, very different beast than potions or scrolls.
Except that in the case of the effected PS-EU players, it wasn't immediate, banning happened weeks after the primary event where endeavors were resetting. And just as problematic is the messaging around it. I'd guess that at least for some of the affected players, if the messaging were more along the lines of "unfortunately, we have to lock this account while we remove excess currency that was earned inappropriately due to a bug at our end" rather than the very accusatory initial messages, and the rather backhanded "well, you got your account back but be better at avoiding exploits in the future" for those that were restored, that the situation would not feel as heartless as it does.
spartaxoxo wrote: »"This account has encountered a bug that allowed it to more seals of endeavors than it should have, as a result it has been temporarily suspended as we investigate this issue. If it is determined that no fraudulent behavior occurred, the account will be restored. We apologize for the inconvenience. Thank you for your patience as we investigate this matter."
Hi all. Just wanted to follow up here based on some of the feedback. Our intention with highlighting the Endeavor reset issue is to be proactive with the community, noting we are aware of the issue and working toward a solution.
We do not expect players to be monitoring their endeavors in fear of accidentally encountering the exploit, and we'd like to highlight the Endeavor resetting is not a widespread issue and is pretty rare to trigger. In addition, we have a better understanding of the issue and have set up systems on our side to see when someone is specifically exploiting. So if you accidentally run into the issue, you don’t need to worry about having your account actioned.
We are not looking to punish anyone who accidentally stumbles into this, but rather inform the community about an issue we discovered and warn that we will take action on those who take extreme advantage of it (which, again, is not accidental.) We hope this helps to clear up any concerns here. Thanks for your patience and understanding regarding this.
Is this "kill with class skills" or "kill with weapon skills? I have ongoing issues with these, as my mains (who are the ones doing the endeavors) are all wardens - and it takes me a bit to remember to either summon the bear (if kill with class skills) or dismiss the bear (if kill with weapon skills).
Which is why I generally don't do either of them....
MidniteOwl1913 wrote: »
Is this "kill with class skills" or "kill with weapon skills? I have ongoing issues with these, as my mains (who are the ones doing the endeavors) are all wardens - and it takes me a bit to remember to either summon the bear (if kill with class skills) or dismiss the bear (if kill with weapon skills).
Which is why I generally don't do either of them....
Also dismissing companions seems to help. But yes I notice that even when I am careful to only use weapon skills some of the kills don't count. I have no idea why.
MidniteOwl1913 wrote: »
Is this "kill with class skills" or "kill with weapon skills? I have ongoing issues with these, as my mains (who are the ones doing the endeavors) are all wardens - and it takes me a bit to remember to either summon the bear (if kill with class skills) or dismiss the bear (if kill with weapon skills).
Which is why I generally don't do either of them....
Also dismissing companions seems to help. But yes I notice that even when I am careful to only use weapon skills some of the kills don't count. I have no idea why.
I don't use companions, so that's not it for me. But yes, I do notice that ever if I'm NOT just a space cadet, and even if I "fix" the bear (depending on the actual endeavor), it still doesn't work all the time.... I do have to say though, that my mega ping could be my issue.
boi_anachronism_ wrote: »Finedaible wrote: »Lets play roulette then. Certainly our odds are good, right?
... Right?
Zenimax is not playing roulette. They would be looking for specific behavior to determine who they banned up front.
Ok so for example the weekly is "complete 3 trials" i run idk how many a week. Or "complete 6 dungeons" i do way too many to count across all my toons. Id rack up thousand in endeavors. If im farming for gear i may run a dungeon 20x in a day. Do 1 dungeon is a daily very frequently. For those that pvp "do x amount of damage with siege" you do that in like 10mins.
spartaxoxo wrote: »Finedaible wrote: »Lets play roulette then. Certainly our odds are good, right?
... Right?
Zenimax is not playing roulette. They would be looking for specific behavior to determine who they banned up front.
They literally stated that they unbanned a ton of people because it was determined they had not met their criteria.
SimonThesis wrote: »@Zos_Kevin Why wasn't this issue caught and resolved in the PTS before mass amounts of players were banned then unbanned?
Hi all. Just wanted to follow up here based on some of the feedback. Our intention with highlighting the Endeavor reset issue is to be proactive with the community, noting we are aware of the issue and working toward a solution.
We do not expect players to be monitoring their endeavors in fear of accidentally encountering the exploit, and we'd like to highlight the Endeavor resetting is not a widespread issue and is pretty rare to trigger. In addition, we have a better understanding of the issue and have set up systems on our side to see when someone is specifically exploiting. So if you accidentally run into the issue, you don’t need to worry about having your account actioned.
We are not looking to punish anyone who accidentally stumbles into this, but rather inform the community about an issue we discovered and warn that we will take action on those who take extreme advantage of it (which, again, is not accidental.) We hope this helps to clear up any concerns here. Thanks for your patience and understanding regarding this.
No, it won't. Or if it does, it's only in the short term. Just wait until the next ban wave and the forum explodes again saying they need to change things (and knowing ZOS won't change). For reference, ZOS has a history now of seemingly randomly banning people over crown trading (early days TCE EU and Crown Exchange lost a lot of sellers because of this), gold duplicating because an addon was automatically taking gold from mail (but the gold wasn't actually being duplicated), and now this. And let's not forget the people who have been banned in the past for reporting bugs. I understand that it's one of the parts to the mail saying that they want to verify the contribution, but why is it ban first and ask questions later? What don't bots get banned this fast?FeedbackOnly wrote: »You did good. This will addresses community concerns.