Skip to main content

In game map. To be or not to be.

From the start I wondered if I wanted to have an in game map, either a mini map or a separate screen that you could switch to to see the map.



One of the things I liked about the old games was there no in game map, if you wanted to map the game you had to do it by hand. So for a while I was sure I didn't want an in game map.

As time has gone on I'm leaning more towards the idea of making the game flexible.
Do you want an in game map? Yes, well you can activate it from the options menu before starting your game. Do you want permadeath? Well, it's available.

Most of the things I want to add, I'm not sure others will like. I know I will, but I'm not only making this game for me. So I'm going to add some options to turn off or on certain game play elements at the start when you generate your dungeon.

Here are some things that I've been cooking up for the rule set that may be optional:

  • Food and water consumption.
  • Weapon and armor wear and tear.*
  • Traps and teleporters.
  • Monster psychology and morale.
  • Player psychology and morale.
  • Crafting and potions.*
  • XP from monster combat.
  • Single player character or team play.
  • Permadeath.
  • Resting.
  • Resurrection Shrines.
  • Auto mapping.
  • Player location marked on the auto map.
  • Petrification and other one-shot kills.
  • Player wounds and semi-permanent critical hits.*
  • Random starting handicaps for player characters (like "partially blind", "oh my back!", "picky eater" or "greedy swine")*
  • Blood and gore.

When you choose the options that you want it will give you an overall difficulty rating which will affect your final score. Some things will also auto balance, such as XP from monster combat will reduce XP awards from events and achievements. Other things won't be triggered if certain options aren't present, such as the "greedy swine" handicap won't be added to a character if food and drink consumption is disabled.

If you want you can disable most of the hardcore options and sweep through the dungeon killing enemies like flies, but that's gonna make it pretty easy and IMHO pretty boring. On the other hand you can engage all hardcore options and get ready to be worm food. In any case, the options can only be set when you first start a dungeon, you can't just turn permadeath off because you're low on health it looks like you're going to get eaten.

*The options marked with a star are onces I'm leaning towards keeping as required elements. Wear and tear of items has been one of my key design points from the start. Some RPG games become boring because you find a +5 sword of decapitation and that's the best thing in the game. After that what's your motivation for looting? But what if your sword broke in combat, or became blunt. What if you were all out of whetstones and oil? Well, you could use a lesser weapon while waiting for some more repair items to turn up or you could leave it in a chest and take along a lesser but more rugged weapon. I don't want to permanently steal a player's hard earned gear, but I do want to give players an incentive to actually use some of the mountains of loot they pick up. That rusty engraved dagger you just found may not be better than your heavy butcher's knife but you might want to save your good weapon for the boss who's guarding the stairs to the next level.

I'd like to get rid of resting to regain HP once and for all, but most people expect it as part of a classic RPG. Whether it can be removed will depend on how the combat model turns out. I'd like to reject the traditional simplified HP model of health in favor of a wound and critical hit based model. Players will suffer wounds which may lead to critical injury, reducing the player's vital statistics either temporarily or semi-permanently.

Here's one final look at the in game map:

 I'm going to have to add more room types as some of them are becoming a little repetitive.

The map is made up of multiple triangular tiles, they have two overlaying textures, one being the rooms and the other being a old paper type texture. The map will be drawn automatically as you progress and uncover new areas. Areas not yet visited will not be shown. You'll be able to add tags and comments to the map as you go through the game and look at other levels while navigating the one you're on.

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 …