I haven't encountered crashes yet but it is probably best for early or mid-game, I'm guessing.

Hey cjddig, just a quick couple of suggestions I have after running this for the first time.

1) If you're going to change the wiggle power, give the user the option of what to change it to. I was working on low wiggle power and was caught off guard when the script changed it to high without warning.

2) Also have an option for the user to select whether or not they want to work with their current pose or credit best. Due to number 1 my credit best pose was not what I wanted to work with, so even after deleting the wiggle power code and re-running, I ended up working with the incorrect pose again.

3) I'd recommend saving the original pose in one slot and the best scoring pose in a different slot. Then never overwrite the original pose's slot, I may want to go back to compare my original pose to the ending pose.

4) Add some dialog options for wiggle iterations.

5) More of a personal preference but I would take a look at breaking your code up into smaller functions. Refactor out distinct blocks of code that do 1 thing. For example, the dialog or when you compare the score or when you're printing, those could be a separate functions. This also makes it easier to read and understand your code.

Cheers,
TurtleByte