And it seems to be more basic than a propagation error:
Requested 20x detector
Web page predicts the expected 0.88
Offer contains 0.99
Now, I'm really not going to quibble over 1 scrap but your arithmetic is wrong somewhere, which is sloppy programming, and that is just *bad*.
Conversion/Rounding error? Did you precompute the total in refined, hand off to a backpack picking function, convert back to scrap count, and round up?
MvM part trading - webpage metal count / offer metal count mismatch
in Archive
Posted
Current prices charging 0.4 scrap ref per reinforced part.
Buying in 5x = 2 scrap (0.22) [technically 0.20 if using decimal arithmetic, but I'll forgive the limited representation].
Requested 10x detector (0.44), 5x pump (0.22), 5x stabiliser (0.22)
Web page predicts the expected 0.88
Offer contains 0.99 (quite literally; 2 rec + 3 scrap).
And it seems to be more basic than a propagation error:
Requested 20x detector
Web page predicts the expected 0.88
Offer contains 0.99
Now, I'm really not going to quibble over 1 scrap but your arithmetic is wrong somewhere, which is sloppy programming, and that is just *bad*.
Conversion/Rounding error? Did you precompute the total in refined, hand off to a backpack picking function, convert back to scrap count, and round up?