Looking at the yaml files for world generation at doing some experimentation, it looks like some of the POI generation coding was done either with incorrect assumptions on how it actually works in game, or the game actually has a bug with how it works.
Attached are the two examples of what I am talking about.
In FrozenSlush the POI "heatsinks_a" has "poi/frozen/heatsink_a" and "poi/frozen/heatsink_b" listed under it. It appears that the intention either is to have both of them spawn, or a random one of these POIs to spawn. However, the game will always pick poi/frozen/heatsink_a to spawn regardless. If you switch the order, it will always spawn poi/frozen/heatsink_b instead of poi/frozen/heatsink_a. It never spawns both.
The same goes for "ruins_a" and it's two points of interests. "poi/frozen/lab_splitroom" never appears because "poi/frozen/lab_basement" is listed first and will always appear.
It is most obvious in JungleGassy though where you have "geysers_b" and it always spawns "expansion1::poi/jungle/geyser_hydrogen" since it is first, and never the "poi/jungle/geyser_chlorine" which shows up second. Swapping the order will swap which one shows up in the asteroid, but neither order causes both to show up, nor does it become random.
I can't tell you the proper way to correct this issue. I am just here to point out the issue. Obviously there was some intention for things to work differently than how they are, but I can't possibly know the actual intention.
Inspect the files.
A developer has marked this issue as fixed. This means that the issue has been addressed in the current development build and will likely be in the next update.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now