Total raw calculations seem to be rounded down to one decimal place. In my situation, this means I get a lot of recipes that show things like "copper ore 0.0" which is really "copper ore 0.05", and "copper ore 0.7, tin ore 0.2" which is really "copper ore 0.75, tin ore 0.25". The rounding is to the decimal place, not significant figure, so results like "128.0" are also possible.
Could this be controlled - either per recipe or as a global setting? I realise this is not an earth-shattering issue but it can be a bit misleading.
[Request] Total raw precision control
-
Deadlock989
- Smart Inserter
- Posts: 2529
- Joined: Fri Nov 06, 2015 7:41 pm
Re: [Request] Total raw precision control
Really? I thought the design was to limit all numbers to 4 characters.
It would be nice to allow 0.05, since that is still 4 characters.
-
Deadlock989
- Smart Inserter
- Posts: 2529
- Joined: Fri Nov 06, 2015 7:41 pm
Re: [Request] Total raw precision control
Well, I've definitely seen things like 66.0 (which may have been 66.09, and the only reason you know that is because it isn't shown as 66), so I guess your evaluation of whether my statement was accurate or not hinges on your subjective construal of what I meant by "like".DaveMcW wrote: Tue Apr 16, 2019 1:24 pmReally? I thought the design was to limit all numbers to 4 characters.
It would be nice to allow 0.05, since that is still 4 characters.
I've never heard of a 4 character limit. I do know that suffixes like k and M start appearing above their respective limits, and they also seem to be rounded to one decimal place or possibly 2 significant figures (e.g. 1573.34 petroleum gas is represented as 1.5k) but that's not quite the same thing.
As a side note, this kind of thing also results in full storage tanks being shown as containing 24k fluid when their limit is actually 25k. Presumably the amount inside is actually 24,999 or something and this is being represented as 24k.