I have repeatedly called for inclusion of an augment to the restore best function, starting last spring and repeated again this fall and early winter, but unfortunately it appears that both the original suggestion and subsequent posts on the subject have vanished and the idea seem to have gone unnoticed.

So, one more time if I may

The best score is saved in a file, which stores the highest scoring protein configuration for a player's puzzle entry.

It is just a positive-value peak detector.

That is

If Score > Best score, save to autosave-best

Pressing ctrl-b, the new hotkey for restore best, or using the mouse to click the "To best Autosave" button under the Undo Window then simply loads the workspace with that instance.

To explain the concept of "New best" once more,

1) New best would use a hotkey to store the New-best-Autosave file to the current score on screen, regardless of whether it was the high score or any score.

2) New Best would use a companion hotkey to the first which would load the New-best-Autosave file, identically to using the restore-best, except that instead of loading the Autosave-Best, it would load New-best-autoave.

3) New best would perform its function identically to the standard restore-best. That is, it would autsave overwrite it's file with language nearly identical that of autosave-best

If Score > Best score, save to autosave-best

AND (note that logical AND)

If score > New-Best, save to New-best-autosave

Under this method, new-best does not negatively impact the current function or its content, so if the is a concern amongst the developers to that end, there need not be.

4) To simplify the work required, it would be incumbent upon the player to ensure that they do not hit restore-best during use of the new best function. To do so would immediately overwrite their New-best-autosave with the current high score, ie their best-score. To add a new set of rules that blocked such a situation from occurring could be implemented, but imo it would simply add to the complexity of such a feature addition and prolong its absence from the toolset. IMHO, some user responsibility for any tool use is required...

It is important to stress two facts.

First, any implementation should not interfere with the autosave-best file. this should be obvious, but for the record, no one in their right mind would suggest overwriting the autosave best (which at present is essentially the only way a player can achieve some of this capability, by manually deleting, moving, or renaming the files containing pertinent information to that end, resulting in the ability to use the fundamental ability but becoming unable to restore their high score without more manual work - in the case of those smart enough to either move or rename that is...).

Secondly, addition of such a feature would be simple. Very simple, in fact, based on the method used by foldit for implementation of both its Autosave-Best_score and undo contents, all of which are file, or said another way, image based in nature. The lack of said function is a great shortcoming of the game, as it often makes the use of human intuition quite difficult to achieve due to the one-way-street approach currently enacted, forcing the user into either restarting or continuing with whatever approach was originally enacted by the user. This really limits the "human approach"

Humans aren't linear, instead we think along multiple paths, using internally branching "algorithms" to decide on how best to progress, and this feature request has been outstanding for over six months....

The required code addition is absolutely trivial, and following bug repairs, imnsho, this should be right at the top of your task list.