AI War Beta 6.017-6.018 "Defending The AI's Front Lawn" Released!

[Radiant Phoenix]

Is the Exo Firepower and ship count broken?

At least a Black Widow Golem + Armor Golem = 1 massive, 0 FP ship?

things that occur to me:

• I don't know how Special Forces works, but it might be that
• They might not be the flagships (!!!)
• I thought they might have already made it to your planets, but further inspection suggests otherwise.

[keith.lamothe]

Is the Exo Firepower and ship count broken?

Hasn't changed recently.

At least a Black Widow Golem + Armor Golem = 1 massive, 0 FP ship?

It may actually be the spirecraft that's counting as the massive ship, dunno.

you're missing a *10 somewhere.  (7^2)/2 = 24.5, not 245.

This is why I should not be trusted with math.  I meant *5 instead of /2, in this case.


On the nemesis timing rule change I just amended it to "Offensive Nemesis champions now do not start unless the player has completed a nebula (win or loss) or the game clock has reached 3 hours. "

[contingencyplan]

Is the Exo Firepower and ship count broken?

Hasn't changed recently.

At least a Black Widow Golem + Armor Golem = 1 massive, 0 FP ship?

It may actually be the spirecraft that's counting as the massive ship, dunno.

So 2 Golems don't count as massive ships, or add anything to the FP? 

On the nemesis timing rule change I just amended it to "Offensive Nemesis champions now do not start unless the player has completed a nebula (win or loss) or the game clock has reached 3 hours. "

Schweet.

[keith.lamothe]

So 2 Golems don't count as massive ships, or add anything to the FP? 

Displayed FP is actually the internal FP divided by some large number, so I don't know much about it.  And less about the massive ship count thing

[Diazo]

I think that message is actually misleading.

As I understand it, if it says there are "3 massive ships" on the way to your planets, that means their are 3 groups incoming, each with their own group leader and escorts.

Then in brackets the firepower is only the firepower of the group leads and ignores the escorts.

So if for some reason you had a Spirecraft group lead with a couple golem escorts, that would be the message I'd expect to see.

D.

[Histidine]

All potential exo leaders (or components, for that matter) should have a nonzero FP though.

[Toranth]

All potential exo leaders (or components, for that matter) should have a nonzero FP though.

Spirecraft Implosion Artillery are a massive ship with a FP of 0.

As I understand it, if it says there are "3 massive ships" on the way to your planets, that means their are 3 groups incoming, each with their own group leader and escorts.

I don't think that's right.  I don't know if you've ever triggered the Defensive Exowave, but it is one group with lots of 'massive ships'.  The message when it's on the map is usually "Lotsa massive ships heading to your planets (truckloads-o-FP)".  I'm pretty sure each Spirecraft, Golem, H/K, Avenger, or Mothership should count.

[TechSY730]

All potential exo leaders (or components, for that matter) should have a nonzero FP though.

Spirecraft Implosion Artillery are a massive ship with a FP of 0.

It's more like a FP with such a tiny amount of base firepower that is basically rounded to 0. (Which is odd, because in the map display, firepower is rounded up instead of down). Of course, the implosion artillery never actually does its base firepower but uses that percentage calculation. This unfortunately makes reasoning about its "average" combat deadliness complicated.

I think maybe the spirecraft shield bearers may show up as rounded down to 0.

[Toranth]

Running 6.018, there's a minor problem with the "Avoid Pathing Through This Planet" control.  I think it has to do with Team Control of ships.
When I select any non-main player Champion, the routing ignores the Avoid flag.  This is expected, since I hadn't set that flag in those GUIs.  It's not an issue, though, since including main player stuff in a group selection causes the flag to be correctly applied.

However, when I select a group including Champion 3 (that'd be the 4th player in the list), any pathing route will ignore the Avoid flag, no matter what else is in the group.  The highlighted path on the Galaxy Map looks like it will apply the flag, but after clicking, the red highlighted line shows the true path (through the Avoid-flagged system).
In reverse, if Champion 3 has the avoid flag on a system and no other player does, Champion 3's flag overrides everyone else if included in a group.

In my testing, it's only Champion 3 that causes this.


I've attached a game where this can be easily demonstrated.  In the Harkalenan system are all my Champions.  The adjacent system Neijuash has a BHG and is marked as Avoid by the main player. 
Try routing the Champions in various combinations from Harkalenan to the Yehatin system (marked as P7, slightly to the southeast).

[Cyborg]

Update: 6.018 hotfix to fix a bug preventing sending champions into unexplored nebulae.

lol, I hit this...

[keith.lamothe]

New one