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

Popular posts from this blog

Level design basics, part 2

An arch level design is hard, as it doesn't involve only polygon boxes, but also also three dimensional curve lines. If you ever played. Americas army 1, you'll know how hard it is to make a curve building, like the famous over played bridge crossing map. The point is to start. With one curve. Curve is not a straight line, but it's still a line. Means it is possible to apply lines into a three dimensional level. arch 0 0 1 0

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

Coding

I find it extremely hard to code a game. It gets worse than that. I also have to do the game design, UI design, level design and the story. Basically lots of bugs, lots to learn, lots to design. The good news is I have a teammate and she works on level design and story. Helps a lot regardless there is tons of work to be done before even first of the three Trix games gets published. I sometimes work even 12 hours a day. Yikes!