Skip to main content

Barbarians!

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.

Comments

Popular posts from this blog

Automating Level imports from Blender to Godot

  Recently I've been making some levels in Blender an importing them into Godot. There are only about 7 or 8 shaders for each level, not counting dynamic objects which will be added later. But to improve rendering performance, it can be a good idea to split the meshes up into sections. At that point you might be faced with a list like this: Or it might be even more chaotic, if you didn't use simple names for the objects in your level. So it can take a long time to sort out all the meshes, make them unique and add textures and so on. Blender imports with simple Blender textures, or with placeholder materials. This is sometimes OK, but if your Godot shaders are very different to those used by Blender, it means applying new materials to every mesh object in the level when you import the scene. I found that during the design process, I was importing and readying a level several times before I was happy with the final layout. So at first I was wasting a lot of time. In Blender, I us

Upstairs / Downstairs.

I've decided to make my prefabs multilevel. Later this should allow me to add pit traps and other great stuff. It also makes it easier to line up stairs so that you can exit them on the same co-ordinates where you entered them. The prefab editor is pretty much finished, it just needs some code for loading up prefabs from a saved dictionary, so that they can be checked or edited. The entries will need to be forwards compatible, so I'll be loading each tile and then translating the indexes to a new array, that way if I add extra indexes or extra info (like traps or puzzles) I'll be able to update existing prefabs to work with the new standard. Click for a video.

Advice needed on tilesets...

I need some advice on which is the best way to handle building the dungeon. Right now I'm using prefabs for my dungeon, they have a north south east and west section for each "room": The basic tileset. This has several advantages, and also several disadvantages. Firstly I can have curved rooms, I can have tunnels and other interesting shapes. The tilesets can look quite nice with a little work. On the other hand I can't easily get the navigation data before building the map and once the map has been built I can't make changes to the layout, like having active pit traps or believable secret doors. Although the rooms are interesting, they are quite repetitive, and it takes a lot of effort to make even a few different variations. Also rooms are constrained to one size. A newer version of the tileset with a lot of variant parts for making more interesting rooms. To create a tile set is a real headache too. Planning how to lay out the UVs, trying to cra