Skip to main content

Making prefabs.


Now the prefab builder is finally finished I can begin making prefabs. It's kind of fun, I get to dream up puzzles, traps, little bits of narrative for the game to make it come alive. it'll be more fun once the level builder is working and I can begin navigating around my creations in game.

I added some final finishing touches to the way prefabs are handled while saving. Now a border of wall tiles is added to the floor tiles, but the rest of the unfilled area is dig able. That means the tunneler will be able to join prefabs together more closely without leaving a big border around each prefab. Also the prefab is cut down to an array that includes only the area containing walkable tiles. Any empty tiles are trimmed. So a 4x4 prefab will only take up a 4x4 array, not a 20x20 array. Also empty lower levels are cut out and replaced with a [None] array if the prefab is a single level one without stairs. I've included some data with the prefabs in the dictionary to show if it is a single level prefab and how big it is. This will make it quick to sort prefabs ready for adding to the level builder.

I just remembered that I forgot to do something... Have to go and fix that. :)

In the mean time, here's a short video (click the image to go to youtube) of some prefabs I already made:
http://www.youtube.com/watch?v=BaCtvlmU5Z0&feature=youtu.be
Click for a video.


Comments

  1. I forgot to rotate prefabs when saving them so that the long edge is always on the x axis. That will help a lot when creating levels as I can check vs longest edge and shortest edge, then rotate prefabs to fit in the BSP space. I don't need to create unique long x or long y prefabs, as I can use the rotation script to make any prefab fit where it is needed. I also forgot to set the first part of the unique dictionary key string for newly saved prefabs to the length of the existing dictionary (+1), that resulted in a few prefabs being overwritten.

    ReplyDelete

Post a Comment

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…