@meazelplaq, read my last post. A correction: September of 2011 -- over three years ago should be December of 2009 -- about five years ago

@meazalplaq, I have downloaded and ran the scenario and found the same issue. Being that it appears to work properly on the site AND that there is a check for 'getRotation() == -20' in the code (which today can never return true), it would seem that the implementation of 'getRotation' was changed between then and now. Today, it returns a value in the range of zero to 359; where at the time this was created, it would seem that it returned a range of -180 to 179. (this scenario was uploaded September of 2011 -- over three years ago, with probably one of the first versions of Greenfoot). If you start a discussion thread, I will post my corrected Torso class for you.

Please, remove this scenario from the site. It is not yours to unload. It is a copy of http://www.greenfoot.org/scenarios/8351 by nooby123.

@Dillybar, please start a discussion thread on this issue, I will be able to respond and post code there more easily. However, it will probably be a couple of hours or so as I am pressed for time atm.

It can also happen when there is either a problem with the database server or during maintenance of the server (or probably a number of other reasons on the greenfoot end).

Current tallies I guess would be ok; and you could program it to appear after a certain number of votes have been tabulated. In a way, that would also keep the challenge administrator honest (not saying you would be dishonest; but, others might be more at ease about the final results being they were made public).

Why did you say this: "I shall cast my vote later so no one knows what my vote is."? Nobody should be able to see what anybody else voted -- or even have any idea how the voting is going. This might cause unwanted bias in how they decide to vote. I get the feeling that voting will not be extensive and with only four entries, the results may not even be conclusive (be it what it may).

Yes, but please do so by creating a new 'Discussion' thread. Thee, code posts are easier to view and reference; also, others may benefit by seeing how to correct their similar problems (plus, your scenario page does not get filled with a bunch of comments that deal with bit and pieces of the scenario, instead of it in general as a whole).