Skip to main content


Following on from yesterday's brain storm I'm going to revisit clothing and armor briefly. Before there were four types of armor: Clothes, light, medium and heavy armor, as well as hats and cloaks.

I'm going to extend this to add robes, which can essentially be worn over your armor for extra visual distinction. I also added barbarian furs to fill up some of the slots created by adding the separate robes category:

New to the catwalk this season, dead animal wear.

I may extend these even more to make a whole new category of armor so that barbarians and the like can enjoy visually actuate representation on screen. I kind of hate seeing my barbarian walking around in purple elven chain mail.

I've also moved some of the magical armor out to be "unique" armor. There will be unique items in game, very rare and with their own graphics so they feel even more valuable.

Magical glowing high level armor!

I want to get all the weapons, armor and gear sorted out now because next up I'm going to be working on the inventory system and making equipment visible in game on the character models.

A mock up of my intended inventory system.
I'm going to aiming for a slot based inventory system, you'll be able to carry a certain number of slots worth of equipment depending on your strength. Picking up containers such as bags extends the number of slots available. If you drop the bag, you won't drop all the gear, but you won't be able to move until you reduce your load.

Enemies are going to have visually accurate weapons and armor (if any) just like the player. If you see a beast man with a battleaxe, you'll be able to take the battleaxe if you manage to defeat him.

Today I did some more clean up of the code, merging some stuff so I don't have to remember which object is handling which parts of the code. There is now a single object which hosts the scripts which drive most mechanics of the game. Next up I'll be moving some stuff away from GlobalDict which has been causing me problems and storing it as data in a property attached to the controller object instead. From there it can be marshal'd out for save games rather easily.


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 …