Thanks, I've passed it to the team to see if they have any ideas.

this is a tad important - one of the most used GUI recipes (Blue fuse) no longer works as intended....it appears that lines of instructions have simply disappeared. Considering the warning from U (Foldit central) that more or less no one will be about next week.....any chance of a concerted effort to sort this?

A bit of digging into all.macro shows that old GUI recipes have "ActionNoviceRestoreRecentBest" and "ActionNoviceResetRecentBest" for these actions. But the GUI recipe editor in the client simply omits these steps. From the earlier feedback, it seems like they are skipped when you run the recipe as well.

If you add the actions in a new or updated recipe, they are rendered as "ActionStandaloneRestoreRecentBest" and "ActionStandaloneResetRecentBest".

It would seem to be a simple matter to accept either name for the corresponding action.

Looking at "Blue Fuse GUI w25 [NC]", recipe 48188 it seems like there may be some other problems with how old GUI recipes are displayed in the GUI recipe editor. I'm limit up on my folding for the moment, will update this feedback later with more detail.

Does someone have a list of GUI recipes to "quarantine" until this is fixed? Or can I just search GUI in recipes?
(I have a bunch of them, not all sorted into GUI and LUA.)

Synopsis: GUI recipes get modified as they are downloaded or run.

In testing, I first downloaded "Blue Fuse GUI w25 [NC]", recipe 48188 manually into a client that's not connected to chat.

The downloaded recipe gets written to "single.macro". This version of the recipe is intact.

The downloaded recipe gets incorporated into "all.macro". In this version, the recentbest actions have been eliminated, and all subsequent steps have been renumbered This happens without running or editing the recipe.

I also tested with an all.macro that had a number of GUI recipes with recentbest steps. If you run one of these recipes, the recentbest steps are deleted from that recipe, and all.macro is updated with the changes.

GUI recipes that you don't run stay intact, and running Lua recipes also doesn't hurt anything.

The good news is that the recipes on the server seem to be intact. So any shared recipes can be re-downloaded once this is fixed. You can also manually add the deleted steps to any recipes that have been zapped. The re-added steps are written out with the "Standalone" versions of the keywords. Presumably those keywords will continue to work going forward.

Also good news is that other recipe steps don't seem to be affected, although I haven't tested all the actions. So far, only the GUI recentbest actions are a problem. I was confused when I suggested other actions might be an issue.

One point of confusion stems from how the recipes are stored. The steps are stored as properties named "action-0", "action-1", "action-2", and so on through "action-10", "action-11", "action-12", and so on. The steps are executed in this order.

The confusing part is that the steps are written to the file in collating order, so "action-1" is followed by "action-10", "action-11", and "action-12" and so on. As a result, the file order is not the order of execution on recipes with more than ten steps.

If anyone is interested, I now have a vim edit macro that makes all.macro or single.macro more readable. If anyone knows a Lua package which handles properties files (like options.txt and yes all.macro), please PM me.

Further testing of "My GUI Script [NC]" and "Aotearoas_Romance" revealed that the "Restore Very Best" action (internally "ActionNoviceRestoreAbsoluteBest") is subject to the same issues as the two "recent best" actions. No other issues were found.

Quick save and quick load actions are also affected - they appear in all.macro as ActionNoviceQuickload and ActionNoviceQuicksave, but they do not appear in the GUI recipe editor in foldit and are not executed.

Team's been narrowing down the cause - these reports have been helpful. I don't have any ETAs of adjustments or fixes yet, though.

This looks like it was caused by some internal restructuring that we have done recently. We'll look into hooking everything back up correctly. Thanks!

jflat
thanks for getting to this. when you fix it, can you let us know if we have to delete and reload all our GUI recipes. It is not clear tome that they have not been corrupted, soI'd like to understand if I have to rebuild my cookbook
Much appreciated. I never realized how much I'd miss GUI
Skippy

Has this problem been cured without that being mentioned? I just checked the running of a GUI recipe that uses restore recent best a number of times and it appears to be fine

Mimi
I ran a test run of blue fuse GUI version this morning my time. GUI still not working for me. So unless we have to reload every GUI recipe again, this is not fixed

Actiasluna tried reloading Bluefuse GUI 25 into newest client. It still does not work correctly in restoring best scores, etc.

Boosted to the team this morning, no updates yet.

Edited to add: Solution being investigated/worked on, but no ETA.

Just a quick test on 20161207-87ca1b235d-win_x86-devprev, but the results look promising.

I ran an existing recipe, and the cookbook remained unchanged at the end. In particular, the "ActionNoviceRestoreRecentBest" command survived intact.

A more complete test is still needed.

Also, editing or downloading a GUI recipe crashes devprev, see feedback 2003194.

I'm having problems when trying to download gui recipes. Connected foldit client crashes every time i try to download a gui recipe.

just to note, I'm "main" client, PC windows 7
not going to download and replace my GUI recipes until notice this is fixed

Just to add

Crash (windows) trying to dowload GUI recipes with their number in blue pannel. Example:

http://fold.it/portal/recipe/1878

Simple actions like mutate and shake are abnormally low on GUI after several steps. The following recipe never ends:

https://fold.it/portal/recipe/103612