Ah, there
was something else to discuss. How is the determination of immune/vulnerable made? In short, like this
like this.
On the vertical axis is the number of ticks it takes for the roids the attacker capped to repay the losses they suffered. On the horizontal axis is the ratio of attacker losses to defender losses: higher means the attacker lost more value relative to the defender. The attacker is assumed to have Corp and 30 FCs.
The assumption I made is that you'll be more willing to risk a landing if the defender suffers (much) more than you. If your calc shows that you lose 100k value but the defender loses 300k, you might attack for 48 ticks roid repay time, whereas if you lose 100k and the defender loses nothing, you might only want to attack a target that'll give you 16 ticks of repay time. The defender is assumed to have a non-Demo, non-Tot government (Tot and Demo help defense by improving salvage).
In addition, if the attacker's losses are very low, less than 1k value, they'll land for any roidcap. If the roidcap is 0, a very low income increase of 10 value per tick is assumed (so only gigantic defender losses will entice an attacker to land for 0 roids). Neither of these exceptions is visible in the graph, because it only shows relative losses.
I'll also hijack this post to host a changelog. Here:
Changelog
v1.2.1 (2018-10-18):
- Support race headers, empty lines, and make race column optional in ship stats
v1.2.0 (2018-03-02):
- Support ETA when parsing ship stats (the values are otherwise unused)
- Support resource stealing
- Support EMP ships both as 'EMP' and 'Emp' when parsing ship stats
- Allow use of + and / in fleet names in the fleet composition file
- Support multi-pod fleet compositions in the analysis: the ships in the same class as each pod used as separate attack fleets
v1.1.0 (2016-12-02):
- Include vulnerability score at verbosity level Warning and below
v1.0.3 (2016-10-10):
- Support files with CRLF line endings
v1.0.2 (2016-10-09):
- Support stats with T1, T1+T2 and T1+T2+T3
v1.0.1 (2016-10-09):
- Initial release
v1.0.0 (YYYY-MM-DD):
- Never released