Skip to main content

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

"The way it's meant to be played"

This is something I've been wondering about a lot lately. It is a trademark from Nvidia company which created Geforce. You have probably seen it in the Unreal Tournament 2004 intro.

Most people see it, but just take it for granted. To me it is an interesting pattern as I love to see details consciously and this one is the most interesting one to me as it provokes so many thoughts about the topic I'm writing about, which is how to make better games.

So what do you think it means? Fair play? By the rules(no cheating)? Unreal is a good game to play? Perhaps a thrilling challenge at hardest difficulties?

I think all of the above would be a good example of directions for a better game: fair play means a healthy competition while respecting opponents and teammates. By the rules means no cheating. I think I find cheating bad for the gaming atmosphere. A thrilling challenge can be a great.

But most important one is a "a good game to play". I think Unreal Tournament is an awesome game.
I learned a lot in it about real life. But what precisely makes it a good game? Answers are everywhere but all partial.

Personally I think "the way it's meant to played" signals passion and the game was made by gamers.

What is a good game then? I don't have the exact definition. But I can tell all the games created so far could have by far better game design, coding, story, music, quests and levels design.

My mission is to figure it out even though the definition might not be as a mathematical formula.
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

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