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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.
6 comments
Read more

Automating Level imports from Blender to Godot

  Recently I've been making some levels in Blender an importing them into Godot. There are only about 7 or 8 shaders for each level, not counting dynamic objects which will be added later. But to improve rendering performance, it can be a good idea to split the meshes up into sections. At that point you might be faced with a list like this: Or it might be even more chaotic, if you didn't use simple names for the objects in your level. So it can take a long time to sort out all the meshes, make them unique and add textures and so on. Blender imports with simple Blender textures, or with placeholder materials. This is sometimes OK, but if your Godot shaders are very different to those used by Blender, it means applying new materials to every mesh object in the level when you import the scene. I found that during the design process, I was importing and readying a level several times before I was happy with the final layout. So at first I was wasting a lot of time. In Blender, I us
3 comments
Read more

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra
7 comments
Read more