[F.Rq.] Basic Bot: Find best frame count that matches condition

[Sophira]

Currently, Basic Bot works by loading a savestate, running the ROM for a specified number of frames while doing random inputs according to your choices, reading the specified memory locations and comparing them to either the best value achieved or a specific value,

One feature which would be lovely to have is if, rather than checking once at the end of the specified number of frames, to have an option to check every frame and to add the frame number as a possible comparison.

For example, you could set it up so that it would run for a maximum of 50 frames, but to find the smallest frame number (-> fastest time) for a specified condition (say, X position >= 500) to be reached (at which point the attempt could be recorded and the next attempt started).

(You could potentially even use the same comparison operators as with regular memory accesses, so >= would find the slowest time within your max frame count, etc... although this seems less useful.)

I tried searching both here and in the BizHawk forum on TASVideos.org to see if this has already been requested and was surprised to see no results. If this has in fact been requested previously then I apologise, but as far as I can tell this is not something people have asked for.

This will probably slow operation down somewhat as it would involve checking for the conditions every frame (so it would make sense for it to be an option) but it could still be very worthwhile.

[Sophira]

I've been thinking a bit about this and I think one thing which might be good if this feature was implemented is to dynamically reduce the maximum frame count where appropriate.

For example, the following might happen:

1. The user sets a max frame count of 50 frames and starts the bot.
2. The first 5 random runs don't match the conditions, so they all run for 50 frames.
3. The next run matches the condition 47 frames into the run. This run is saved as the current best, and the maximum frame count is adjusted to 47.
4. Subsequent runs go a little quicker as there's no need to test for more than 47 frames.

Note that in the above example the maximum frame count is adjusted to 47, not to 46 - after all, the user might have specified secondary conditions that could result in a better 47-frame run.