You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hard coded 9f I believe is the problem. Since everything is percentage based, taller worlds are penalized in this calculation. This constant should be scaled to either sea level or world height.
The text was updated successfully, but these errors were encountered:
I've been doing a little more digging, and I suspect the sea level is being set after the deposit generators are initialized. This would explain even better the behavior I'm seeing especially with obsidian. The deposit variants are loaded in the AssetsFinalize stage of the GenDeposits ModSystem, but the world height is set in the StartServerSide of the GenTerra ModSystem.
GenTerra's execute order is later, but it's unclear to me if mod initialization is "interleaved". As in, is AssetsFinalize called for all mods before any mods StartServerApi is called?
I'm not sure if it's safe to delay initializing deposit variants or move the world height setting to an earlier phase.
I noticed this while seed hunting for worlds with large amounts of obsidian rocks. The higher the world height, the less likely top layer obsidian would produce surface stones. This can be seen at https://github.com/anegostudios/vssurvivalmod/blob/81e52e9a61eabd6aa2131fb255f072feaf9901f1/Systems/WorldGen/Standard/ChunkGen/5.GenDeposits/Generators/DiscGenerator.cs#L359.
The hard coded 9f I believe is the problem. Since everything is percentage based, taller worlds are penalized in this calculation. This constant should be scaled to either sea level or world height.
The text was updated successfully, but these errors were encountered: