The possibility of terraforming is not properly recognized (Candidate for terraforming).

[nepomuk16321]

Bodies marked as “terraformable” in the journal are recognized as “not terraformable.”

I tested this with the variables {body.terraformstate} and {body.terraformState.invariantName}.
Tested with my character and with an EDDI copy in English.

{ "timestamp":"2025-09-15T21:00:18Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Col 285 Sector EX-A c14-20 3", "BodyID":4, "Parents":[ {"Star":0} ], "StarSystem":"Col 285 Sector EX-A c14-20", "SystemAddress":5581477778178, "DistanceFromArrivalLS":426.787437, "TidalLock":false, "TerraformState":"Terraformable", "PlanetClass":"High metal content body", ...}
{ "timestamp":"2025-09-20T20:18:06Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"b2 Carinae B 6", "BodyID":26, "Parents":[ {"Star":2}, {"Null":0} ], "StarSystem":"b2 Carinae", "SystemAddress":2003358976363, "DistanceFromArrivalLS":36941.001225, "TidalLock":false, "TerraformState":"Terraformable", "PlanetClass":"High metal content body",
{ "timestamp":"2025-09-22T21:51:25Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Macalites D 6", "BodyID":18, "Parents":[ {"Star":6}, {"Null":0} ], "StarSystem":"Macalites", "SystemAddress":4855217260907, "DistanceFromArrivalLS":68500.290334, "TidalLock":false, "TerraformState":"Terraformable", "PlanetClass":"Water world", ... }
{ "timestamp":"2025-09-25T22:45:41Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Zelano BC 3", "BodyID":13, "Parents":[ {"Null":2}, {"Null":0} ], "StarSystem":"Zelano", "SystemAddress":8330256782042, "DistanceFromArrivalLS":3329.518740, "TidalLock":true, "TerraformState":"Terraformable", "PlanetClass":"High metal content body"

Configuration

• EDDI Version: v4.1.6
• Localization German
  • EDDI's language: German also testet with English
  • Voice: Harpo Nuance Petra 22 kHz - German

[Tkael]

"Not Terraformable" would be the normal default value if something went wrong or didn't get updated somewhere.

1. Did you confirm that body was reporting information about the correct body (e.g. using the body name or ID)?
2. Did you try using the BodyDetails() function at all or did you just rely on the body property directly?
3. Did you test to see if any other information from body was missing / not as expected? The body type, distance from the start, etc?

[nepomuk16321]

Hello T'kael, since the last CG, I have been working quite intensively on the values of the bodies. I have created an Excel spreadsheet with exploration data. I can give it to you if you like. However, it is in German. I would have to adapt it.
There are four values for terraforming: “Terraformed” – terraforming complete, “Terraforming” – currently being terraformed, ‘Terraformable’ – expresses the possibility of terraforming (candidate for terraforming), and “Not terraformable” – which applies to most bodies and is the standard. For bodies that I scanned and for which the journal says “Terraformable,” EDDI always output “Not terraformable,” see journal entries. For these bodies, the other properties were available, such as the “Earth mass” value.

to 1. Yes ! I look at the log and compare the output (speechresponder.out) with the values.
to. 2. Okay, I won't do that. I'll call the SystemDetails() function and query the bodies using a loop. I'll use the names and types of the bodies for identification.
to 3. Yes !

I didn't notice any problems with the other terraforming options. Different planet types also had different terraforming options. Everything worked fine. Only this one option, “Terraformable,” was never displayed, even though it is listed in the journal for this body.

Addendum: For comparison purposes, I also use the EDEB tool from CMDR Panostrede.
https://www.panostrede.de/EDEB/

Queried the body “Zelano BC 3” with BodyDetails(). Same result = “Not terraformable,” even though the journal says ‘Terraformable’ (without “Not”).

{system.systemname},
{for body in SystemDetails(system.systemname).bodies:
    {if body.planettype = "Wasserwelt" :
        {body.shortname},
        {body.planettype},
        {body.terraformstate},
        Masse {body.earthmass},
        Wert EDDI {body.estimatedvalue},
    }
}

{_ Planet mit hochwertigen Metallen / HMCB }
{_ Erdähnliche Welt / ELW }
{_ Metallreicher Körper / MW }
{_ Wasserwelt - WW }
{_ Ammoniakwelt - AW }

[Eahlstan]

I'm no expert on EDDI, but in their code there's a comment that says:

Obsolete("Please use TerraformState instead")

So maybe your problem is that you're using terraformstate instead of TerraformState?

terraformstate has 0 things that use it in their code, TerraformState is used all over the place:

[nepomuk16321]

{body.terraformState.invariantName} - Is the non-localized content of the variable.
{body.terraformstate} - is localized. If there is a problem with the translation, I have also tested the non-localized version of the variable. Unfortunately, with the same result.

[Tkael]

I think I've got this one squared away. Essentially, the value we were expecting to see from Spansh was our invariant value "Candidate for terraforming" and the value we actually received was "Terraformable". Because it wasn't a match it fell back to the default value of "Not terraformable". I've written a quick equivalency so either one should be an acceptable input moving forwards.