Skip to main content

Spotted!

After some testing, I decided to rework the radio contact rules described in the previous post. I've been playing a lot of RPG and Strategy games lately and one thing I don't really enjoy is the micromanaging aspect of buffing and de-buffing.

Rather than force the player to make hard decisions on where to allocate their buffs, it just ends up with them having to devote too many resources to support. You end up having at least one team member out of four doing nothing but support.
It also wastes a lot of time clicking and selecting and so on.

So, I want support actions to offer a significant bonus when active, but most should be passive. They should have specific utility too, not a general buff which you simply apply to your best unit. If your tanks are getting swarmed with infantry, then rapid fire will help you clear them out. If there's an enemy who is well dug in behind cover, you can use steady aim or mark target to get a bead on them.

In the end I just made special actions and ability to receive buffs reliant on having a radio. While the support role requires the command radio. Infantry can't carry a radio (yet) but they don't need to as none of their special abilities are reliant on it.

I'm also working on air support.

It's nice to be able to abstract this element. Not having to have actual planes flying around the map makes coding it a whole lot easier. Later I may add some graphics to represent it, such as a shadow cast on the ground, or an inset box with a picture of the type of plane doing the action.

Three types are currently planned; Spotter Planes, Fighter Planes and Air Strike.
In both cases they start their first turn inactive. The icon is placed on the map, but nothing happens.

On its way.
On the very next turn, the effect becomes active. Either dropping some bombs or revealing some of the map.

Circling and looking for targets.
At this time, the enemy (or the player) has a chance to use anti-aircraft weapons (or Fighter Planes) to try and cancel the effect before it is active. The chance will depend on a number of factors, such as the weapon being used, distance from target and so on.
About to head home.
The big advantage of air support is they can be targeted on tiles which are covered by fog of war. You can use them to scout out objectives or soften up the enemy before an attack. The disadvantage is that they can be nullified by opposition air support or anti air defenses.

This is quite a significant development, as none of my previous versions of Vinland got as far as adding air support rules. I hope I can train the AI to use them effectively, along with anti-aircraft weapons.

Labels:

Comments

Post a Comment

Popular posts from this blog

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.
6 comments
Read more

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
3 comments
Read more

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
7 comments
Read more