Saturday, February 9, 2013

Cease Fire 2010 (2021?)

oh, my head...

First off, this game can't even get its own title right.  On the game's webpage, it says "Cease Fire 2021," but when you download it, the file is called "CeaseFire2010."  Let this set the mood of inconsistency and confusion that characterize this game as a whole.

I wasn't being sarcastic earlier.  This game actually gave me a headache (though that may also be from rolling down a hill head-first during a sledding trip earlier today).  I had to play without sound, because the gunfire sound effects overlap upon each other, amplifying them to the point of being agonizing.

The real problem, though, is the gameplay.  Oh God, the gameplay.  You cac pick among a variety of classes, which should make for good team-based combat.  The problem is that each class is unbelievably frustrating to use.  The control is off the walls!  It's hard to explain, but the targeting reticle is always relative to the front of your vehicle, meaning moving the mouse one direction will yield any one of 360 results, depending on where you're facing.  Trying to control something this batty while moving at speeds that are either way too fast or way too slow makes for one frustrating experience.

Honestly, though, I like that this game exists.  It has much more of a right to be here than games like Cat Nap, which, in my opinion, teaches us nothing about game design.  Cease Fire Whenever, on the other hand, is a brilliant example of how to make every single aspect of a team-based shooter frustrating.  Think of it as a sort of how-to-not guide on how not to program a game.  I think a game developer would do well to play this game in order to learn what makes games frustrating.  This knowledge may end up improving the medium as a whole.

Obviously, this game is far from getting my seal of approval.  However, I'm glad I experienced it.  Give it a shot to see how frustrating a game can truly be.

Links
https://www.digipen.edu/?id=1170&proj=510


No comments:

Post a Comment