dfriedman

its not just my last game that I saw this in. its been every game since I installed the Intrigue upgrade.

just did. said there were 5 files that failed to verify and were reacquired. i'll start up the game again and see what's what.

they wont read the support forum? ok I will [quote who="Island Dog" reply="5" id="3635283"] If you still have a problem please start a support ticket and include a save game if possible. https://esupport.stardock.com/index.php?/Tickets/Submit [/quote]

just started a new game with exact same settings as before and changed only the minor races frequency from abundant to common, and already met 2 minor races within 5 turns. I don believe theres a bug when setting the minors to abundant

its still pre-planetary invasion and I've met about 3/4 of the major races and explored about half the galaxy. no minors to be seen anywhere. im playing a huge galaxy with 8 major races, abundant minors, lots of stars, lots of planets. its puzzling. i'll start a new game with the minor setting one less than abundant and see if that makes any difference. [quote who="androshalforc" reply="2" id="3635276"] I'm

1.7 release, just started a few games ago, I know I have chosen 'abundant' minor races when setting up the galaxy, but no minor races are ever found in the galaxy.

found it. it's in: C:\Program Files (x86)\Steam\steamapps\common\Galactic Civilizations III\data\Game\GalCiv3GlobalDefs.xml

ive search for this file and its not found. where are you seeing this xml file?[quote who="Horemvore" reply="4" id="3632441"] They order upto 2 upgrade modules per starbase. Its defined in GC3GlobalDefines.xml, set it to 0 and you will basicly have the "effect" you want. 2 2</MaxNumber

just want an option to turn it off. the way it is now, its a worse form of micromanaging to turn off each starbase's option than it is to micromanage each starbase's manual update

when manually sending constructors to starbases, they enter orbit and no notification is given that a starbase is ready to be upgraded

can you add a setting to default this option to NO?!? its annoying as hell to have it set automatically on when building a new starbase

if a resource is already being mined by an outpost and you create a new outpost in range of the same resource, the mining constructors are enabled. im fairly sure in v1.6 they were listed but greyed out, meaning you already had an outpost in range of the resource that was already mining it.