[1.6.1](b38e) Android Defense Armies are Listed Under Armies on Outliner

[nwb]

Pretty much just the title. I noticed regular defense armies don't show up on the outliner but Android defense armies do.

 

[Lys]

There are android defense armies?
I believe robotic (and thus also android) armies do not have the distinction between defense and assault armies. As such you can use them for attacks, which is why they will be displayed in the outliner.

 

[nwb]

You're probably right. I should've posted a screenshot as well, here it is.

 

[Wyrm]

I can second this. Just went here to post a report myself. They can also be embarked on transports, so they behave exactly as assault-armies. Probably a missing flag somewhere in the text-files

 

[Secataur]

"android_defense_army" misses "defensive = yes" in the text file. Very likely related.

 

[Wyrm]

Good chances this will be fixed in the next patch then, as long as the devs have seen this report. It's a 5-second fix

 

[Yograin]

Indeed very annoying.

 

[Cassilda]

I'm reporting this bug too. And as android armies aren't treated as defense one, they can be built over the max garrison limit for planet.

 

[FlyingPhoenix]

Would also like to report this bug.

 

[Kliwarrior]

In "00_armies.txt" , "android_defense_army" lacks the "defensive=yes" flag that every other "defense" armies have.

Spoiler: android_defense_army

android_defense_army = {
    robotic = yes
    damage = 1.70
    health = 2.17
    time = 80
    maintenance = 0.45
    icon_frame = 4
    has_species = no
 
    cost = {
        minerals = 75
        energy = 10
    }
 
    prerequisites = { "tech_synthetic_workers" }
}

Spoiler: robotic_defense_army (see the defensive tag)

robotic_defense_army = {
    robotic = yes
    defensive = yes
    damage = 0.96
    health = 1.70
    time = 60
    maintenance = 0.23
    icon_frame = 4
    has_species = no
 
    cost = {
        minerals = 50
        energy = 8
    }
 
    prerequisites = { "tech_droid_workers" }
}

 

[Gruntsatwork]

Hi everyone, thanks for the reports, we are aware of the issue and it has been fixed on our internal build.

 

[Moso]

Hi everyone, thanks for the reports, we are aware of the issue and it has been fixed on our internal build.

Kudos Gruntsatwork! It's really encouraging seeing the QA team responding to the bug reports