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

Make your game models POP with fake rim lighting.

I was watching one of my son's cartoons today and I noticed they models were using serious amounts of simulated rim lighting. Even though it wasn't a dark scene where you'd usually see such an effect, the result was actually quite effective.

The white edge highlighting and ambient occluded creases give a kind of high contrast that is similar to, but different from traditional comic book ink work.

I'll be honest, I don't know if there's a specific term for this effect in 3d design, since my major at university was in traditional art. I learned it as part of photography.

You can find plenty of tutorials on "what is rim lighting" for photography. It basically means putting your main sources of light behind your subject so that they are lit around the edges. It can produce very arresting photographs, either with an obvious effect when used on a dark subject...

..,or as part of a fully lit scene to add some subtle highlights. See how alive the subject look…

How to... build a strong art concept.

So you want to make some art assets for your game. The first on the list is a Steampunk Revolver for your main character to shoot up Cthulhu with. Quickly opening your internet browser you start with a Google image search. Ah, there is is!

It might be a good idea to find a few influences so you don't accidentally end up copying a famous design.

Just mash them up and you're ready to go! Off to your favorite modeling program.
But wait! isn't there more to building a strong design concept than that?

Of course there is.
One of the diseases of modern design is that of recursion. Everything is a copy of a copy of a copy. This is especially a problem with "historical" concepts. Over the course of that recursive process the concept becomes infected with modern design elements, and ends up looking very similar to everything else that anyone else has ever made.
If you want to come up with a really fresh idea, you have to get beyond secondary references and go look at real …


Ok, so it's not exactly skynet, but I have got my first AI state working, kind of.

The first state is "HOLD" in which case the agent stays in place where they are and shoots at any unit that comes in range. When I started writing this module, I found that the existing method of triggering actions wasn't good enough to allow the AI to choose the best weapon or target. It worked by simply sending a command to the unit to trigger the currently selected action.

If the action is valid, it triggered, if not it didn't.
That's fine for play controlled units, as that's all they need to do. But AI needs to know in advance if the action is valid. The player can get that info from UI feedback, but that wasn't available to the AI player.

There were three problems:

1. The UI feedback duplicated code in the action trigger function. These  two sets of code could get out of phase so that UI feedback was wrong.

2. The action trigger didn't give enough feedback for …