EDDI parses compartments in the order provided by FDev (which is not necessarily in order of power consumption like you see in your right hand screen).
{SetState('eddi_context_body_system', system.name)}
{SetState('eddi_context_body_name', event.name)}{SetState('eddi_context_star_system', system.name)}
{SetState('eddi_context_star_star', event.name)}Yes, it's possible. In fact, that's typically what is already happening on a scan in-game. The 'BodyDetails()' function in both the 'Star report' and 'Body report' scripts pulls data from a server and by setting variables like you see in the 'Body scanned' and 'Star scanned' scripts, you can control which data gets pulled (as long as the data is present on the server, the in-game scan is not even necessary - you can even pull data on places you've never visited before).
It turns out that one of the journal changes deals directly with this. No promises / guarantees, but by the time we finish incorporating all of the changes this may be included.
FDev doesn't publish anything that we can reference when you target or select a body, so we can't set a variable based on that.
{if len(ship.model) > 0:
{set installed to 0}
{set enabled to 0}
{set bays to 0}
{for compartment in ship.compartments:
{if compartment.module.name = "Planetary Vehicle Hangar":
{set installed to 1}
{if compartment.module.enabled:
{set enabled to 1}
}
{if compartment.module.class > 0:
{set bays to compartment.module.class / 2}
}
}
}
{SetState("srv_installed", installed)}
{SetState("srv_enabled", enabled)}
{SetState("srv_bays", bays)}
} {_ SRV Check _}
{F("SRV check")}
{Pause(2000)}
{if state.srv_installed && state.srv_enabled:
SRV Ready {Occasionally(2, "for deployment.")}.
|elif state.srv_installed:
If you are planning an excursion, please enable the Planetary Vehicle Hangar.
|else:
No planetary vehicle hangar has been installed.
}