I started writing this back in January, but back then other events overtook it, and it languished unpublished until now, when I thought it might be a useful insight to some who question my sanity for embarking on this venture...
So at this stage it's very apparent that Warcradle's iteration of v3 of Firestorm is quite a departure from SGs v2 - not in itself a bad thing, but also not quite what many in the community were expecting. To me, the changes made are not necessarily detrimental, but they just make the game feel different - like playing Dropfleet or Full Thrust - games that existed during FSA's existence too, and have some nice mechanics. The thing is, I have Dropfleet, though I've never played a game in earnest, mainly because I had Firestorm and it scratched the itch...and Dropfleet felt different.
So I come to the main point of this blog - FSA (Future Space Apocalypse). I started work on this even before SG went bust, as a continuation of the work that the FFG and myself had done for SGs FSA v3 before Neil took a different route with its development. The development worked on elements that the community had fed back that needed tweaking - not all of these were universal (for example, movement, which was seen as more of an issue in the US than Europe). So broadly speaking the big areas are;
- Game speed
- Movement (making it faster and less "fiddly" with the old template)
- SRS & PD "wall"
- Link fire calculation
- Boarding
- Cyberwarfare
- Small faction rebalancing (Aquans & Sorylians were variously called out as stronger and weaker factions)
Then some smaller elements were;
- "zombie" ship syndrome
- Number of tokens
- Iterative dice rolls (part of game speed above)
- Some fleet building & battle log hurdles (making some ships more or less appealing due to their place in the fleet building or number of BL points they yielded on destruction)
- MAR "bloat"
Some of these things are relatively easy to fix, some require a more fundamental change, and the underlying aim was not to change core mechanics so the game didn't change overall - widely being seen as being pretty good and one of the most balanced of systems out there.
As an example of game speed, the FFG discussed shields, as this is one example of an iterative dice roll (one player rolls, then the other, before the outcome can be determined) - and talk was had of making shields a sort of static boost or reduction. The problem with that is that it removes player agency and alters the "feel" of the game -especially for shield-heavy factions, so it was dismissed as a concept. However, using different dice mechanics can retain the agency but still speed up the game - hence Shields moving to "basic" or "black" dice, where successes are on a 4,5 & 6 and don't explode.
At this point I'm sure Terran players are having a heart attack as this obviously reduces the average hit reduction from 0.8 to 0.5, and of course this switch requires adjustment of the shield numbers on ships, but this also has several beneficial consequences - it "caps" the top end, making shields feel more believable in the game (we've all had experiences of an SH1 frigate resisting a huge attack by a string of lucky sixes), but it also makes Shields more reliable - especially at the lower end. So an SH1 ship with exploding dice has a 50% chance of the ship blocking absolutely nothing, whereas a SH2 basic dice shield ship only has a 25% chance of the same null result. This change then also allows you to play with dice mechanics - shield modulators can "bump" the dice up to "blue" or "heavy" dice, making the shields more effective very easily.
So although many people think that tweaking Firestorm is a quick job requiring nothing much more than changing movement, there are many things which are very interconnected. It just so happens that I started looking at this way back in v1 of the game with the custom ship creator, and trying to adapt that to a more balanced thing, and then adapt it for v2. Turns out that's not easy - how do you truly evaluate the effectiveness of a weapon in FSA - a game which is all about positioning and timing in many ways - when so many things affect it...the ships movement, other ships movements, DR, CR, what type of ship is firing, what sort of weapon, what range, what MARs exist on both ships....it's a huge and extremely complex network, and so I started creating what I ended up calling the "Battle Log calculator", which looked at all these elements for every ship in the game. I almost finished it as my time at Spartan ended, and then it lay fallow for many years until now, when I've resurrected it to help me finish Fanstorm.
This project uses probability curves based on al the mechanics of the game, and plots these out per ship, in all squadron sizes, in all damaged and undamaged states, together with modifiers for movement, MARs, Scenario effectiveness across the course of a game etc. It's been a HUGE labour of love (and horrible grind at times!) to create, but I wanted to have something that wasn't just based on "gut feel", but based on facts and data and that could be adjusted to represent changes to ships through design. This also means it can be used to create new ships...otherwise known as a custom ship generator...and give them appropriate costs and BL points.
There are two main elements to this - threat potential and threat resistance. Let's look at this in a bit more detail;
1) Threat Potential
Simple put, this is how threatening a ship - or group of ships - is to other ships in the game. The obvious point to start here is with AD vs DR & CR - that's an easy thing to analyse, and for any AD value you can see the probability curve of how likely it is to breach the DR and CR of a given target. Of course, range has an impact, since AD vary by RB, so now you have four values for each ship. Now, because AD degrade with hull damage, you really need to see the degradation through a ship's damage state, creating its HP value x 4 values....and if its a capital ship then the probability changes if its firing at a non-capital ship, and for a squadron you really need to look at each number of ships in a squadrn at each damage value.....
You can see how this set of probabilities quickly escalates when just considering a single squadron in Firestorm. Then you have types of weapon and firing arcs, and time in the game. For example, an Aft-firing weapon is of absolutely no use in most games for at least two or three turns, whereas a Kinetic FF weapon RB3 & 4 weapon is great in the opening couple of moves, but the likelihood of getting a shot at those ranges later in the game is vanishingly small. A high AD RB1 primary weapon is not of much use to a slow capital ship, especially in the early stages of the game, but to a high-speed, manoeuvrable corvette, that same weapon has much greater utility.
So how do you deal with this huge complexity? Simply put, you model it all out. The numbers seem unmanageable (and they are if you're trying to do it manually), but to a computer this is much easier - it's just data. Putting the data in takes a long time, but when its there the manipulation is relatively easy. So yes, I went through every scenario and looked at each weapon type in each arc, and what it could threaten in each turn through the game. Now it's impossible to look at every iteration (well, not impossible, you could write a program to do it I'm sure, but I'm not that good a programmer), but you can look at areas and probabilities. Ships have set starting points and bounded movement parameters, and the game area is likewise fixed.
So if you know where and when a weapon can threaten an enemy, and what threat that weapon then represents to an enemy, that's a set parameter that can be given for every weapon stat in the game. As they're all contained by the same parameters, they're directly comparable - they're relative measures. As we now have a value for each of these, you can sum them up and create an overall value for any given ship with any combination of weapons. The details are expansive and numerous, but the concept and end result is simple.
2) Threat Resistance
Once we have a measure of the threat potential of ships in the game, Threat resistance is pretty much the inverse of that - how well can a ship resist the potential threats in the FSA universe? Again, this is a combination of DR, CR, range, defences, MARs etc and the threats posed against all of that at each stage in the game. For example, a DR6, CR10 PD 5 SH2 ship 46" away from an enemy fleet can only be threated by Kinetic weapons and torpedoes, most of which have very little chance of penetrating its defences. A DR3 CR5 SH1 PD1 frigate in a small squadron of two at the same range has exactly the same threats, but they are more likely to be able to breach those defences. If the weapons fired at them also have a MAR like Torpedo Spook, then they are much more vulnerable. Later in the game, the more ponderous battleship might be less able to avoid RB2 shots from enemies, PD flagging from damage making it more vulnerable to torpedoes and boarding, whereas the frigates can manoeuvre out of reach of Fore Fixed weapons, and group up to ensure that their PD remains relatively high and thus making them an unattractive target for torpedoes.
Once again, not ALL circumstances can be modelled, but as long as representative ones are built into the modelling, the relative measures apply. From the work I did on the v2 analysis, the results bore out many of my feelings and suspicions about ships based on play experience and community feedback.
Of course, I did all this with SGs v2 of the game, and it wasn't quite finished when I let go of the whole thing a couple of years ago...or rather, it was, put it wasn't where I wanted it to be - I could see areas for improvement. Now that I've altered some elements of the rules, I need to redo all of that, which is why Points and Battle Log values will be the last things that get changed/fixed in all of this.
