StarFallArmada

too early... need our dev.exe , convert.exe, xsiconvert.exe, forgetools with particle forge included, etc...

Using Kdiff3 , will be able to use the software perfectly once we have the convert.exe only:

- all .mesh are different but by 4 bytes more... maybe a version number... cannot be sure since we have not the convert.exe

- majority of texture are identical

- all map files are different... for example, the Agamemnon's Bounty.galaxy...  green is change, only version number... blue is added... the triggerCount is maybe what will be used for make scenario... seem some gravity wells data are not anymore entity related but map related... will allow to have two identical planet with different gravity wells size... for the new entitycount/asteroidcount, i have no idea :

TXT
versionNumber 4
isBrowsable TRUE
browsePictureName "ScenarioPicture-AgamemnonsBounty"
browseName "IDS_CUSTOMGALAXY_NAME_AGAMEMNONSBOUNTY"
browseDescription "IDS_CUSTOMGALAXY_DESCRIPTION_AGAMEMNONSBOUNTY"
isFirstCapitalShipIsFlagship TRUE
randomizeStartingPositions TRUE
planetArtifactDensity 0.150000
planetBonusDensity 0.400000
normalStartHomePlanetUpgradeLevel:Population 3
normalStartHomePlanetUpgradeLevel:CivilianModules 1
normalStartHomePlanetUpgradeLevel:TacticalModules 0
normalStartHomePlanetUpgradeLevel:Home 1
normalStartHomePlanetUpgradeLevel:ArtifactLevel 10
normalStartHomePlanetUpgradeLevel:Infrastructure 2
quickStartHomePlanetUpgradeLevel:Population 4
quickStartHomePlanetUpgradeLevel:CivilianModules 1
quickStartHomePlanetUpgradeLevel:TacticalModules 0
quickStartHomePlanetUpgradeLevel:Home 1
quickStartHomePlanetUpgradeLevel:ArtifactLevel 10
quickStartHomePlanetUpgradeLevel:Infrastructure 2
recommendedGameTypeCount 1
recommendedGameType "Solo"
metersPerGalaxyUnit 25000.000000
pixelsPerGalaxyUnit 5.753997
useRandomGenerator FALSE
galaxyWidth 1920.000000
galaxyHeight 1126.000000
nextStarNameUniqueId 3
nextPlanetNameUniqueId 27
triggerCount 0
starCount 3
star
 designName "Star0"
 inGameName "IDS_STARNAME_230"
 type "RandomNonGreenStar"
 pos [ 568 , 116 ]
 radius 25.000000
 moveAreaRadius 60000.000000
 hyperspaceExitRadius 50000.000000
 planetCount 5
 planet
  designName "Planet11"
  inGameName ""
  type "AsteroidBelt"
  pos [ 562 , 102 ]
  moveAreaRadius 40000.000000
  hyperspaceExitRadius 30000.000000
  owner ""
  isHomePlanet FALSE
  normalStartUpgradeLevelForPopulation 0
  normalStartUpgradeLevelForCivilianModules 0
  normalStartUpgradeLevelForTacticalModules 0
  normalStartUpgradeLevelForArtifacts 0
  normalStartUpgradeLevelForInfrastructure 0
  quickStartUpgradeLevelForPopulation 0
  quickStartUpgradeLevelForCivilianModules 0
  quickStartUpgradeLevelForTacticalModules 0
  quickStartUpgradeLevelForArtifacts 0
  quickStartUpgradeLevelForInfrastructure 0
  planetItems
   templateName ""
   subTemplates 0
   groups 0
  spawnProbability 1.000000
  useDefaultTemplate TRUE
  entityCount 0
  asteroidCount 0

I really hope using the moveAreaRadius and hyperspaceExitRadius in the maps are optional. Otherwise, it will pretty much kill some planet mods, such as NU.

If the planets are of a standard radius, I would be glad to make a script that could go in and fix all the planet radius values. And they must leave in the values in the normal entity files otherwise the random maps wouldn't know what to do.