MattG's Observatory plugins
- Thread starter MattG
- Start date
FWIW, most of the time BI should handle this. I've set the cut-off date to 1st March 2018 - anything before that won't be processed but anything since should get recorded in case the system is revisited. Off hand, I don't remember the exact reason for that date - but suspect extra detail was added in journal that I rely on. It might be possible to record star data from before then but there would still be a hole from before journals existed. I'm also hoping to add support for spansh at some point to help pre-determine biologicals too, but that may be a little while yet.
Codex Companion no longer seems to be marking bios as being seen. I presume that this is because of the latest updates to BioInsights that new deals with this directly.
Yep, between .Net update and U14, I've just not had time to get to CC yet. Soon
That's fine. I can wait. I'm trying to achieve a 100% bio collection. That will take me ages!!Yep, between .Net update and U14, I've just not had time to get to CC yet. Soon
The new version of BI lets you know if there are any new codex bio on the planet, but I must admit having them all listed in the codex with requirements was handy for hunting them down, the in game codex is a real pain to use for that!
Hi @MattG,
There is a non-atmo species named Prasinum Sinuous Tubers that BioInsights is totally silent about. Neither scanning the planet nor scanning the species itself triggers any activity in the plugin.
Can you please take a look at this?
There is a non-atmo species named Prasinum Sinuous Tubers that BioInsights is totally silent about. Neither scanning the planet nor scanning the species itself triggers any activity in the plugin.
Code:
{ "timestamp":"2023-01-04T09:32:01Z", "event":"FSSBodySignals", "BodyName":"xxx", "BodyID":3, "SystemAddress":xxx, "Signals":[ { "Type":"$SAA_SignalType_Biological;", "Type_Localised":"Biological", "Count":1 }, { "Type":"$SAA_SignalType_Geological;", "Type_Localised":"Geological", "Count":3 } ] }
Code:
{ "timestamp":"2023-01-04T09:50:01Z", "event":"ScanOrganic", "ScanType":"Log", "Genus":"$Codex_Ent_Tube_Name;", "Genus_Localised":"Roseum Sinuous Tubers", "Species":"$Codex_Ent_TubeABCD_01_Name;", "Species_Localised":"Prasinum Sinuous Tubers", "SystemAddress":xxx, "Body":3 }
Code:
{ "timestamp":"2023-01-04T09:58:16Z", "event":"ScanOrganic", "ScanType":"Analyse", "Genus":"$Codex_Ent_Tube_Name;", "Genus_Localised":"Roseum Sinuous Tubers", "Species":"$Codex_Ent_TubeABCD_01_Name;", "Species_Localised":"Prasinum Sinuous Tubers", "SystemAddress":xx, "Body":3 }Can you please take a look at this?
Last edited:
That's an old horizons bio, BI doesn't do those at all.
Oh. Good to know. Thanks!
Would it be a big deal to add them, though? Bio is bio, after all.
Would it be a big deal to add them, though? Bio is bio, after all.
Oh. Good to know. Thanks!
Would it be a big deal to add them, though? Bio is bio, after all.
True, but it is Matt's baby, I would like to see something that tracks geo as well so I could get my codex updated with those, may have to write my own.
He did say on the front page;
Give me the exact spawning requirements for each bio. Even then it's not as trivial as you might think - Horizon bios can spawn multiple variants on same body for example.Oh. Good to know. Thanks!
Would it be a big deal to add them, though? Bio is bio, after all.
What would geo tracking do, exactly? Spec it out and maybe it can be done. I don't think geo prediction is possible though.
Yeah, basically the only idea I have that I would like to have it let me know when a geo on the planet isn't in my codex because checking the in game codex is a pain, but I am thinking you can't do that without mapping first right? The FSS on the body only gives pretty basic info for geo, sometimes only stuff like "water magma" but not if it's geysers, fumaroles and etc, you need to map to find that? I mean I am also thinking, do we even know if there is maybe more than one class of geo feature of said type, maybe a planet can have both water and methane fumaroles in the right conditions for instance but it only tells you fumaroles.
It's a desire only at the moment and not really thought through, I don't know enough about the date returned from FSS on geo to make a good guess of what it could do.
I'm pretty sure what you say here is right. Prediction is difficult.
It's not to do with Matt's plugins, but I had intended to learn how to do custom criteria for Observatory and get it to alert me when there is a bio signal on a non-atmosphere body. Be it shards, anemone or whatever, they're usually worth a look. I'll get around to it one day.
::Criteria=HorizonsBio::
if scan.Landable and not scan.AtmosphereComposition then
if biosignals > 0 then
return true, 'Biological Anomaly', biosignals .. ' biosignals detected on non-atmospheric body'
end
end
::End::
Here you go: check the spreadsheet linked in this thread, and the "Surface Bio - Horizons" part there.
That said, to everyone: it's not as easy as you might think. The multiple variants (actually implemented as different species instead) per body is less of a problem, there's a more practical one: a good handful of Horizons flora don't cover entire regions, but only appear in relatively small spheres. Bark mounds only appear within 100 ly of a nebula center, brain trees only appear around a handful of specific nebulae (the ones with remote Guardian ruins). These one are at least established and their centers are well-known, but there is also the problem of sinuous tubers: there are spheres of those in the galaxy which's centers AFAIK haven't been determined yet.
So, without checking for locations, the predictions would be swamped by false positives. For reference, take a look at this map.
In other words, beyond the functionality needed for the Odyssey flora, the program would need to check for: star types present in the system, body types present in the system, system's distance to certain other systems. Doable? Sure. Worth the effort for flora that pays poor credits, and can easily be predicted by a human? Well...
One of the bigger issues I have is the temperature requirements for different atmospheres. I strongly believe Ody temp ranges are based on black body temperature, but there’s enough examples to cross reference atmosphere to range. That data for older bios is harder to come by.
I’ll ponder it more though. Much of the recent refactoring was with an eye on support for older bios. As usual, I expect the biggest problem is finding the time!
Oh Fab! Thank you. That was very kind.
@MattG, @marx, thanks for explanations. It's indeed much more difficult task than I thought. I think the criteria suggested by @CMDR Sheehy will work good enough.
Last edited:
I had a derp last time, because even if implemented that way, there shouldn't be too many false positives: after all, the plugin would alert when bio signals are found on a body, and if there are none, then it wouldn't say "there should be sinuous tubers here". Plus instead of unknown centers, sector names could be used to filter too: it wouldn't be 100% accurate, but still reasonably so, and could be implemented without knowing the area center systems.