Skip to main content

What does a good game consist of? (part 12)

Unreal Tournament 2004 - Game Analysis

Keep in mind I'm not making a review, and no review score. I thought I would analyze a good game I enjoyed a lot; because it should get us closer to understanding.

Let's start with the no lying fact I never used any version of the Unreal Engine, but I can readily says it's complicated.

Graphics are awesome, but they only distract you from really immersing yourself.

What about the difficulty curve? I have to say it's awesome beating on Adept mode, even though it takes a very long to beat. But to beat a single level on Godlike, it's impossible unless you've played a long time and even more time on having superior reflexes and puzzling skill. Which I don't imagine myself doing it even though it would mean learning a new skill.

Why not? Because it would take a very long playing it to achieve basics competence with other elite players. Also I have great reflexes(I train Shaolin Kung Fu), but I can't win on Godlike.

Very good aspect of the game is AI or Artificial Intelligence. Skaars are really hard to catch.

I also like the hidden potential behind the point and shoot, which is a need for teamwork, knowledge of great weapons.

Level design of the game is made well. Unreal Engine rocks, but I prefer Direct X.

Why play the UT2K4 then?
I think AI, teamwork and cool weapons. Also the Onslaught mode.

It contains many modes, but I think Death-match has been copied in so many games, but Onslaught fixes the issue.
Labels:

Comments

Post a Comment

Popular posts from this blog

object oriented programming

Object oriented programming is a sound and bold approach to c++ and internet wiring application and video games. It reduces a lot of code messes, made by global and half global functions. One of the more advanced object programming techniques are private access, poly morph and object message inheritance. It is set by c++ bjarne stroustrup and iso isometric standard convention comitee to use classes instead of structs and structures for making objects. Which means you most definitely should , but not must or have to. class Monster {     std::string memory_attributes{}; public:     void treck();     void track();     void trace(); }; The treck() function makes the monster roam and do human like jogging and trimming. track() means the monster goes ai path tracking and trace() means it tries to find other monsters in the area. class Weapon {     std::string memory_attributes{}; public:    void use(); }; void Weapon::use() {   ...
Post a Comment
Read more

Coding and game development, part 2

 Consider the following C++ sample: int main() {     std::cout << template_1() << '\n';     return 1;      } Every moron who knows C++ would know what this means. Now consider that almost every line is a regular expression, so try to translate it into your native language, English for example; line by line in steps. ... rofl lol oO? I tried to do that with the example and my head almost had a system shutdown.
Post a Comment
Read more

C++ and OOP in a different manner

Keep in mind this article is meant strictly for C++ game devs and not for application programmers or game devs of scripting/other languages. I have my own technique when it comes to OOP in C++. The game I'm deving right now(or we are making) is a simple windows console project. It's up to you to decide whether you'll use this technique. First let me tell you in which cases you might need this technique: if you're ready for a new look on OOP if you need a new toolset for your coding practice if you like to learn(which I clearly hope for) So, the technique then. Decide which you prefer more: classes or structures. This helps you understand what kind of objects you want in a game.
Post a Comment
Read more