Riot are you even working on the thresh problem????
I would just think that you guys could fix it in 3 days.
I would just think that you guys could fix it in 3 days.
Friend, do you even know how much pages of code those Rioters have to go through to find the problem? It might even be a single incorrect number causing this shit. And if it's something bigger, they might have to re-write entire pages of code to fix it.
3 days = 72 hours. As long as they have enough people, im sure they could find the problem fairly quickly. If they find it and it will take a while to fix, why not give us an update instead of letting us wake up hoping its there?1
The problem might not even be in (DS) Thresh's files. They might have to dig way deeper, and see if some of DS Thresh's code blocks another piece of code that was already there.
And do you seriously expect those people to sit behind their PC for 72 hours straight?
I would expect them to have multiple people looking in different parts of the code and swap out with others when they go home. You knwo because some people probably work in the night?
That is not how this works. That is not how any of this works. And I'm not talking about the fact that some people work at night. Because that is entirely true. I'm talking about the fact that you think a guy can just tell his collegue ''Start reading from this line''. If you handed a piece of code to a different guy, he would have to start reading from the beginning to have ANY chance at finding something.
They don't work 72 hours straight. That's not how things work. Probably 8 hour works days+breaks+time doing other stuff, so its about 20 hours they've been working on it. Do you know how business's work at all?
Of course they dont 72 hours straight but they probably swap people out. So at least maybe 50 hours of work?
It's also the weekend, so probably not as much staff
The gravity of this situation is immense.
I know I'm late to this thread. First, apologies for the problem having in the first place. We have since disabled DS Thresh, and we have a team working on a potential fix. We are testing it over the weekend in hopes of a hotfix very soon.
To give some behind the scene context- once we get these types of reports- we attempt to get as much information as possible to see how widespread the problem was. We worked with our data analytics team and saw that this issue was pretty wide spread and made the decision to disable DS Thresh. So, when we say we're working on it- it implies we are studying the problem, seeing how wide spread it is, what types of players and machines it's happening on, are there other factors (ie server problems, latency problems, etc.). Once we determined it was for sure DS Thresh and in what type of conditions- we were able to gain enough information to make the call to turn him off.
Totally agree- any feature, skin, champion etc..that causes such widespread disruption should immediately be turned off to protect the overall player experience.
Thanks for sharing your thoughts. Genuinely, appreciate it.
Thanks but that doesnt really help me. Was hoping for something relating to how long they will be
It's litterally in the post you just read. They are investigating how widespread it is...
Nobody Fucking Knows
They are not stating a direct date, only that they are working to fix it ASAP. They know WHEN the problem is occuring, they just need to try to find WHY, get a fix, and make sure it actually works and it's not actually an underlying problem. It's a weekend, so the office crew is likely ligher than on weekdays, so it may be slower untill they can get the full team's heads working on it.
I'm really Going to be brutally Honest here but I really do not appreciate how Riot constant keeps us in the dark about issues like this. Yes I do see the post made by Pabro but that was a day ago. an ETA would be amazing :) I am a Thresh Main and I still need to buy the skin so please understand my tears of salt ;(
http://na.leagueoflegends.com/en/news/riot-games/editorial/total-recall-or-time-we-disabled-ranked
They explain how they had to jump through a bunch of hoops to fix a problem with Riven instarecalling. They had to close ranked queues. They don't like telling ETA's etc because;