I noticed that some common recipes leak moves before they display an initial dialog.

It turns out that SetFiltersDisabled is the culprit. Recipes may check the filter bonus by first enabling filters (just to be sure), getting the score, disabling the filters and getting the score, then enabling the filters again. The current filter bonus is the difference in the two scores, but the recipe just leaked three moves without doing anything.

Administrative calls like behavior.SetFiltersDisabled shouldn't deduct moves.

This problem is easy to work around with quicksave and quickload.

The following one-line recipes demonstrates the issue:

behavior.SetFiltersDisabled(false)