Monday 28 June 2010
, by Teatime
So here I was, expecting the Macupdate actually being the prelude to the engy update.

Okay, that assumption was probably quite naïve to begin with. Valve released the game on a new platform, and maybe they were (for once) smart enough not to rush into other things, but instead waited to see how this new branch is doing, if any problems occur or bugs pop up needing fixing.
Also that update was released just before E3, so I guess the guys of Valve had other things on their minds as well. You know, this game obsessing with cake. [1]
But I also remember vividly the “Coming Soon” teaser accompanying the 119th update celebration. Okay, TF2Wiki expressively defines “Coming Soon” in Valve time as equivalent to “Not soon enough”.
But then there was also the comic featured on the Macupdate ending with a bloody cliffhanger.
Ah well, we will see. As I’ve mentioned before, this is an update I’m awaiting with mixed feelings, since engy is my favourite class. I’m curious about the new toys Valve will have in store for us, but of course I’m really hoping it will be some useful weapons or items really helping to make up for some of the disadvantages the other class updates have created for the engy, rather than being treated the same disappointing way scouts and demos were.
But also I’m dreading the myriads of people playing engy after the update and the number of people playing engy more often even afterwards. Not that I basically mind, a good engy is always a great addition to a team. But reason dictates that a team should only have so many engies. Too many engies are usually either rubbish or – in those rare cases the engies are good and cooperating – unbalancing. So more people playing engy interferes with my chances to play engy. Well, tough luck, I guess
Maybe I should pick up spy? Nah, probably no fun backstabbing engies when there are 6 sentries around you. In those cases: Medic. Nothing gets rid of 6 well-placed sentries (and trust me, far too many will be well-placed – read: next to each other) than a ubered demo.
If I’ve learned one thing in the last (almost) three years: Most engies have no stamina. Once they have been handed their ass to them a few times they will usually switch class very quickly. Probably to sniper. So I know I will get my opportunities again soon enough 
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
-
Obviously I couldn’t agree more with your comment on Demoman ubers. I implore everybody to uber me continuously during the post-update phase!
Also, you may be interested in todays blog post, it does seem to hint at an update rather heavily.