215 IsMutable = true
120 IsMutable and IsLocked = true
101 true mutables found the old way! O_O
If IsLocked is to be believed, Mutate Combo mutated up to 6 locked segments (537 clean script says my rank 100 score is clean, but it has 2 mutated locked segments).
Let's see, the extra segments marked true mutable are 38, 220, 225, 301, 316, and 319…VLYHLL. A script shows these 6 as both selected and locked!
list= { 38, 220, 225, 301, 316, 319}
selection.SelectAll()
–structure.SetAminoAcidSelected('g')
for i = 1,#list do
print(list[i], selection.IsSelected(list[i]), structure.IsLocked(list[i]), structure.GetAminoAcid(list[i]))
end
Tracking all these down shows that they have locked backbones and free sidechains (whew).
Request structure.IsLocked() return a 2-tuple for BB and SC status, or a 3-tuple = BB and SC, BB, SC.
the puzzle has points and they seem to be on player pages these are quite wrong.
spmm, do you mean that it's wrong that there should be any points awarded because of the bug?
or
that points were awarded normally since the puzzle closed, but something is wrong with how this puzzle was scored?
Since the bug was noticed so late, we didn't close the puzzle or reduce the number of points or anything. Turns out that if we closed it and re-opened it with the bug fix you would still be able to load in incorrect solutions because there is no check for that (so we'd have to update both clients… etc. you can see it gets messy!)
So the puzzle should have closed as normal and points assigned the way the usually do.
Let us know if something went wrong with the normal scoring!
Thank you and again our apologies for this, but thank you all for catching this mistake!
The puzzle closed and points were accorded normally.
The problem is that several people leapt on and started using the script even though they knew it was a bug, these players gained massive points from the script, Deen said she got 150 points in about ten minutes.
Other people stopped playing at that point with around 9 hours playtime left. The players who were using the script just kept it running, and of course many people would have been running other scripts and been unaware of the problem.
So the scores just before the script was introduced are fair and could be used, but may also inadvertently contain incorrectly mutated segs - and I assume that your comment in global that: ''Seth says we should be able to scan all the solutions for the correct sequence and give credit based on that.'' will somehow eliminate all of the bad mutations, and may of course penalise people who unknowingly mutated a frozen seg, because their pose and sidechain scores may be adversely impacted. That is ok just bad luck.
Rav and brow have created a test script to run to check the puzzles :)
@ spmm…
It was actually much worse, I let the script run it's course as I said in global, because I still think that something is not quite right with my mac devprev client (I wanted to see if it picked up any normally mutable sidechains and what it did with them). The final tally of points for me was more like 350, and 50 ranks.
I did a pm to beta today stating my concerns about this, and that of course my score should not stand.
As you say - many folders had likely inadvertently run one of the older scripts that also showed this bug in main, both on this puzzle and on the previous CO2.
I do hope that the devs are able to scan the solutions for the bad mutations. There are many folders who worked very hard on these puzzles, and should get the credit they deserve for them.
I have brought this up in a news post: http://fold.it/portal/node/992332
We will manually recalculate all the scores for both puzzles, where only valid solutions will count.
jflat06 is looking into resolving this obscure bug so that it never happens again!
Until then, thanks to Rav and brow for creating a test script to double-check new puzzles!
Please PM me (as well as posting a feedback) if you ever notice this to be a problem in the future.
