Skip to main content

Concept: Monster Spawns.

Today I had some ideas on what to do about monster and room management spawns.

I want to add random objects, monsters and props such as tables to the map, but I want them to be placed in a way that makes sense and has some kind of internal narrative.

I don't want you to enter a room and see:
  • an empty book case
  • a skeleton
  • an elf
  • a potion of speed
  • a rug
  • a telescope
  • a green slime
  • some writing on the wall
  • a puddle of rats blood 
What I want is that you enter a room and see:
"Some guards standing around a table, on the table is a lunch buffet of green cheese and mushroom sandwiches. In the corner two guards are sleeping on bedrolls. A guard captain is sitting at a card table playing cards."
The above situation would be the result of three themed spawns:
  1. A table with appropriate contents and some appropriate monsters standing around it.
  2. Sleeping monsters on bedrolls (perhaps with optional equipment spawns nearby)
  3. A card table with one or more themed monsters. 
The spawns would be packed in to the room, if there wasn't enough room another spawn would be substituted.

I'd use a dictionary a little like this:
Yes, that's right arrays can contain function calls.

There are other indexes in the dictionary as well as the object spawn arrays, the level index would restrict spawns to different levels, the x_size and y_size are not really needed as you could just measure the array lengths to get that info, but you could include a theme key here such as "insects" or "horror".

The random monster function calls a random monster from the meta list of monsters using a guideline of max xp cost and starting state, allowing sleeping, frozen, stone or polymorphed (etc...) monsters to be placed.

With this kind of method you could have spiders (a monster) and cocooned prey (a prop), or a book case and scattered books (all props) or a barracks with beds, chests and sleeping guards and lookouts. Further refining the random monster function, you could use a wild card such as False or None instead ofXP amount to use XP from a general spawn pool (calculated in relation to the player's strengths and weaknesses). Or you could add an extra argument to the function such as monster type, which only adds monsters with that type to the random generation pool. A typical type would be "furry" which would generate giant rats, wererats, werewolves, cave bears and such, or "insect" which could generate all kinds of bugs, or "human" or whatever. The more tags you have, the more you can control the spawns and create more narrative for your game, but the more chance of getting an empty list.

For instance you spawn a monster formation on level one which includes a random monster call for a "demon". The xp pool is just 100 xp, but the lowest level "demon" monster is 5000xp. That's going to result in no monsters being spawned unless you have a fall back, like:

       monster_instance = monster("giant_rat", "crazed")

In which case the player is going to be so busy dealing with a berserk Giant Rat they may not notice the "pentagram" and "sacrificial_altar" props in the room.

The above concept may need tweaking a little, the final game is going to include props that can block your movement but also others that don't (such as a puddle). In that case it would be fine for a spawn location to include a prop as well as a monster or object. Objects could also be placed inside or on props (such as food on a table).
Imagine entering a room and seeing a zombie feasting on a fresh corpse, or an egg that splits open to release a juvenile giant spider.

Anyway, today I'm going to be experimenting with saving and loading and maybe try moving a player object around the map.

As a closing video I'm going to post this, which is exactly what I don't want my game to be like:


I hate the way you can upgrade the rusty helm (which doesn't look nearly crappy enough to be a rusty helm by the way) while still fighting and running around. How? Does he have an army of crafting gnomes stuffed into his loin cloth?
And you can speed up the upgrade by paying for it. Again, how does that work?
Although the worst thing was the massive in game tutorial pop-up which completely covered the bossfight (and the bosses spawn was ruined by happening mainly off screen).

No wait, the worst part was:

He had several special abilities, but there seemed little point in using them as every enemy fell to a few quick slashes of his mighty rusted sword.

I don't have full details of the combat system I'm going to use yet, but rest assured it will feature more than just tap=slash, and special abilities will be useful.


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.


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…