Skip to main content

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

Elements

Elements of an object or a subject can be hard to understand, because
they are well related to the chemical periodic system of elements.
Same goes for elements in a video game. Just like real world physics

and real world graphics can be made in a video game, so can be real
world chemistry. This includes xenon, titanium, radioactive platinum,
sicilium, carbon, dirt water, oxygen, hydrogeneric, helium, ether,

nitrogen, sodium and magnesium. If you combine dirt water,
hydrogen and ether, you get internet potential water. Obviously you
wouldn't need that substance in a video game virtual world, but it is

possibly required in some genres and game types, such as racing
games that have illegal driving chase helicopter interpol internet
patrols. Internet patrols basically work like store security

surveillance. The video records are then sent to (military) police
personal system criminal records facility. To make the helicopter
surveillance, you would need to apply internet potentially

radioactive water for the moving cameras. This means you have to make
actual real world cameras, not the graphics ones. In other words, you
don't make a point of view, but an actual real world surveillance

system. The point I'm trying to make, that a good game consists of
making and building solid elements. These elements then connect the
parts of a structure of development of the game and of the game

itself. One way to do that is to start with one element only. In our
case, we'll pick a base element. The radioactive planitum is
plutonium. So a base element is like an orbital element. To decide

what kind of a world the game will have (like planet Earth related)
and what kind of genre mix it will have. Then you connect the base
elements to all other elements of the game, that seem most important

to you. Elements work as a guide of you should you develop the game
and how the game will look like, based on your current development
of the game and the state game or in other words state of the 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 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