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.

Comments

Popular posts from this blog

Level design basics, part 2

An arch level design is hard, as it doesn't involve only polygon boxes, but also also three dimensional curve lines. If you ever played. Americas army 1, you'll know how hard it is to make a curve building, like the famous over played bridge crossing map. The point is to start. With one curve. Curve is not a straight line, but it's still a line. Means it is possible to apply lines into a three dimensional level. arch 0 0 1 0

static mesh render

Static mesh is a data compound of a three dimensional object in time and space. To render one, it takes a one big storage file that contains all the data about the object. That data has to be stored on a disk drive. The really tricky meshes to render are the flying ones. It's a completely different air pressure. The data gets written to a game memory log, it's a massive multiplayer online game, otherwise in the cloud, like Steam. To render one, the data from the level and monster data files to the monitor handling chip. Monitor handling chips vary based on personal computers, lap tops, operating system, processor and graphics car. Before a three dimensional object can be rendered it has to be fixed on memory, either random access memory or the disk drive recovery point. A three dimensional object data can take quite a large amount of memory, especially those used multiple times. Steam Cloud has it's own of handling data, so that it is persistent. A level is made of static m...

object render

To render objects with c++, it is first required to load them on the engine's heap. After loading the object it has to be integrated into the game engine's allocated memory. void integrate() {     direct_x_node.call(); } Modern games(after doom 2) take an insane amount of heap memory. Integrating all the objects on the level, can take 400 mb or random access memory (ram). The same memory has the chip effect on the working of the central processing unit. To completely render the object, the first step is to load all the textures, shadow models, parts, particles, inner model, render the object on the level map, all the corelations with the heuristics. It is very hard to render the inner part of the objects, such as anatomy or infra structure. While it is perfectly fine to just render the inner part to not be displayed.  The anatomy of a player character or non player can be seen on the outside, and the internal strurcture of a level object such as a building, including the ...