Beyond DefaultGameCore.ini - Analyzing the Game Scripts

[Amphibious]

I'm interested in xcomgamedata.ini specifically this section:

 

[XComStrategyGame.XGFundingCouncil]

 

Most stuff is straighforward however I'm wondering about these entries:

SMALL_DEMAND_AMOUNT=8
BIG_DEMAND_AMOUNT=16
HUGE_DEMAND_AMOUNT=24
PROFIT_MARGIN=1.25f
FCM_MONEY_SCALAR=2.25f
FCM_INTEL_CHANCE=0

BASE_REQUEST_COOLDOWN_DAYS=40
FC_REQUEST_EXTENDED_COOLDOWN_DAYS=10

Any thoughts?

 

p.s. Sorry for necroing but thread name was appropriate.

Edited July 20, 2014 by Amphibious

[Amineri]

Those are variables that control how the vanilla Fundring Requests work, for the most part.

[Amphibious]

That's obvious. it determines request and council mission rewards. But I'm more interested in specific how does each value work and what it means.

 

Let me share what tested out so far and am 100% sure it means. Blanks are unknown or not tested out properly.

 

[XComStrategyGame.XGFundingCouncil]

• FCREQUEST_DAYS=20; number of days you hve to fulfill council member request
• DELUGE_GAP_HOURS=168; nmbr of hours after base defense when deluge mission starts
• MIN_MONEY_REWARD=100 ; these values govern min and max council mission sum, just can't figure ot how exactly, are they percentages or what?
• MAX_MONEY_REWARD=225
• MAX_MONEY_REWARD_HARD=150
• MAX_MONEY_REWARD_CLASSIC=125
• MIN_MONEY_REWARD_EASY=100
• FIRST_MONTH_MULTIPLIER=0.5f
• SECOND_MONTH_MULTIPLIER=0.75f
• SMALL_DEMAND_AMOUNT=8
• BIG_DEMAND_AMOUNT=16
• HUGE_DEMAND_AMOUNT=24
• PROFIT_MARGIN=1.25f
• FCM_MONEY_SCALAR=2.25f; governs council mission reward sum somehow?
• FCM_INTEL_CHANCE=0

• BASE_REQUEST_COOLDOWN_DAYS=40
• FC_REQUEST_EXTENDED_COOLDOWN_DAYS=10

• MISSION_FAIL_LOW_PANIC=1
• MISSION_FAIL_HIGH_PANIC=2
• MISSION_REWARD_LOW_DAYS=21
• MISSION_REWARD_LOW_MULT=0.5f
• MISSION_REWARD_MED_DAYS=41
• MISSION_REWARD_MED_MULT=0.75f
• MISSION_REWARD_SOLDIER_LOW_LEVEL=3
• MISSION_REWARD_SOLDIER_MED_LEVEL=4
• MISSION_REWARD_SOLDIER_HIGH_LEVEL=5

• SLINGSHOT_LOWFRIENDS_START_DAY=51; day on which sigshot 1st mission start
• SLINGSHOT_CNFNDLIGHT_DAYS=25; second singshot mission delay after first one
• SLINGSHOT_GANGPLANK_DAYS=2, 3r slingshot mission delay after 2nd one

• REQUEST_WINDOW1_MIN_DAY=5; days when first/second request/mission can occur
• REQUEST_WINDOW1_MAX_DAY=15; as above
• REQUEST_WINDOW2_MIN_DAY=17; as above
• REQUEST_WINDOW2_MAX_DAY=27;s above
• REQUEST_MISSION_CHANCE=50; chance for event to be request or mission, 0 means 100% chance for request and 100 means 100% chance for mission