Thanks!
That is not something I initially thought was worth spading; I had the thought that the types of encounters were specific to a planet but they were randomly selected. I noticed that quest encounters were one type per planet, spants and murderbots had specific mixes of types, and that animals, plants, and aliens had one type - and always had the same image.
(I believe taltimir spaded and found that hostile aliens dropped specific trophies based on which of 6 images appeared. I should validate that - and incorporate it.)
Initially, I just had "rocks" - but when I decided that not all planets had all rocks - and one of the types was skippable - I added support for that and revisited every planet I'd been to prior to that fix.
So, lets see. I have fiveccharacters who generate a random planet name each day and explore.
Here is one result:
Let's try that planet with a different character:
Regarding "deriving from planet name" - that was a main goal of this program's data collection.
There are seven letter in a planet name, so 26 ^ 7 = 8,031,810,176 different planets. That is about 33 bits of data.
Apparently, some data are shared - hostile alien image number and trophy item type.
The presence of hostile animals is there somewhere.
There are 20 different small hostile animal images (sganimala1.gif - sganimala20.gif)
There are 10 different large hostile animal images (sganimalb1.gif - sganimala10.gif)
There are 3 different exotic hostile animal images (sganimalc1.gif - sganimala3.gif)
In any case, it looks like encounter types are encoded in planet name - but distribution varies. Perhaps is is seeded by player, class, turn count, whatever. Or perhaps it is randomized, some how.
One could write a program to scrape the enounter summary from session logs and look into that, if one wanted to try spading it.
But the raw data is not in the distributed data files.
I should make a new data dump; I probably have a couple thousand new planets to publish.
That is not something I initially thought was worth spading; I had the thought that the types of encounters were specific to a planet but they were randomly selected. I noticed that quest encounters were one type per planet, spants and murderbots had specific mixes of types, and that animals, plants, and aliens had one type - and always had the same image.
(I believe taltimir spaded and found that hostile aliens dropped specific trophies based on which of 6 images appeared. I should validate that - and incorporate it.)
Initially, I just had "rocks" - but when I decided that not all planets had all rocks - and one of the types was skippable - I added support for that and revisited every planet I'd been to prior to that fix.
So, lets see. I have fiveccharacters who generate a random planet name each day and explore.
Here is one result:
Code:
> Today's encounters on the planet at coordinates BCROQNB (Delta Draper XI)
> Cool Space Rocks: 2
> Paradise Under a Strange Sun: 1
> Space Cave: 6
> Spant drone: 5
> Wide Open Spaces: 3
> small hostile animal: 3Let's try that planet with a different character:
Code:
> VeracitySpacegate visit coordinates BCROQNB
...
> Today's encounters on the planet at coordinates BCROQNB (Delta Draper XI)
> Cool Space Rocks: 2
> Paradise Under a Strange Sun: 1
> Space Cave: 5
> Spant drone: 4
> Wide Open Spaces: 4
> small hostile animal: 4Regarding "deriving from planet name" - that was a main goal of this program's data collection.
There are seven letter in a planet name, so 26 ^ 7 = 8,031,810,176 different planets. That is about 33 bits of data.
Apparently, some data are shared - hostile alien image number and trophy item type.
The presence of hostile animals is there somewhere.
There are 20 different small hostile animal images (sganimala1.gif - sganimala20.gif)
There are 10 different large hostile animal images (sganimalb1.gif - sganimala10.gif)
There are 3 different exotic hostile animal images (sganimalc1.gif - sganimala3.gif)
In any case, it looks like encounter types are encoded in planet name - but distribution varies. Perhaps is is seeded by player, class, turn count, whatever. Or perhaps it is randomized, some how.
One could write a program to scrape the enounter summary from session logs and look into that, if one wanted to try spading it.
But the raw data is not in the distributed data files.
I should make a new data dump; I probably have a couple thousand new planets to publish.