This release is mostly cosmetic: I added a new level, UI and models. The full list of fixed issues can be found here.
The new level is an industrial complex, built using props from the Phishers’ Gauntlet project that I abandoned. I’ve also added some third-party assets:
The title scene also has some limited scenery, with other player characters crouching behind cover.
Mostly, I got rid of the smiley faces that showed the player status. My original plan there was to have images similar to Jagged Alliance 2 that become increasingly bloodied as they take damage, but I found this to be dead weight.
I also replaced the fonts. Instead of Arial, I’m using this archaic typewriter font. I’ve also used Ampad Brush in the title scene to make the buttons resemble graffiti on the walls.
Screenshots of the level
It’s still a bit empty, even after adding props, but I’m starting to get tired of this project. For something that was originally meant to be a proof of concept, it’s gone further than I expected. I’ll probably leave it for a month and come back to it, but I’m a bit stuck on what to add next.
Finally, Fiptubat has reached version 0.4! The full list of fixed issues is here, but here’s the main ones.
The big change was adding humanoid enemies that take cover. Finding cover was adapted from a very useful post on the Unity forums, which uses the following flow:
- Sample random (or not-so-random) positions around the unit’s current position
- For each sample position, find the nearest edge in the NavMesh.
- Obtain the normal field of the resulting NavMeshHit
- Remove any results that don’t point sufficiently away from the target direction
- Choose the closest.
It broadly works. Once they get to a cover position, they will repeatedly fire at their chosen target if they can see it, or reposition on their next turn.
- Turrets will pick the most exposed enemy they can find, rather than the closest. There is one slight caveat: this is based on the number of Raycasts that hit the target, which may result in things like this.
- Suppression mechanics: dump enough ammo into the area around a target, and they lose their remaining action points. On their next turn, they’ll have half their total.
- Turrets no longer have 2-D aim. This took me the better part of a day to fix, and was the last issue added.
- Enemy units will try to relay the position of enemies to their comrades when spotting them.
- Sidestepping is no longer a free action. It now works by shifting the player units a guaranteed distance forwards/backwards/sideways, with a cost of 4 action points per unit moved.
- Toned down the sirens. Turrets still use this when spotting an enemy, but they have other noises. The humanoid enemies use a recording of Radio na Gaeltachta under heavy static.
- The player unit’s current path is now visible as a solid red line. I would like to make it dotted and translucent behind objects, but that’s another issue.
The next release will probably involve character models and a larger level to play in.
I finally have a gameplay video for Fiptubat – warts and all. It shows the player units picking their spots and moving to them, basic combat, and swapping turns with a hostile faction.
The video shows one really annoying bug that I haven’t got to the bottom of yet. Player units sometimes start jerking around when standing still, and I’ve tried quite a few things without any success. I had originally planned to fix this before filming, but decided that it didn’t break the core gameplay enough to hold back everything.
About a year ago, I screwed up the boot loader on my computer, which put a crimp in my development work. While trying to fix that, I spent a lot of time watching Christoper Odd’s XCOM 2 playthroughs, and it eventually lead to a new game project. I’ve been working on this since May.
The idea I had was to try doing a turn-based tactics game (such as XCOM, Jagged Alliance or Silent Storm) from a first-person perspective, i.e. from the perspective of the units themselves. This has lead to a few interesting design implications around player units in particular:
- Should player units be allowed to look around without costing action points?
- How should aiming work? Should it be freeform like in a first-person shooter, or should the player choose from a list of existing targets?
- Should player units be allowed to move at all without costing action points (e.g. stepping in/out of cover)?
It’s currently a WebGL prototype, available here. There’s no screenshots yet, but the general turn-based mechanism, combat and objectives are functional.