Then cancel the sub or play on a pserver or make your own. Jeez, have some sort of spine and atleast stop giving them ideas on how to screw you (the customer) even more.
The game is fun man, but it is not THAT fun.
Nope, heâs said it many times before. It doesnât matter, heâs objectively wrong. This isnât up for discussion.
And as I suspected, the document doesnât disprove anything regarding CSâs workforce not being substantially reduced. You have a very simple view of things.
I want the bots fixed better than what they have done. Thatâs all.
I would donate a dollar, one time, for that to happen.
I actively hunt bots, break their gear by kiting them into mobs, and report them. But for every bot I get reported and banned, they have 5 more to replace it already leveled to 60 through bots boosting bots.
The current system of report review then ban isnât working as the bots are getting worse.
Bot detection by computers would be easy. Blizz presumably has access to the client connection data from every person playing the game. The player input information is extremely tiny from a data point of view - Iâm a data scientist, not a game developer, but I assume the player inputs are transmitted as primitives, or maybe even at a lower like bytecode level? In any case, with access to this data, it should be fairly easy flag some known botters and known players, produce a large data set of labelled player inputs, and then train a neural net to classify botters. Given my experience with building classifiers, I am confident this would work, since the two classes of inputs are likely very different.
Sure, the botters will probably build in new features to try to evade this check, but once the Blizz people have this in place and running, all it would take is to have a handful of humans continually identifying and flagging new botters to keep training the ML algorithm.
I doubt Blizz is taking it this seriously though. This would require likeâŚyou know, a small dev team that costs money.
The document lists every single position that was cut in the February 2019 layoffs, this is a fact. Zero CS were cut, this is a fact.
Specifically, laid off In February of 2019.
My doubts of the information being 100% accurate aside, itâs only layoffs that happened in February, and it doesnât cover potential shifts in structure after said layoffs happend.
You can keep trying to sell me your simple take on the matter despite quite a good amount of reasons to believe otherwise, but Iâm not interested in debating this further. If you think no changes in CS have occurred since 2012, you are living in a fantasy land.
You linked a single businessinsider article that you believed because it suited your bias. I agree with not arguing this any further because youâre going to keep going in circles around the facts.
There hasnât been a reduction in CS force since 2012. Blizzardâs CS team numbers around 1,000.
Facts are hard on the false narrative, I know.