Tuesday 18 August 2009
, by Teatime
OH MY GOD, VALVE RELEASED THE UPDATE WITH A GAME-BREAKING BUG!
And then those lazy bastards even dared to leave their desks for the weekend.
This cannot stand!
This is the result of sloppy development, of insufficient testing and displays a total lack of respect for their users and customers.
People like that only learn the hard way. So I petition, I even urge you to stop playing TF2 immediately. In fact don’t buy or play any more Valve products until Valve have regained our trust by making their future updates and releases a 100% error free. To increase the pressure don’t make any more purchases via Steam. Let the other game developers take note that we will no longer tolerate this careless attitude towards the products they expect us to pay for. Studios! Don’t hide behind schedules and release dates. We gamers are known for being patient. We want our games working perfectly. And yes, we want them now. This is not asking too much. Don’t hide behind technical errors. You are working in the computer industry, for chrissake. If you can’t master you tools get a job as janitor. And don’t hide behind human errors. If you are well trained, intelligent and focused you won’t make errors. Otherwise: Get lost. Work in a financial institution. I was told those are very error tolerant.
Ah heck, I don’t think such a movement of consumer rage should be limited to games. The whole industry is corrupt, spoiled and rotten. We HAVE to send a message!
Stop using any application which wasn’t delivered to you error free. Demand back your money for every program which shows bugs. Return every piece of hardware with faulty drivers. Don’t use Windows. All these security leaks and countless other bugs are just the result of sloppy programming and rushed development. A single bug in Mac OS? Throw it into Apple’s face. And don’t get me started on Linux. Thousands of people working on an OS and they can’t avoid bugs and errors? I don’t care if you don’t get paid for your work. Do it right or don’t do it at all.
I call out for a general strike. Boycott computer applications. Do it now and do it without mercy. Only with drastic measures like that they will ever learn.
And for the future: When buying any new program demand a certificate that this program is error free. Demand a lifelong money-back guarantee on occurrence of the first error.
BTW: Valve fixed the rocket-jump bug with last night’s update.
But too late, Valve. Fixing a bug on the first workday after its occurrence isn’t good enough. You won’t console us so easily this time. Feel our wrath and fear our vengeance.
Now excuse me. I have to look for that old typewriter I once had. Please note that the next editorial of the Fort will be delivered to you by mail.
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/safehtml.php on line
348
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
46
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
48
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
49
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
50
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
52
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
53
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
54
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
86
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
93
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
102
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
109
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
116
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
123
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
131
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
220
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
222
Deprecated: Assigning the return value of new by reference is deprecated in
/home/teatime/thefort2.net/htdocs/ecrire/lib/safehtml/classes/HTMLSax3.php on line
224
Discussion
-
You forgot to mention that the developers must be personally punished for their code based imperfection / defects.
Like I said before - there is whining and nothing is error free. However, people have the opinion that some bugs (like this one) should have been very easy to spot. In the case of the soldier, did no play tester spot the difference in the jumping ability? I certainly noticed it and I don’t play soldier! 
-
To be fair Junta, I didn’t notice the bug until someone told me about it and soldier is my main class. The first few times I did RJs after the update I didn’t notice that I wasn’t going as high as usual, then when I did notice I thought I had just messed up the jump. So I can see how, at a glance, they might have thought there was nothing wrong with it.
-
Not to be rude mate, but the first bball server I went into was full of people whining about it!
As for the bug... I find it strange that a fix to the demoman’s jump, broke the soldier’s jump. Just seems like they messed it up a bit and updated both classes code. I think you’re right that people are overreacting to mistakes Tea, but unless we know that these mistakes weren’t easily preventable, how can we be patient and trusting?