LogFAQs > #889898130

LurkerFAQs, Active DB, DB1, Database 2 ( 09.16.2017-02.21.2018 ), DB3, DB4, DB5, DB6, DB7, DB8, DB9, DB10, DB11, DB12, Clear

Topic List	Page List: 1
Topic	Blizzard built a "strike team" to put an end to Overwatch cheaters
Apocalyptic 11/06/17 8:34:07 PM #4:	He also pointed to a notification system thatll tell players when somebody theyve reported has been hit with some kind of action. Currently, Kaplan said, between 20 and 30,000 test players receive notifications via email, but it wont be long before notifications start showing up for all players in-game (as opposed to via email). The goal, he explained, is to make it clear that reporting does something and, to the reported, that their actions have tangible consequences. In the longer term, the strike team is also looking at machine learning as a possible complement to other elements of its anti-toxicity apparatus. At the moment, Blizzard is trying it out in the chats of both Overwatch and Heroes of the Storm, using it to determine words and phrases frequently associated with toxicity. Kaplan says similarly toxic sentiments are aired in both games chats. It remains disheartening, however, that things ever managed to get this bad in the first place. Kaplan said that he wished the team had put more of a focus on heading these issues off at the pass early on, but stressed that he did not feel the team was simply being lackadaisical or negligent when it failed to implement features like console reporting functionality in Overwatchs early days. Its kind of like The road to hell is paved with best intentions, he said. Console reporting was a big point of discussion early on, he said, but the team decided against it because, at the time, it would have required all console Overwatch players to also create Battle.net accounts, a small but annoying barrier to entry. But, I noted, that simply meant that the Overwatch team had dodged a bullet, only to get hit by a truck later on. Thats where were at now, Kaplan replied with a sigh. Best intentions, indeed. Kaplan feels like the team is on the right track now, though, and he wants people to know that this is not a problem theyre tackling reluctantly. People are fired up about this issue, Kaplan said. He used as an example a particular server programmer on the team who has recently become laser-focused on using the fact that he knows the code better than just about anybody else to deal with toxicity. Nobody had to direct him on that, Kaplan said. Theres a lot of passion on the team to tackle that right now. Hm... --- ... <cite>Apocalyptic posted [p:889898130] in Blizzard b... [t:75962944]...</cite> <quote>He also pointed to a notification system thatll tell players when somebody theyve reported has been hit with some kind of action. Currently, Kaplan said, between 20 and 30,000 test players receive notifications via email, but it wont be long before notifications start showing up for all players in-game (as opposed to via email). The goal, he explained, is to make it clear that reporting does something and, to the reported, that their actions have tangible consequences. In the longer term, the strike team is also looking at machine learning as a possible complement to other elements of its anti-toxicity apparatus. At the moment, Blizzard is trying it out in the chats of both Overwatch and Heroes of the Storm, using it to determine words and phrases frequently associated with toxicity. Kaplan says similarly toxic sentiments are aired in both games chats. It remains disheartening, however, that things ever managed to get this bad in the first place. Kaplan said that he wished the team had put more of a focus on heading these issues off at the pass early on, but stressed that he did not feel the team was simply being lackadaisical or negligent when it failed to implement features like console reporting functionality in Overwatchs early days. Its kind of like The road to hell is paved with best intentions, he said. Console reporting was a big point of discussion early on, he said, but the team decided against it because, at the time, it would have required all console Overwatch players to also create Battle.net accounts, a small but annoying barrier to entry. But, I noted, that simply meant that the Overwatch team had dodged a bullet, only to get hit by a truck later on. Thats where were at now, Kaplan replied with a sigh. Best intentions, indeed. Kaplan feels like the team is on the right track now, though, and he wants people to know that this is not a problem theyre tackling reluctantly. People are fired up about this issue, Kaplan said. He used as an example a particular server programmer on the team who has recently become laser-focused on using the fact that he knows the code better than just about anybody else to deal with toxicity. Nobody had to direct him on that, Kaplan said. Theres a lot of passion on the team to tackle that right now. Hm... --- ...</quote> ... Copied to Clipboard!
Topic List	Page List: 1