Skip to main content

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

Part 2 talks about difference between the terms "complex" and "complicated".

Complex versus Complicated

Let's first look at how we would define a complicated game:
-hard to understand
-too many difficult patterns
-sometimes even annoying
-won't teach you anything new

None on this list are good components for a good game.

On the other hand let's take a look at a oversimplified game:
-too easy to grasp, too hard to master
-too many simple patterns
-dull and idle entertainment
-won't teach you anything new

Notice how they both won't teach you anything new. Should teaching valuable real-life lessons be a trait of a good game? The last elements on the list made me guess if both sides really teach nothing new, what is the golden-middle?

Let's take a look at another term, called a complex game and how to define it:
A complex game is neither simplified nor complicated. Does that mean it can teach us something? Most certainly I believe this is the case. There are many patterns to be learnt and integrated.

I believe "complexion" gets us closer to a better understanding of a good game.

How to make a complex game then? There are several aspects to implement:
-has to have depth and non-linearity in story line
-has to teach something valuable for real life
-uses intelligent decisions which require smart behavior

Let's further explain the term "complex game":
It is not the same as "complicated game" as complex and complicated are two completely different and unrelated terms.

So what is a difference between a complicated game and a complex game?
Complicated game requires memorization of thousands of rules (by thousands I mean really thousands) in the game documentation. A complex game can have the same of rules, but the rules will be interconnected, easy to memorize. Another thing which distinguishes them from each other is replayability.

By replayability I mean to play the same situation/campaign/level/skirmish/mission in different ways.
To this contributes a non-linear story, variety of ways to beat a level(like many games give the boss a weakness, but this doesn't exactly grant replayability) and interesting game modes.

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

Level design basics, part 6

Blocks It takes a lot of building blocks to make a video game level. Video games are after all nothing but very sophisticated and complicated toy games. You can start by making very small pieces of code, say ten of them. After put them in separate files and connect them together. Using JavaScript should do a good trick here. TypeScript defines code blocks, modules and scripts. Forest campaigns are hard to make, but are real fun to play. It is a great adventure, even if it is not a role playing game; and regard less of the weather. Weather and weather conditions are two very different things. Weather conditions are a clausal, all you have to is switch a weather variable: std::string weather{"sunny"}; weather = "rain"; That is a good way to implement into a video game. But weather is something else, it's a cloud system. Very hard to make changing weather. int weather_clouds{10}; weather_clouds+=1; Pick the one you prefer and are capable of doing. So a major buildi