The objectives area is shown under the score in the top center of the Foldit screen. The objectives can be collapsed or expanded by clicking on the small triangle next to the word "Objectives".
Design puzzles typically have several objectives which are filters, and are specific to a puzzle. (The terms "condition" and "filter" often used interchangeably.) Design puzzle filter objectives typically award bonus points if they are met completely, and subtract points when the design is less than perfect.
Only some puzzles have filters, but all puzzles have a second type of objective, a condition which must be met or satisfied. A unmet condition results in red line through the score, meaning the score is not valid. An example is having an open cutpoint. Opening a cutpoint causes a red line through the score. All cutpoints must be closed for the player's score to count when the puzzle closes.
A similar condition occurs when a player opens a shared solution as an evolver. The score will have a red line through it. The red line persists until the player gains 2 points over the starting score. At this point the score becomes valid and a blue "Evolved!" popup appears briefly on the screen.
A final common condition occurs when filters are turned off for performance reasons. (Yes, it's the condition condition.)
Objective, Condition, Filter, Layers[edit | edit source]
The words used to describe objectives in Foldit have changed over time.
The term "filter" was originally to reflect the idea of "filtering" the score and adding or subtracting points. In recipes, some of the functions in the Foldit Lua Interface have "filter" in their names.
The term "condition" was used for yes/no tests which determined whether the score was valid. Some of the recipe functions have "condition" in their names.
The Foldit team finally arrived at "objective" to describe both filters and conditions. Both affect a Foldit player's score in some way, and both are outside of the basic scoring provided by the underlying Rosetta software. Everyday discussions in the Foldit community may use objective, condition, and filter more or less interchangeably.
The term "layer" is also seen, usually in the "Core Existence" filter found on many design puzzles. The core existence filter, originally called "layer score", was one of the first added to Foldit. The idea is the the protein has a surface layer open to the solvent that's all around (but never seen), and a core layer, where the solvent can't get in. There's also an in-between boundary or transition layer between the surface and the core. The "show" checkbox on the core existence filter changes the coloring to the protein, showing blue for the surface area, green for the boundary area, and red/orange for the core. Some Foldit recipes may have "layers" or "for layers" in their names, meaning they were adapted for the core existence filter, turning off filters at certain points.
Toggle All, Run All[edit | edit source]
Objectives, particularly filters like core existence, can be expensive to calculate. Foldit offers players the option to turn off checking for one or more objectives. The objectives area offers a "Toggle All" button to turn objective checking on or off for all objectives.
Individual objectives can also be turned on or off using checkboxes when the objectives list is expanded.
Turning off objective checking results in a red line condition. Players must turn objective checking back on using the "Toggle All" and "Run All" buttons to clear the red line.
Recipes can also turn objective checking on or off in an attempt to run faster. There are various strategies for when to do this, but typically recipes turn off checking while performing operations like wiggle, shake, or remix, and turn on turn on checking only when getting the current score.