creditbest.GetScore function will crash a client (both main and devprev) if the track doesn't have a credited best yet. (possibly related to https://fold.it/portal/node/996350)
Procedure:
Load un-evo'd player's share in new track.
run creditbest.GetScore()
Alternate procedure:
Load puzzle that has unmet conditions from the start like [DEVPREV] Conditions
run creditbest.GetScore()
Thanks for the feedback Pauldunn! Reproduced this (and the linked feedback) issue has been sent to developers.
Still an issue on both main and devprev.
More specifically, both creditbest.GetScore () and creditbest.GetEnergyScore () crash the client when working on an unevolved solution.
Similarly, creditbest.GetSegmentEnergyScore () and creditbest.GetSegmentSubscore () crash the client for an unevolved solution. Interestingly (?), when these functions are called with a bad argument, such as segment index 999 for the first argument, the error is detected and no crash occurs.
A crash also occurs for creditbest.AreConditionsMet ().
No debug.txt is generated for any of the crashes.
The functions creditbest.Restore() and creditbest.GetExplorationMultiplier do not crash. Sadly, creditbest.GetScore still crashes after a call to creditbest.Restore ().
The other poses – current, recentbest, and absolutebest – do not have this problem.
Using pcall to invoke GetScore and the other crashing functions does not help, nor does running the entire recipe inside an xpcall.
An "unhandled exception" traceback appears in log.txt (see attached).
Crossposted from 1299 feedback… crash on running LUA recipe Banded Worm Pairs
(didn't know about the scriptlog, will be attaching these regularly now)
Working in main, the client which on my mac shows as "game_dynamic" in the finder bar.
Recipe crashes are the most common for me so it is "helpful" to know that this issue is still outstanding.
Are the developers working on this or will we have to live with this bug?
Basically the game client crashes instead of throwing a LUA error when a recipe tries to access the creditbest solution but the current undo track does not have one, because it never had a solution which statisfied all conditions to get credit.
I think that should not be so hard to fix, but this is open for years now. Are the developers overloaded?