Skip to main content

Nearing the end of player movement development.

I'm getting nearer to finishing the current part of development, handling player movement during the movement phase.

There's still a few parts that I'll have to come back to later, but for now the player's characters move as they should. They don't walk through walls, they don't fall in to pits or walk on water.

Here you can see a small party of adventurers.
Left clicking on an empty tile of the map will send the selected Character there if the path is valid. Left clicking on another Character will select that Character.

If the distance exceeds your normal movement range your character will run, if it exceeds it by double the amount you won't be given the option of moving there.

Improvements are needed, such as showing which character is selected. Being able to select characters by portrait if they are not on the screen (or using the in-game map).

For the next part of development I'm going to be saving a dungeon to disk and working from that dungeon each time. That will make it easier to track changes, compare results and continue the development arc.

I've planned carefully so that any one part of development can be carried out in any order without causing too much disruption, though the natural next step will be player and monster stats.

Once I have the ability to give stats to entities I'll be able to set them up with basic equipment for combat development. Monsters use most of the same code for movement as the players so it won't take much to set them up for movement, however I will have to give them a basic AI.

Here are some of the planned stages of development:
  • Basic player character and monster stats
  • Hand to hand combat Combat (+ Monster AI for that)
  • Ranged combat (+ Monster AI for that)
  • Magic (+ Monster AI for that)
  • Monster spawning
  • Player skills and development, leveling
  • In game UI (It's going to be quite minimal anyway, you'll get a lot of feedback from animations and player/monster behavior)
  • Inventory management and item usage (+ Monster AI for that)
  • Doors and keys
  • Map visibility
  • Traps
  • Secrets
  • Puzzles
  • Menu screens (and some graphics for them, probably some high poly versions of in game equipment laid out in still life)

Sigh, lots to do, but at least I've done a lot already. Most of those stages will be able to use some of the existing code so it's going to go a lot faster once I get going.

Before I go any further though I'm going to have to do some tests regarding the graphics for the game. There might be some big visual changes soon, but they're unlikely to affect the game play.


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…