"An additional source of disconnecting mid game was identified and a fix implemented; however, it didn't make the cut off for this patch so will be included in the next patch."
Out of curiosity, why doesn't something like this get hot-fixed? We hot-fixed LRM damage and other crash bugs... why wait an additional two weeks?
Re: Bug Update
Started by Michael Costanza, Apr 18 2013 10:23 AM
4 replies to this topic
#1
Posted 18 April 2013 - 10:23 AM
#2
Posted 18 April 2013 - 10:34 AM
They didnt hotfix lrms...
They spent a total of two days coming up with a stopgap solution so they could work on a real one with an ETA of may.
A hotfix would have been an actual (Complete) fix, not a "this feels right" but we'll actually fix it next month.
They spent a total of two days coming up with a stopgap solution so they could work on a real one with an ETA of may.
A hotfix would have been an actual (Complete) fix, not a "this feels right" but we'll actually fix it next month.
#3
Posted 18 April 2013 - 11:05 AM
Michael Costanza, on 18 April 2013 - 10:23 AM, said:
"An additional source of disconnecting mid game was identified and a fix implemented; however, it didn't make the cut off for this patch so will be included in the next patch."
Out of curiosity, why doesn't something like this get hot-fixed? We hot-fixed LRM damage and other crash bugs... why wait an additional two weeks?
Out of curiosity, why doesn't something like this get hot-fixed? We hot-fixed LRM damage and other crash bugs... why wait an additional two weeks?
Short answer?
"Computers are hard."
#5
Posted 18 April 2013 - 04:51 PM
I work with computers. I know the deal. Just felt it was a decent question. Even more important than, say, 12v12.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users















