Closed AlexKnauth closed 3 weeks ago
One crazy hacky idea I have, is to repeatedly call skip_split
until it's on the last split, then call set_variable_int
to set the column value for the last split, then undo_split
and set_variable_int
for the 2nd-to-last split, undo_split
and set_variable_int
for the 3rd-to-last split, and so on.
It appears that this "crazy hack idea" does not work at all. When the undo_split
happens it also erases the Future split entry, rather than leave it there.
In terms of settings, instead of having a
Timing method
field that allows one of:Load-removed time
Hits / dream falls
Hits / damage
Change it to an extra
Hit counter
field that allows one of:None
Hits / dream falls
Hits / damage
Provide a layout that displays the hits via a variable, alongside load-removed time.
Variables to display could include:
hits
cumulative hits so far in the current runpb hits
the minimum number of total hits in previous finished runsdelta hits
difference between current runhits
and "best-pace" hitssegment hits
hits in this segment of the current runThe settings map would need to keep track of "best-pace" hits for each split. The
pb hits
variable can just use the best-pace hits for the ending split.I don't think it's possible to display the best-pace hits for splits you haven't completed yet in a column.