Skip to main content

Level design basics, part 7

Meta files
Meta means in between. Wild hard ware and soft ware connection.
A game design level document is just documentation; it is normal
text. Actual level files however are en coded. Not normal text, in

other words; which is why they are a lot harder to make. Forests
for example are hard to put into a text file. Trees are real world eco
systems that are the source of nature and life. It is one thing to put

a real world object into a game, what is even a LOT harder is putting
one, for example a tree into a text file. Source code is just sofware,
it is nothing but encoded writing, which is why to put it into soft ware

is not exactly easy, but has been done many times before. However,
putting source code directly into hard ware is a completely different
thing. That's where meta files come in handy. Meta files are clay ware.

They work very similiar to a human brain. Like a connection between
software and hardware. A meta file contains level game design
documentation and level code. A structure of a level code document

is basically encoded data about the level's structure.  A good example
of a meta file application would be trying to implement a navy into
a game: like a naval unit. The only problem with making a combat game

is that it many times interferes with united states army official and
confidential information: a navy here would not mean type of combat,
more accurately a naval unit of 20 ships, each containing navy sailors,

pirates and soldiers.

Make files
A make file contains logs and caches of what was going on when the
multiplayer game client was running. They are used for breaking routine
checks. Developers can read make file reports, and then analyze the

players key board and mouse inputs. This analysis is used for tweaking
the game features: HUD means holo graphic user design interface.
The HUD in a game isn't just display information, but what matters

is also the contents it displays. A holo graph is a virtual reality element.

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

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.
Post a Comment
Read more