As written in Topic: Stone and uranium ore seems to be interchanged.
It was written in Release-Log, that starting resources are nearby and for uranium you have to take a look. But this behavior is reversed. Uranium comes in mid huge deposits near starting area. For stone on the other hand, you have to go sometimes more than a mile and than getting only deposits in size of about 150k.
I've try that with more than 20 maps, plus preview.
[0.16.7] Ore generation: stone and uranium interchanged
Re: [0.16.7] Ore generation: stone and uranium interchanged
Can not reproduce, I generated 20 maps, 19 had stone in the starting area 0 had uranium in it.
Re: [0.16.7] Ore generation: stone and uranium interchanged
You're right. Stone will ever spawn at starting Location (some k of it).
But look at attached screenshot - I startet creative-mode nad the first map I createt is this map.
On entire revealed map, ther are only 44k of Stone (at starting Location) and an overall of 3.4M of uranium. (You see one deposit of 1M uranium on the middle bottom, and one deposit of 2.2M on the right side. In top part of map, which is not on screenshot, you could see two more deposits of uranium with 70k and 238k.)
But no mor stone at all.
But look at attached screenshot - I startet creative-mode nad the first map I createt is this map.
On entire revealed map, ther are only 44k of Stone (at starting Location) and an overall of 3.4M of uranium. (You see one deposit of 1M uranium on the middle bottom, and one deposit of 2.2M on the right side. In top part of map, which is not on screenshot, you could see two more deposits of uranium with 70k and 238k.)
But no mor stone at all.
Screenshot
mapexchangekey
Re: [0.16.7] Ore generation: stone and uranium interchanged
Player here seems to have the same problem.
Re: [0.16.7] Ore generation: stone and uranium interchanged
You seemed to have missed what I assume is about 2.5M stone in the south east in your screenshot, considering that stone is not needed for consumable material this does not sound bad at all. Even if there was none, the way it is created, a single map is completely anecdotal.TheRaph wrote:You're right. Stone will ever spawn at starting Location (some k of it).
But look at attached screenshot - I startet creative-mode nad the first map I createt is this map.
On entire revealed map, ther are only 44k of Stone (at starting Location) and an overall of 3.4M of uranium. (You see one deposit of 1M uranium on the middle bottom, and one deposit of 2.2M on the right side. In top part of map, which is not on screenshot, you could see two more deposits of uranium with 70k and 238k.)
But no mor stone at all.
To wrap this up, stone and uranium have not been mixed up, what you describe is a balancing issue which are handled here: viewforum.php?f=16. NaB.
Re: [0.16.7] Ore generation: stone and uranium interchanged
Stone is need for purple science as well as various bits of infrastructure (rails, walls, furnaces, landfill). If you are doing 1k science per minute, then science eats 2.49 blue belts of stone (5952 stone per minute), even with max productivity modules everywhere.considering that stone is not needed for consumable material
Re: [0.16.7] Ore generation: stone and uranium interchanged
- Maybe I've missed something. I'll check that, next time I sitting at home on PC. But I also if it's true, that's quite more uranium than stone in Map.Loewchen wrote: You seemed to have missed what I assume is about 2.5M stone in the south east in your screenshot, considering that stone is not needed for consumable material this does not sound bad at all. Even if there was none, the way it is created, a single map is completely anecdotal.
- As Zavian wrote, stone is a consumable material since it is used for infrastructure (that's my problem ... not enough stone for concrete and walls) and purple sience.
- How much Screenshots of different maps will you need to not declare it as anecdotal? 20? 50? Or more?
I'll place this in "balancing" as you mentioned ... as I've enough screenshots (just sitting in train to go home). But as this behaviour was different in 0.15 I think it is bug.