Skip to main content

Large Monsters in game.

After spending a lot of time going through the code and adding in some special conditions I now have large monsters working pretty much as I want them. Well, as far as movement is concerned anyhow. When it comes to combat there really shouldn't be any trouble, it'll just be a case of checking which characters are next to the occupied squares for the intention of performing an attack.

One of the big monsters in game. The green circle represents the "home" square from which movement.

I've prepared a video which shows how the routes are calculated and how it looks in game.
You can see it below:



Working on this has thrown up a whole host of issues with the code so far. There'll be a lot of polishing going on over the next few days. One problem is that at times the game was calculating things based on a static floor height of z=0.1 rather than a dynamic z=walkmesh_data height. That will have to be corrected if my later experiments with variable height floors will work. Another problem was that many things were using the player object's world position (dependent on the visual representation of the player, i.e. object orientated) in their calculations, when they should have been using the character's ['xy_location'] (a property dependent on the walk mesh dictionary, i.e. data driven). This is one of the hazards of having a data driven game system represented by an object oriented visual overlay. Data can influence visual representation, but visual representations should not at any time influence the underlying data.

In theory you could strip away the visual representation and replace it with an old school roguelike UI, or upgrade the graphics engine, or transmit the data across the internet for a multiplayer game, without the local visual conditions having any effect. One player could be using an ASCII display, while another could be using a 3d display and it wouldn't matter.

Well, that's the idea anyway. :)  I'm not sure I'll ever follow through with that scenario, but it's something to consider when making the game.

Comments

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 …

Skynet

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 …