It seems to me that many good scripts spend time trying to detect minimum or maximums by replaying the same process several times and comparing results. If the standard functions would stop at local minimums or maximums or at identified offset on either side of them then the scripts wouldn't have to start and stop so often, save the game in one of the slots, play some more, replay, etc. The game would be more pleasant to play as well as achieve results faster, or so I believe.
Yes, a minimum/maximum positive/negative score change threshold for stopping wiggles/shakes would be good.
It was mentioned in a thread Tlaloc wrote, I couldn't find it at the moment.
http://foldit.wikia.com/wiki/Lua_Functions_That_Should_Be_Implemented
Look for threshold parameters.
Tlaloc's text is dealing with maximum positive/negative changes, to get results finer than a wiggle with 1 iteration.
To my opinion, a minimum value would also make sense, so you could chose a high iteration value, but the tool will stop earlier, if there is nothing changing anymore.
Morevoer, the threshold values should be valid per each iteration.
I made good experiences doing it this way.
Thanks. I guess I need to look more closely at tlaloc's work so I don't duplicate suggestions.
It seems to me that in addition to the threshold functionality it might be nice to have an array of minimums and maximums so one can choose the highest high or lowest low or any particular instance within the set.
Pull in a given direction,
get array of minimums,
select position with second lowest value,
…
Since I've only done one script so far I'm probably not the best for suggestions.
I'm mostly watching them work and thinking about them and what they are accomplishing.
Baby steps.
Yes, he did very much, the whole site was made by him, as far as I know.
I can do some programming, too, but not that professional.
Had to learn Lua by myself from scratch for the game, I only did VB and a little bit C / Turbo-PASCAL before.
In my regular job, the focus was rather on hardware than software (software, too, but more controlling devices).
Well, you could pull 5 times into a direction, save and get the score of each pull, then compare them, and load the state you want.
But saveslot handling should be more flexible (like Tlaloc described in Wiki), and we should also be able to get the associated score of the saveslot.
All wiggle and shake functions could return the score value with a minimum function rewriting. It is so diff
icult to change de void for the current score? Not the best solution but…
answered