Skip to main content

Early demo file.

 The player model and equipment is a little old.
I'll probably be redoing them later with higher poly count and better textures, but for now they serve well enough for testing.

I'm releasing an early demo file for testing.
You'll need a fairly modern graphics card if you want to get the full experience, non-existent graphics cards or very old ones will give strange results.

You can pick up the demo from here.

Here's the instructions I posted on the Blender Artists thread where I usually go for feedback and game engine related support:

I've been doing a lot of work on this and I could do with some feedback.
You can move the character around the map by using the left mouse button and clicking on a tile within her run distance (about 15 squares).
Pressing space will freeze the game and bring up the mini-map. I've not added the keys for going back to the main game yet, so you'll have to esc to exit. It's just to see the map and give feedback.

Right clicking on a valid square will place a slime monster and as you move the game should give feedback about your LOS to that monster.

Not much to do yet, but I'd like to hear from you as to whether all the textures are showing up OK and if there's any strange behavior. I also need to know what kind of frame rate people can get from the game at this early stage. 

For non blender users you'll have to download Blender from Here.

You can make the game run by pressing the "p" key on your keyboard.

Later I'll be bundling the game as an .EXE or whatever so you won't need Blender to run it. But this is just an early test of the game environment.


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 …