Checkbox for if rupees behind board were collected

[csunday95]

If the three rupees behind the board are collected, the RNG tick rate in the room is changed. A user entry method to indicate the rupee state is required for maximally accurate prediction of offset.

[csunday95]

appears to be partially implemented by @petersn at https://github.com/petersn/web-sploosh-kaboom/blob/master/src/App.js#L431 but commented out in current deployment

[Amphitryon0]

I think the hardest part of this is designing what the feature should do. If there were no user-configurable settings, I would say it should adjust timer rate, timer intercept, room entered offset, timer standard deviation, reward offset, next board mean, and next board standard deviation. But with all of those except reward offset exposed to the user, the decision becomes much harder.

If we want to have this checkbox, then the user shouldn't need to configure anything else by default to use it. But we still want everything to be configurable, since the whole purpose of the configuration is to allow individualized or simply better known values to be used without us updating the site.

The best option I can think of is to duplicate all of these options and switch out which set we use based on this checkbox. Only the active set would be shown in the UI, but both sets would be saved locally to persist changes to them. This does have the issue that the user cannot see all of the settings at once, but I consider that relatively minor.

It also seems, based on Peter's incomplete implementation, that he wanted to support collecting the rupees while in the room and then immediately playing a game. In my opinion, this is way too complicated, and the best results we'll ever get with it will only be marginally better than not using the timer at all.

[Amphitryon0]

Regardless of how we may want to implement this checkbox in the future, there is currently nothing stopping users from manually entering the values needed to play with the rupees collected. Thus, I don't feel this should block the version 0.1.0 milestone.