[HELP] Scripting Anomalies into Custom Systems

[Adrik Thorsen]

- How can I add anomaly events to specific planetary bodies? I originally assumed that something like this would work when tagged on an asteroid in my system:

            init_effect = {
                add_anomaly = {
                event = "precursor.2005"
                days = -1
            }
        }

This does not work, and broke my entire system when I tried adding it to one of the asteroids in my home system. Any advice on getting this working?

 

[LamilLerran]

You add anomalies by adding an appropriate anomaly category, not by directly adding an anomaly event. So in this case, your code block would look like

    init_effect = {
        add_anomaly = cybrex_habitable_category
    }

where I determined that cybrex_habitable_category was the appropriate anomaly category for this anomaly event by searching the 00_anomalies... files in the anomalies folder for precursor.2005.

Note that anomaly categories may be associated with more than one anomaly, in which case you will not necessarily get the specific anomaly event you are looking for. In this case, for example, there appear to be five possible anomalies for cybrex_habitable_category, and which one you get depends in part on whether the cybrex_intro country flag is set and in part on luck.

 

[Adrik Thorsen]

So the following:

   planet = {
        count = { min = 2 max = 5 }
        orbit_distance = 20
        change_orbit = @base_moon_distance
   
        moon = {
            count = { min = 3 max = 9 }
            orbit_distance = 5

            init_effect = {
            add_anomaly = cybrex_uninhabitable_category
            }
        }
    }

Would add that anomaly to at least 1 of the 3-9 moons in question? Or to ALL of them?

 

[Kordishal]

all of them.

You will need to create one special moon and spawn the rest in at random.

 

[Adrik Thorsen]

Also, that doesn't precisely work. Breaks the entire system. Played with it a bit and concluded that the proper syntax should be:

init_effect = {
add_anomaly = {
 category = "cybrex_habitable_category"
   }
}

Except that that removes the custom moon from my system, although it doesn't break anything else. Is this a weight issue? Should I use a line such as

init_effect = {
add_anomaly = {
 category = "cybrex_habitable_category"
 weight = 500
   }
}

perhaps?

 

[Adrik Thorsen]

planet = {
count = { min = 2 max = 5 }
orbit_distance = 20
change_orbit = @base_moon_distance

moon = {
   name = ""
   count = 1
   orbit_distance = 3

   init_effect = {
        anomaly = {
        event = precursor.2000
        category = "cybrex_asteroid_category"
   
        weight = 500
   
        potential = {
            always = yes
                }
            }
        }
    }
moon = {
count = { min = 3 max = 9 }
orbit_distance = 5

init_effect = {
add_anomaly = cybrex_uninhabitable_category
   }
 }
}

Should work for spawning both a random number of moons and the anomalous one?

 

[Adrik Thorsen]

Actually adding the anomaly to an asteroid in my home system removed all the planets which spawn after that asteroid. Is there a system flag I'm missing for precursor anomalies?

 

[Kordishal]

Does the error log say anything?

Each system gets a precursor flag from the precursor file. You can see which precursor will spawn in what system with "-debug" turned on. So there might be a conflict.