Skip to main content

Validation checks.

I did some coding today on the prefab builder. I want to get most of the possible functions in before I go and build a load of test prefabs. If not I'll have to go back and rebuild them, or build a bunch of new ones.

Since I'm hoping that later people will help to expand the game by making new prefabs I want to make sure the prefabs are valid before saving them.

This one is not valid. Need to add a message to state that fact eventually...

Right now I've only included a couple of checks, there are more I should add. Such things as checking if a prefab has any encounter areas set, if it has a valid walkable path from the entry hook to the exit hook (pretty essential to avoid game breaking prefabs), if it has any invalid door or stair placements and other things like that.

The check for stairs came to me when I was thinking of how to deal with stair containing prefabs vs non-stair containing ones. How can I choose the right kind in the right situation? Why should there be two types? Why not include stairs in every prefab? Then when placing the prefabs the algorithm can decide if the stairs are needed or not. If they are not needed then they can be replaced by plain floor tiles. If they are needed the level builder can decide if they should be stairs up or down.

This way makes it much easier to lay out levels and have down stairs match co-ordinates with the upstairs while still having stairs placed in logical locations, and having things such as door guard encounters and safe rest areas at the bottom of a new set of stairs.


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 …