I think you are required to key a number in for the other color parts (at least zeroes, if that is the value you want for them). You could programmatically account for an empty return string. I do not know if setting a default '0' value for the inputs would be enough.

In fact, with a little testing, I figured out that the current act cycle completes before the scenario is actually stopped (in other words, even if the 'stop' was in the world class act method, all the actors will still have their act methods run afterwards before the scenario stops).

You missed fixing this one: * greenfoot : move left/remove at edge should check '<= 0' Also, somewhere you stated that the statement after a 'Greenfoot.stop();' statement would not execute. That is not true. The method will still finish even after the 'stop' statement (and the current 'act' method will also finish up, even if it calls a method with a 'stop' statement in it).

Things to fix: * boss-basic : correct relational operators should not have (0 <= x) as a valid answer * greenfoot : move down/remove at edge should use 'getWorld().getHeight()-1' * greenfoot : move left/remove at edge should check '<= 0' * animal : WALKING_SPEED : Question 2 answer should be 'Cannot tell from the given information' as neither the cellsize nor the rotation is given (movement is in cells -- not pixels; and the rotation could cause variance in the actual distance moved with the cellsize causing an exaggeration in this variance); with a cellsize of one, the answer you have would be approximately correct.

@lordhershey, the image came from my Kaleidoscope scenario at http://www.greenfoot.org/scenarios/4780. The settings used were as follows gravity: 1016 contortion: 1210 stretch: 832 fold: 10000 translation: 0 zoom: 46 distance: 40 x: 0 y: 0 background color: white (by way of code change)