• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

Denniss

CORE developer
38 Badges
Jun 15, 2005
3.371
43
www.matrixgames.com
  • Mount & Blade: Warband
  • Victoria: Revolutions
  • Semper Fi
  • Sword of the Stars II
  • Victoria 2
  • Victoria 2: A House Divided
  • Victoria 2: Heart of Darkness
  • 500k Club
  • Europa Universalis IV: Pre-order
  • Rise of Prussia
  • Europa Universalis IV: Res Publica
  • Europa Universalis IV: Common Sense
  • Achtung Panzer
  • Surviving Mars
  • Age of Wonders III
  • Surviving Mars: Digital Deluxe Edition
  • Shadowrun Returns
  • Surviving Mars: First Colony Edition
  • Surviving Mars: First Colony Edition
  • Deus Vult
  • Cities in Motion
  • Crusader Kings II
  • Crusader Kings II: Legacy of Rome
  • Crusader Kings II: The Old Gods
  • Crusader Kings II: The Republic
  • Crusader Kings II: Sunset Invasion
  • Crusader Kings II: Sword of Islam
  • Commander: Conquest of the Americas
  • Darkest Hour
  • Arsenal of Democracy
  • East India Company Collection
  • Europa Universalis IV
  • Europa Universalis IV: Art of War
  • Europa Universalis IV: Wealth of Nations
  • For the Motherland
  • Hearts of Iron III
  • Hearts of Iron III: Their Finest Hour
  • Majesty 2
108b4: savegame issues

1) In a current savegame I saw an odd duplication in the attachment preferences section, a duplicate entry for b_u10
Code:
attachment_preferences = { infantry = { extra1 = { (snip) b_u1 = 0 b_u2 = 0 b_u3 = 0 b_u4 = 0 b_u5 = 0 b_u6 = 0 b_u7 = 0 b_u8 = 0   b_u9 = 0
 b_u10 = 0 b_u11 = 0 b_u12 = 0 b_u13 = 0 b_u14 = 0 b_u15 = 0 b_u16 = 0 b_u17 = 0 b_u18 = 0 b_u19 = 0 b_u10 = 0 } (snip)
The last entry is obviously intended for b_u20.
In other sections of the savegame (AI build preferences, build cost/time, supply stock, models etc) the second b_u10 is always stored separately and also not affected by changes made to b_u10.

If time permits please modify the way attachment prefs are stored inside the savegame, I suggest to store only brigade parameters for matching types (land div prefs should only list none and brigades set up as land_unit_type, etc). Saving it in a human-readable format would be even better.

2) The IC allocation to the infrastructure/province repair slider is still not stored inside a savegame.

3) May be just a cosmetic issue: land units loaded onto transport ships have their leader and division data not stored in the usual human-readable format but in a single line.
Code:
		landunit = { 
			id = { type = 4712 id = 513260 } 
			name = "XIV Corps" 
			location = 0 
			home = 22 
			mission = { type = none target = 2410 missionscope = 0 percentage = 0.0200 night = no day = yes } 
			date = { year = 1940 month = may day = 1 hour = 0 } 
			development = no 
			morale = 0.5000 
			leader = { id = { type = 6 id = 1211 } name = "Mansergh" picture = "gfx\interface\pics\L1211.bmp" category = general rank = 2 rank_year = 1940 rank_year = 1943 rank_year = 1990 rank_year = 1990 max_skill = 7 startyear = 1940 endyear = 1960 skill = 3 experience = 40.0000 trait = logistics_wizard trait = offensive_doctrine changed = yes } 
			division = { id = { type = 4712 id = 512845 } name = "15th 'Scottish' Division" model = 0 brigade_model = 0 type = motorized extra = engineer strength = 100.0000 organisation = 54.0000 morale = 70.0000 experience = 0.0000 defaultorganisation = 50.0000 redep_unit_name = "" supplies = 4.0719 oil = 24.5000 max_supply_stock = 20.1600 max_oil_stock = 24.5000 maxspeed = 12.0000 supplyconsumption = 1.3200 fuelconsumption = 3.5000 defensiveness = 20.0000 toughness = 20.0000 softness = 87.0000 suppression = 2.0000 airdefence = 4.0000 softattack = 12.0000 hardattack = 2.0000 transportweight = 30.0000 airattack = 3.0000 speed_cap_art = 10.0000 speed_cap_eng = 10.0000 speed_cap_aa = 10.0000 speed_cap_at = 10.0000 artillery_bombardment = 0.0000 } 
			dig_in = 0.0000 
			attack = { year = 0 month = january day = 0 hour = 0 } 
			target = 1862 
			staging_province = 1798 
			}
4) Some units in production have a strange way to store their attached brigades
Code:
	division_development = { 
		id = { type = 4712 id = 461785 } 
		name = "HMS Cleopatra" 
		progress = 2.0000 
		location = 19 
		cost = 3.0000 
		date = { 
			year = 1941 
			month = june 
			day = 3 
			hour = 0 
			} 
		manpower = 1.3000 
		close_when_finished = yes 
		waitingforclosure = no 
		total_progress = 0.8867 
		size = 4 
		done = 1 
		days = 160 
		days_for_first = 126 
		gearing_bonus = 0.2392 
		type = light_cruiser 
		extra = naval_anti_air_s 
		extra = naval_anti_air_s 
		extra1 = naval_radar_s 
		extra2 = none 
		extra3 = none 
		extra4 = none 
		model = 3 
		brigade_model = 2 
		brigade_model1 = 0 
		brigade_model2 = -1 
		brigade_model3 = -1 
		brigade_model4 = -1 
		}
Note the two duplicate "extra" entries with only one matching "brigade_model" and the second brigade attachment as extra1/brigade_model1 instead of extra2/brigade_model2. At least an investigation should be made why there's a duplicate "extra" storage. I assume the -1 for higher brigae models is working as intended for disabled/nothing attached. This applies to all unit type, land/air/naval.

BTW a setting in the game options to disable recording of battle history/recorded leader events would be nice. It blows up the savegame just for some flavour.
 
Last edited:
Upvote 0