Since few global points were awarded for Exploration Puzzle 1 Round 1, we will recalculate the awarding of points based on the number of players who played the puzzle (instead of based on the number who met the conditions).
We will do this for the current Exploration Puzzle 1 Round 2 puzzle as well, so please be patient as this may take a while.
Also, we will add in the functionality to separately get the score and exploration score via script in the next update.
Please continue to report each individual problem that you notice with the Exploration Puzzles in the feedback (so that they don't get lost in a comment). We thank you for your patience.
Perhaps you should score both puzzles as only one.
Since you treated the second puzzle as a continuation of the first (which included saves from the first that could be loaded into the second), it would make sense to score them as just one puzzle.
Considering that all you had to do to get on the board was load from the last puzzle, that gave the folders who had managed that (and I was one of those) a ridiculous advantage over those that hadn't.
A number of popular public scripts rely on RecentBestScore instead of or in addition to using quicksave/quickload.
Would it be possible to separate out the RecentBest score into two scores as well, one for segments and one for exploration? This would be at least as much help in scripting as your plan to provide direct access to both the segment and exploration scores (the segment score is already obtained fairly easily just by summing the scores for the individual segments).
RecentBest, CreditBest and OverallBest are an issue in the interface as well. It would be very helpful to be able to return to top segment scores by clicking on icons rather than remembering to save the states manually every time.
When should we expect to see the two Exploration puzzles re-scored?
We actually just finished re-scoring them.
Yes, and each puzzle is now worth 50 points each, rather than 100 points each. This effectively treats them as 1 puzzle in total since solutions for one could be loaded in another.