Skip to main content

Level design basics, part 15

Game design and level design

They are very closely related. A good method is to make separate
document, that shows the relation points. Game design is like an arch
type to all other documentations. Which of course includes the level

design. One documentation doesn't go without the other. They are co
related, and both very important; two documents should do for the
entire documenation: of course as a document I don't mean 1 page or

any thing like that. Because an entire documentation of either can be
in one extensive document. But for better understanding and
comprehension; by then two documents are optimal. Level design

documentation is mostly and most oftenly a part game design
documentation. Level design is paramount part of game design. It
supports the whole structure together. It is very important, in other

words. A good way to start doing that is by making a separate game
design document. Or a level design section. Write all the references
to the level design documentation. What they both share in common is

the word "design". Designing a level is more than just planning it
and then designing it. They inter vine with each other. They are co
related. They don't go one with out the other. And so they both

require a giant ammount of effort. Making a campaign takes time,
effort and dedication. Game design basically covers all game aspects,
what makes it out standing from other games, game play querks,

challenges. Level design is not only writing about levels, but
covers data as well. So can game design. Data is crucial for the game
to not over flow the computer system with memory information. It has

to be stored in data bases. Game data design can quickly cover a lot
of game design and level design in over lap. Data is a very complex
infomation structure. A data unit basically contains a lot of bits

of information. So there is actually a lot of document over lap
between game design and level design. They are very deeply inter
related. As they cover all other design parts of the game, including

code design.

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