Skip to main content

Level design basics, part 14

Accuracy in levels

It takes a lot of accuracy to beat all the level's objectives. The
primary ones, not bonus. And it takes a lot of skill to be accurate
when firing. So it is very important to make accuracy based

objectives. The bonus objectives are really hard to get. Harder to
reach objectives are fun when based on weapon accuracy. Talking is
basically a good support for team work. So making ventrillo or team

speak support. Objectives are actually very small amounts of data,
but can take a huge place on the hard disk drive and on random
access memory. Memory banks business has a lot of problems with

small, but extensive ammount of data. To build a level, it will take
a very solid draft first. Unreal tournament 2004 has a very
challenging single player and multiplayer. I think that forest levels

can be awesome to play if done correctly and they provide accuracy
challenge. A good example be a small rectangular geographic level
with most objectives being at small altitude. Especially if there are

monster protecting it. A good example of such level design would be
a combat arena with 4 very hard places to climb on. Means it takes a
lot of weapon accuracy to even have a chance at bonus objectives.

Team speak can contribute to the accuracy and if there is enough
loyal team work. The hard to reach objectives at locked non standard
mission doors and higher altitude take a mastery of effort to take.

Wild forests are scary, but fun to play. There is enemy danger and
animal monster type danger every where, which is why it is fun, as it
is challenging. Challenge makes a level fun, which makes the game

fun. And challenges in life are fun too. Avoiding challenges is smart
if you are not ambitious and don't want to appear arrogant, but
avoiding challenges in life, just like in levels isn't much fun.

To apply accuracy in levels, use challenging monsters and opposition,
carefully pick challenging attack spawn points; for example in unreal
tournament 2004, skaars are really much fun to fight against.

Comments

Popular posts from this blog

static mesh render

Static mesh is a data compound of a three dimensional object in time and space. To render one, it takes a one big storage file that contains all the data about the object. That data has to be stored on a disk drive. The really tricky meshes to render are the flying ones. It's a completely different air pressure. The data gets written to a game memory log, it's a massive multiplayer online game, otherwise in the cloud, like Steam. To render one, the data from the level and monster data files to the monitor handling chip. Monitor handling chips vary based on personal computers, lap tops, operating system, processor and graphics car. Before a three dimensional object can be rendered it has to be fixed on memory, either random access memory or the disk drive recovery point. A three dimensional object data can take quite a large amount of memory, especially those used multiple times. Steam Cloud has it's own of handling data, so that it is persistent. A level is made of static m...

object render

To render objects with c++, it is first required to load them on the engine's heap. After loading the object it has to be integrated into the game engine's allocated memory. void integrate() {     direct_x_node.call(); } Modern games(after doom 2) take an insane amount of heap memory. Integrating all the objects on the level, can take 400 mb or random access memory (ram). The same memory has the chip effect on the working of the central processing unit. To completely render the object, the first step is to load all the textures, shadow models, parts, particles, inner model, render the object on the level map, all the corelations with the heuristics. It is very hard to render the inner part of the objects, such as anatomy or infra structure. While it is perfectly fine to just render the inner part to not be displayed.  The anatomy of a player character or non player can be seen on the outside, and the internal strurcture of a level object such as a building, including the ...

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