Skip to main content

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

"I make games and I'm proud of it"

This is another interesting quote from Raph Kostert's "A Theory of Fun for Game Design". It represents a very important aspect every good game developer should understand. If you make games in pride of the processes, you'll enjoy it and most importantly, you'll realize you're contributing to humanity.

Why is that true? Because of what I've stated in the first part of the series. If we continually don't fight for a better game design and quality of development of every role in the process, world will not keep up with the need for really good games, the influence of games on other multimedia, books and all types of arts and sports will be affected. Which means the world is in small-chance, but high-potential danger.

I really am proud to call myself a game developer.

Comments

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() {   ...

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

Programmer's Role in Game Development -part 1: Better Code Organization This will be a bit different blog post compared to the previous. It will be a sub-series of the role of programmer in the game development. The first part of the sub-series will explain how a game programmer is more effective alone or in a team. Code organization is in my experience essential, as the amount of code quickly increases, especially if the game has many features. It includes: knowledge of the programming language, APIs, dev kits and make sure you know the techniques with which will you finish the project  list of steps to get there a clear to read and understand GDD a clear task list don't rush to learn everything about everything related to your project-set to make a project which you can actually handle(=have learnt 98%-100% about it) There you go, one step closer to understanding how to make a classic game.