Skip to main content

Level design basics, part 6

Blocks

It takes a lot of building blocks to make a video game level. Video games
are after all nothing but very sophisticated and complicated toy games.
You can start by making very small pieces of code, say ten of them. After

put them in separate files and connect them together. Using JavaScript
should do a good trick here. TypeScript defines code blocks, modules
and scripts. Forest campaigns are hard to make, but are real fun to play.

It is a great adventure, even if it is not a role playing game; and regard
less of the weather. Weather and weather conditions are two very
different things. Weather conditions are a clausal, all you have to is

switch a weather variable:

std::string weather{"sunny"};
weather = "rain";

That is a good way to implement into a video game. But weather is
something else, it's a cloud system. Very hard to make changing weather.

int weather_clouds{10};
weather_clouds+=1;

Pick the one you prefer and are capable of doing. So a major building
block could be a weather. Major building block here means 10 building
blocks put together. Or just one big one stand alone.

weather.cpp
void move_clouds(std::string land_index, int move);

land.cpp
std::string get_land(int index);

Connecting these two together:

wall.cpp
void make_wall(int x, int y);
void open_door(int weather_shock, int land_key);

Key here means a door unlock, related to a specific land part of the
map. The weather_clouds variable here is for calculating cloud
movement. As you can see, changing weather conditions and making

actual two or three dimensional weather are both hard, but still making
real weather is even harder. A good weather system is made in DarkFall.
A metaverse fictional world call Agon, has multiple planets circiling

around it. Counting clouds takes multiple variables, however:

std::vector<int> clouds{};

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