Skip to main content

Game development is hard (part 2)

People understand the game development as something very exciting,
and it is, but that doesn't make it an easy task, in fact far from it.
All game development, especially coding is hard. And all good games

that were ever made, were or are big projects. It takes money and
effort to make an out-standing game, that will people will play for
decades.  Personally, I find coding the hardest part of all game

development. Most people think that becoming and being a coder only
requires schooling, learning coding every day and coding. But the
truth is that coding is hard. It takes a lot of studying and coding.

Having a MIT degree won't hurt anyone, either. Game coder is a vital
and crucial position in a game development team of a business or a
corporate company. The most important part of the development team, in

other words. I am not saying that game art and level design and game
design are not hard either, but coding is a notable exception. My
main advice when it comes to coding, is:

1.write a line of code
2.repeat

In other words, practice coding. Here is a good c++ learn link:

www.learncpp.com

But real learning of c++ comes from having a lot of personal
experience, not from reading tutorials. And here I am not referring to
practice versus theory. Theory is just as important as practice(in

spite of lower priority). What I mean by personal experience is to
just write a lot of lines of code every day. What regards game design
and level design, I could suggest making design images instead by

painting(=microsoft paint).

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 4

Object is either two dimensional, or three dimensional. Even abstract ones. People imagine c++ game objects as a part of a class on a graph chart, to understand the game and development mechanics. But they are really two dimensional, iso metric or three dimensional. They can be seen on the level or the level map, in other words, about 90% of used classes. Even server objects can be seen on the game, if there is any blue print or underlying real world net working mechanism. So in other words, the class objects can be used in game. They have to be dimensional. //PvE class Monster {     std::vector<int>  head_memory{};     std::vector<int> body_particles{}; public:     int get_memory(int element);     int get_particles(int element);     int get_head_memory_size();;     int get_body_particles_size(); }; Monster's head memory is used for AI render, the body particles list is used for rendering. 60 frames per second...
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