Scripting in NewChapter
|Opened on:||Thursday, January 23, 2014 - 21:47|
|Last modified:||Tuesday, May 27, 2014 - 20:56|
I've decided to just create a feedback about this, as NewChapter is going live in 4 days, and these are major issues.
See my comments here: http://fold.it/portal/node/996724
What would be the ETA to add either the matrix caching or wiggle score gain? This is critical to new scripts.
Also, what will be done about existing scripts? They're virtually useless unless wiggle is re-done as by-gain. There are currently 850 public scripts, and I'm sure many group shared ones, and it would be very difficult to convert them all (and useless until we get a matrix/wiggle till point gain). Will we have to do this?
These are pretty important topics, as scripts are now heavily used, and leaving them in a bugged/broken state would either mean that efficiency would go down or everyone reverts to hand folding-reducing the ability of players either way.
Until a wiggle fix, current scripts could do something like this this (using semi-pseudocode):
score = getscore()
wiggleRun = True
wiggleIter = 2
while wiggleRun = true
newscore = getscore()
if (newscore > score + [Some number])
wiggleRun = True
wiggleIter = wiggleIter + [Some other number]
This would work, however resuming back to the last state would mean the possibility, and high probability of wiggle taking many times as long as it would otherwise (depending on your settings even 50x+). Obviously it could be changed by changing [Some Number],[Some other number], and the default for wiggleIter, but who knows what the best results would be for that.... That may even change depending on puzzle size, aas, conditions/filters, current state, etc.
Thanks to the devs for your time. :)