Page 1 of 1

1.7.0.13 - explorer behaviour

Posted: Sun Jan 22, 2012 12:02 am
by Kayoz
This is an old bug which has never been addressed -

Explorers will sometimes fail to explore ruins when exploring a planet, despite it being an automated task (eg: explore all, report all).

Aside from the obvious fix of the explorer not leaving the planet till any present ruins are explored - it shouldn't be too hard to kludge in behaviour to have explorers, when having finished their tasks, seek out the nearest unexplored world (ie: unknown resources) OR the nearest unexplored ruins.

As it stands, you have to manually target ruins which have been missed by explorers, or those revealed by map trades/theft. That's a silly amount of micromanagement.

RE: explorer behaviour

Posted: Sun Jan 22, 2012 9:13 pm
by elliotg
Hi Kayoz

Do you have a savegame showing this problem? This issue was specifically addressed in an earlier Legends patch, so this was fixed as far as I knew.

Thanks
Elliot

RE: explorer behaviour

Posted: Sun Apr 08, 2012 7:33 am
by Kayoz
ORIGINAL: elliotg

Hi Kayoz

Do you have a savegame showing this problem? This issue was specifically addressed in an earlier Legends patch, so this was fixed as far as I knew.

Thanks
Elliot

Issue still occurring in 1.7.0.13 -

Savegame file: RuinsUnexplored-20120407.dwg

Example:
Sector: J1
System: Tynna Minor
Planet: Plozeysi

Explanation:
Explorers on auto seem to have passed over this area. Planet resources were identified, but ruin not explored.
I did not get any system maps or such from pirates or AI empires.

Related issue:
Purchasing/stealing system maps does not expose the ruin characteristics. For example, if the ruins have been explored already by an empire that the maps were traded for - shouldn't the ruins be exposed? If not, then shouldn't explorers target the now known ruins for exploration? Explorers in this (purchase/steal) case (from what I have seen, not demonstrated in this file) ignore those systems.