Skip to main content

Large Monsters in game.

After spending a lot of time going through the code and adding in some special conditions I now have large monsters working pretty much as I want them. Well, as far as movement is concerned anyhow. When it comes to combat there really shouldn't be any trouble, it'll just be a case of checking which characters are next to the occupied squares for the intention of performing an attack.

One of the big monsters in game. The green circle represents the "home" square from which movement.

I've prepared a video which shows how the routes are calculated and how it looks in game.
You can see it below:



Working on this has thrown up a whole host of issues with the code so far. There'll be a lot of polishing going on over the next few days. One problem is that at times the game was calculating things based on a static floor height of z=0.1 rather than a dynamic z=walkmesh_data height. That will have to be corrected if my later experiments with variable height floors will work. Another problem was that many things were using the player object's world position (dependent on the visual representation of the player, i.e. object orientated) in their calculations, when they should have been using the character's ['xy_location'] (a property dependent on the walk mesh dictionary, i.e. data driven). This is one of the hazards of having a data driven game system represented by an object oriented visual overlay. Data can influence visual representation, but visual representations should not at any time influence the underlying data.

In theory you could strip away the visual representation and replace it with an old school roguelike UI, or upgrade the graphics engine, or transmit the data across the internet for a multiplayer game, without the local visual conditions having any effect. One player could be using an ASCII display, while another could be using a 3d display and it wouldn't matter.

Well, that's the idea anyway. :)  I'm not sure I'll ever follow through with that scenario, but it's something to consider when making the game.

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…