Originally posted by ijg
Training question #2:
How exactly are the decimals carried over?
Premise: It appears decimal values - whether displayed (multi) or not (normal train) in the expected training value are rounded when applied to your training bar. Is this correct and is it working as intended?
1) In multi train - where decimals are shown - the training bars seem to go up by the rounded up value displayed, e.g. if it's 16.7% the bar goes up 17% and even if it's 16.3%, the bar tends to go up 17% too. It will go up 17% each train, so after 3 trains, you get 51%, not 50% (16.7% * 3) as best I can tell. So is it correct that the decimal is not stored in the training bar?
2) In daily training, there seems to be a similar decimal expected value, though it's not shown. Is this correct? This becomes apparent at high skill values, so when a skill is at 80, the light expected value will be 1% and normal may be 3% whereas at 90, the light value is still 1% but normal may be 2%.
When you train, your bar goes up by those displayed 1%, 2%, or 3% each time, again suggesting no stored decimal. However, I am guessing when you get 3% normal, 1% light it's because the expected values are say 2.8% and 1.4% whereas at 2% norm, 1% light, it's because the expecteds are 1.8% and 0.9%. Again, is this roughly correct?
Bottom line: The reason I am asking all this is there are funny situations when you're trying to fill out a bar (say speed is at 82 and 94% full) and light takes 6 trains at 1% vs only 2 norm trains at 3%. However, if I wait til 88 to fill the bar, it now takes 3 norm trains at 2%, but I can still do 6 light trains at 1%, so there is a bit of an arbitrage to knowing where norm is of value and where light is of value. Is that disparity WAI? I would have thought there would always be a linear relationship preserved there, but if decimal values aren't stored, then inefficiencies get created.
Note: It isn't just apparent at high values. I've noticed at lower values sometimes as well, usually around the caps.
Originally posted by Bort
Decimals are rounded/chopped off when inserted into the database, as we just store the total gains as integers. No, there's no plans to change that.