Skip to main content

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

Structure of a game

A game normally consists of some challenges to overcome. This can appear in the terms of a campaign, chapters or skirmish(battle-only) levels. Challenges can be single-player or multiplayer.

On the development aspect, this means the Game Design Document must include the core game mechanics.

Furthermore, games include a certain quality of graphics, while some have no emphasis on graphics whatsoever.

But have would one implement graphics in a GDD? Myself I find it an impossible task. While I'm not saying some games don't have remarkable graphics, I don't think they have a place in the Game Design Document.

Another example is game physics. They can be described even if they are set in normal ("real") physics environment.

Let's try to describe graphics in a GDD by an example:
All levels need great textures, lightening effects, weather system, beautiful models and landscapes.


Let's try to incorporate this into test-driven development:
All graphics must start with average textures, and make sure the graphics aren't good from the start.

Nothing too specific, in other words.

Does this mean if it doesn't belong in the GDD, it is not important in the game either?
What does also not belong in the GDD? In example, music does belong, even though it is not easy to define.

Let's return to the challenges example. How would we implement it in the Game Design Document?
Challenge must include a good difficulty curve/line, they must be various and interesting.

Also not anything too specific...

What would an above average game's structure look like then? I believe it would require something easily defined in the GDD! What is easily defined then?

Here's an exercise:
Why did you find a game hard or easy or better yet, why did you find it too hard or too easy?

I think every game belongs in both of these categories.

What I think can be specifically defined in the GDD is the very definition summary of a game:
-what does the game teach us then?
-what kind of skill would it require for it to be beaten? casual, advanced or hardcore?
-what would require from one to immerse him/her in the game?
-what kind of genre is the game? does it push towards the boundaries of the genre? is it too mainstream?

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