Skip to main content

Level design basics, part 11

Hard level design
To make a hard level, you have to apply challenge methods, used on
steam games: achievements are very hard to get. Especially when it comes
to magic games. I had a lot of fun playing bridge crossing in americas army.

Also the FBI in counter strike. Very simple level design, but lot of hard
challenging fun. Traditionally, people think some easy games are fun. But
they really aren't. Making a fun map level requires making a good challenge

structure.

Example hard level design
A good challenge structure: must be directly related to the core steam
mechanics. Pacing is important in hard first person shooters, so if you
ever played a first person shooter, on steam you'll see the achievements

are really hard to get. So the steam basically works just like level design.

secret.bat
get on the 300th level

Steam is a system of games, level design is like a system of levels. Levels
in steam games; or at least some include achievement, so it's important to
under stand steam script code. It basically connects the game and the valve

server. Valve server process many levels every 10 seconds. And the load
that goes back to the game client can quickly over load the server. It reports
back to valve server, but the number of game clients running simultaneously

could easily over load the servers. Which is why it's important to design a
game that has low level data load. This is done by separating data files in
10 segments. Each segment should have about maximum 10 files. These

10 segments mean 1 level, not a chapter or a campaign. A hard level should
have fun achievement connection points. This is done by separating level
objectives into two levels: first is normal tasks, second is achievement tasks.

A hard level is hard to beat, but it will save you the troubles of making a fun,
challenging system. What is hard when making a hard level map is including
all the achievements in one map batch. It is one thing putting them in a

2 dimensional map editor, but a lot harder in the unreal engine editor. Unreal
engine requires a lot of work to create a 3 dimensional map: scripts, three
dimensional objects, progress lines, principle design; I tried making in the

editor.

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