Skip to main content

Level Editor

You might ask why a game with random levels needs a level editor...

Well, roguelikes are not completely random.

Most roguelikes use predefined rooms in their level generation algorithm. Usually these are rectangles, but they might also be another shape, such as an oval or a rectangular donut or a cross.

I'm going to be doing the same, so that I don't have only rectangular or square rooms. But as well as simple primitives (square, rectangle, torus) I'm going to include quite a lot of themed rooms and even themed areas. These might include mazes or an array of dungeon cells or an underground fortress, or a subterranean village or whatever.

For that I need a quick and easy way of creating these prefabricated areas and saving them to disk ready to be called up by the game.

Introducing the prefab editor V0.4:


You can place rooms, corridors, stairs up and down, secret doors and encounter areas (the numbers on the map above).
The encounter areas are my favorite bit so far. They will be added to the level's dictionary of encounter areas and random monsters or treasure or furniture items will be placed there according to a theme when the level is created. There's a good chance that an encounter area won't spawn an encounter but if it does, the encounter parts should be constrained to the tiles specified in the level editor.

The level hook is a tile marked for connection to the other parts of the dungeon. There can be multiple level hooks, or just one. If the prefab contains stairs it will be stored in the "stairs" dictionary along with an entry detailing the length of it's longest edge, so it can be rotated or flipped and fitted in to the BSP generator I talked about earlier.

There will be a lot of prefabs built, so the chance of encountering any 2 identical areas is pretty low. In any case they may have a different tileset, different encounters, furniture or other features so they won't be instantly recognizable.

Comments

Popular posts from this blog

Back to Vinland.

I'm going back to my real time tactics project, Vinland 1936.
While working on the other project I overcame the problems which were stopping me from saving/loading the game and also cleaned up the base code a lot.

After a few weeks I'm getting near the the state I was in before.


Infantry are back to their previous state, and vehicles are running OK.
This time I'm going to push ahead with mocking up the combat system though before I work any more on the vehicle builder or graphical aspects of the game.

Rockets

I finished working on the code for adding foliage and having some extra time I decided to experiment with the code for rockets.

The original idea I had was that rockets would be large vehicle components that can be fired very quickly, regardless of how much manpower is used for reloading.






They would use up a lot of ammo, so they would run dry after a short but devastating barrage.
The problem here is that it's easy to take advantage of this by adding a lot of ammo, which is much smaller than in bulk than the rockets.

There's also the problem of firing large caliber rockets. In real life rockets of up to 30cm were used, but I think that will be too powerful for the scale of combat in this game.



lol. Somehow that one trooper survived the mother of all explosions...

A 30cm rocket could contain nearly 30KG of explosive. That would be a very large explosion.

I've tried to balance the game by using a simple equation to make bigger guns more powerful, but hopefully not too powerf…

Infantry combat and entering buildings.

I've been working a lot on the game recently and I've nearly rebuilt it to the level it was before. Past that maybe, since now I have the beginning of a working combat system and the ability to save and load the game.


Infantry can now occupy a building. It's quite an abstract representation, since they stay at the door and turn invisible. But they can then fire from one of the windows and take damage from shots at the windows too. I think I've set it up well so that when building damage and destruction is working then the system should continue to work.

For combat I tried some new ideas, but they didn't work out that well. It seems that it's important that viewing range should be further than shooting range. Now shooting range is pegged at 18 units of distance, while viewing range can extend out past that.

In the above image one unit has an officer, so has further viewing range. The other can only see as far as they can shoot, a dangerous situation since the en…