Skip to main content

Progress on Procedural Generation.

From the start the idea of this project has been that everything should be done as much as possible with procedural generation. I want people to come back and play it again and again.

That's not to say that there won't be a story, and non random elements, but the key thing is that you can replay it and get a different experience.

Anyway, I've been working on the random dungeon generator for some time, more than a year it seems, though I haven't been working on it continuously.  I got some ideas from existing random dungeon generators such as this one:


There were three things I wanted it to do:
  1. Create interesting rooms which are more than just rectangles.
  2. Allow different ways of joining the rooms through corridors.
  3. Use different tile types in the same map to avoid looking repetitive.
 The first thing required a bit of a different approach from normal generators. Normally we just set a room size and make a room but I used a dictionary of interesting room shapes. At the moment the dictionary contains a small sample so rooms are a little repetitive, but later I'll be expanding the sample and adding different dictionaries for each tileset.

I used arrays to represent the rooms which look like this:

"21":[["l"],[[0,1,0],[1,11,1],[0,7,0]]],        
The arrays can be rotated or mirrored to create new rooms from existing ones. I may write a function to merge room types too.    

I used A* pathfinding to achieve the second goal. Corridors are drawn automatically from each room exit making every room accessible. They can join in sequence or join all to the entrance to the level, or all to the exit.

The builder uses several different tile types to make the rooms, some can transition to other types directly, some can't. I used a transition dictionary to set which can and which can't That can be changed for different tilesets.

Here's what the result looked like using simple colored objects as placeholders:


 The generator created them very quickly, meaning that to create a whole dungeon of levels would probably be the work of seconds rather than minutes (I hate long loading times).

One other thing I'm working on is to create granular rock, some hard some soft, which helps clump the rooms together in to more organic shapes and also causes the corridors to snake more pleasingly. Where corridors have to be cut through hard rock they can be set to have a different appearance.

Finally here's a look at how it all fits together in a video:


You can see the red circles show where there is hard rock. Setting granularity high makes a very noisy image with small pockets of hard rock, this snakes the corridors just how I want, lower granularity makes the corridors avoid certain areas of the map which is also interesting.

Next up I have to work on getting the tiles ready to walk on. I'll be using empties added to the mesh to show which squares are walkable. When the level is loaded the empties will be used to generate a A* graph (taking note of which nodes are linked to doors) which will be saved as a set of dictionaries which can be accessed one at a time to prevent creating a too large graph for the A* algorithm.

There already exists several variables that can be changed to create more varied levels, such as room mirroring, number of rooms and level size, as well as type of room linkages and average room sizes. These are mostly not active at the moment but have been tested and seem to work fine.

Later I'll be adding further refinements to the generator script so that it can add multiple stairs up and down to exit the level, match the location of previous levels stairs to the current level, and also match up rooms from the level above in cases where there is a pit trap. But for now it works well enough for testing purposes.

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…