Cryptic, do you even bother testing your patches or running them through quality assurance or anything?
I'm just asking because:
We are reverting the remote contact changes for now as it was block progression for some players until the system is working as intended. For now though, we are removing all restrictions.
This isn't the first time you've patched in a fix or a change and then yanked it because it wasn't working. It seems to me like you guys use the "Trial and Error" method of making games.
Rather than giving us broken and half-working patches, why don't you take a little bit more time to actually insure that they work before releasing them to the public.
Comments
http://www.pcworld.com/article/189210/microsoft_pulls_patch_that_causes_blue_screen_of_death.html
http://www.toyota.com/recall/
etc, etc
It's not an excuse, but an explanation. **** happens.
Yes. Bad things have happened before so this bad thing is OK.
I need to remember that if I am ever convicted of something... I will just tell the judge that someone else has surely done it before so my actions deserve no question or scrutiny.
go work in the software industry for a few years and you will understand
as a general rule of thumb, every bug you patch creates one more you don't catch in your QA test plan.
To put it succinctly ... yes, they do test their patches. Thoroughly.