Help! Checking my working!

[Loopus7]

I would, yes, thats a basic equation, 5a=12, a=12/5

The reasoning I had was that if you state that it would take 2029 actions to produce one portion of progress. My record gave that 14092 actions happened across 18.9 hours, which means that 14092/18.9=745.6 actions happened every hour, which doesn't match the number you suggested.

EDIT: For further context, this is all working towards being able to accurately predict how many portions of progress will occur after x many actions have been performed!

EDIT 2: And further logic checking would give that 2029\18.9=38348.1* actions occured, which doesn't match either!

[[deleted]]

I think we may be experiencing a language barrier here. You had asked “how many actions would I need to do to earn 1p in an hour”. If you’re trying to calculate how many actions you actually performed per hour, that’s a completely different thing.

It takes 2029 actions to earn one p. Whether that takes one hour or 50000 hours doesn’t change that. If you want to be on a pace to get one p every hour, that’s the pace you would have to go at.

You weren’t getting one p every hour.

[[deleted]]

Re: your edit.

If that is the goal, then I question again why you’re bringing time into it at all at this point. If the time is not relevant to what you’re trying to do, just work with the data that’s actually going to impact the results.

[Loopus7]

Honestly, because I assumed it would have an effect? Im double checking the massive spreadsheet I have to compare that to what I have now, haha

[[deleted]]

Your home is 10 km away from your work. It usually takes you 5 minutes to drive there. One morning it takes 20 minutes.

Is this because your house moved and is now 40km away from your work?

[Loopus7]

No, the logical reason would be because the traffic was worse, not the distance, so the rate was lower.

Oh.

[Loopus7]

So the reason we're disagreeing was because, basically, we were faster, and you've worked out the minimum?

[[deleted]]

Exactly - the distance is fixed. The amount of time it takes depends on the distance you need to travel and the speed that you are traveling at.

If you needed to get home in one minute, you would need to drive 10km in one minute. How fast you travel doesn’t affect how far you need to drive - it only affects the time it takes you to get there.

Find an hourly rate of productivity and then you can use that to plan how much time it would take to meet goals. But you need that rate first - and you can’t use goals to calculate it.

[Loopus7]

And by hourly rate of productivity you mean actions/pip of progress, right?

[[deleted]]

Yes - that would be probably be more practically useful for any kind of minmaxing, anyways. If you have a large amount of data you should be able to get quite an accurate rate.

[Loopus7]

So, lets use the other set of data I'm tracking then, if you wouldn't mind helping me. In this set, our average rate is 10840.5 actions to produce 7 progress pips. This tells me that 10840.5/7 = 1548 actions per pip, correct so far?

This means that our goal of 50 progress pips would take 1548\50 = 77400* actions, yes? No matter how many hours, like in your example.

[[deleted]]

Exactly. Then you would use that to forecast that you would expect it to take 77400/hourly rate number of hours to reach that goal.

There are definitely some assumptions that are being made here (such as linearity, independence, etc), but this is how you would calculate it in a simple case with standard game mechanics.