How to use it

What this is

When a run ends, the result screen shows stats, inheritance and a placing all at once. That screen goes away, and after another run it is hard to recall how the last one went. This app is the place you open in that moment and fill in within half a minute.

Once a few runs pile up, something changes. You can see how far speed climbed last month, or which inheritance shape came with better results. The app does not judge for you. It builds the material you compare.

The calculator is the other half. Once a target exists, whether the turns left reach it is plain arithmetic.

Using the log

The date is filled in with today. The name field is free text. There is no list to pick from, so write whatever you usually call her. Several runs under one name are fine, and so are nicknames.

The five stat fields take the numbers on the result screen as they are. Inheritance has three slots, each with a name and a grade. Grades run from one to three, and an empty grade counts as none.

The result field takes a grade or a placing, whichever you want. A one-line note about this run pays off later when you compare.

Saving adds the run to the list, which you can order by date, by total or by name.

House rules of this app

Runs go into this browser's storage only. There is no account and no route to a server. So clearing browser data clears them, and another device will not see them.

To move them, press export. You get a file holding every run, and importing it elsewhere merges rather than overwrites; where two runs share an identity, the imported one wins. If some lines cannot be read, the screen tells you exactly how many were skipped.

One browser holds up to 300 runs. Past that, the oldest dates drop off.

Empty fields count as zero, and so do negative or non-numeric entries. Session counts round up, because you cannot run half a session.

There is no undo. Delete asks once and then deletes.

The three calculations

First, sessions needed for a target. Give the current stat, the target, the gain per session and the turns left, and you get the count and whether those turns reach it. A cap, if you set one, holds the target down to it.

Second, splitting the turns left. Weights decide the ratio. A stat already reaching its target takes no more, and turns freed that way go back to the ones still short. If there is genuinely nowhere left to spend them, the leftover is shown rather than hidden.

Third, the inheritance total. Name the slots, pick grades, and set what each grade is worth. There are no defaults, because we are not going to claim we know the game's numbers.

All three are arithmetic on what you entered. No in-game probability or bonus goes into them.

Getting more out of the log

Gain per session differs from run to run, so put in what you actually saw this time. With no feel for it, the gap between two or three saved runs is a reasonable place to start.

Weights are read as a ratio, not a size. Three and one split the same way as thirty and ten.

Even a one-line note beats a column of totals later on. What you changed to get a different result never shows up in the numbers.

Where people get stuck

If every result reads zero, the gain-per-session field is usually empty. With nothing to divide by, the count stays at zero.

An all-zero split table means no weights were entered. We will not spread them evenly on your behalf, so the screen says so instead.

An inheritance total of zero means the points per grade are still blank. This app ships no default table.

Runs missing on another device is normal. Move them with the export file.