Skip to main content

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.
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

object render, part 3

 Making a object requires a class call, but also has to be rendered. Monster monster{}; monster = new Monster[10]; void render_monster(Monster* monster_array); The iso c++ standard says you should use classes for making objects, not structs(structures). Considering it is a standard.  With emphasis on  should , not  must . It is a standard, not a coding rule. It was set forth by iso commitee and bjarne stroustrup. Polymorphism allows us to make multiple monster arch map types. virtual void render_monster(std::string map_name, int type=0); Atch map is a data map about what all is happening in the game, like for example campaign map. It allows making archetypes. monsters, for more efficient run time memory and pointers managing bugs and random access memory. Random access memory can hold quite many objects. class BackPack {     std::string inventory_node{}; };
Post a Comment
Read more

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

Small goals Challenges can quickly get out of hand, proportionally after have been playing the game for a while. That is why it is important to implement game goals as well. This work as a guiding force for challenge motivation. The terms challenge and goal have very different meanings. Imagine a call of duty 2 mission. It is a challenge, but lacks small goals that keep you motivated, and not beat the mission feel bored and drained and sore. Beating a video game is not exactly a small task. Takes accuracy, will, focus, concentration and understanding your opponents(including AI). An example small goal would a chunk of challenge. Like subsystem parts of a call of duty 2. This parts of a major hard challenge can then be used as a realistic take on or as a memory level map. Small goals are far from being bound easy either; but they are a realistic approach to beating a level. Example would be beating the level's extra challenges by breaking them down into chunks, such as level practic...
Post a Comment
Read more