Fun exercise. Maybe add light vertical lines to show the levels of indentation possible on the ordered statements side. Also maybe allow us to read the problem before starting the timer, (so the problem shows, we read it, we hit start when ready, then code blocks appear and timer starts).

good job, I like your idea with the indicating arrows if something is wrong! maybe you can make it also possible to be correct if the content of {} isnt intended (?) but good job ;)

Thanks bourne, I added your suggestions. Also, thanks for the feedback AIMrOrange. I understand that some people prefer different indentation levels but I am following the Java standard except for having the opening brace on its own line.

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.

Hi danpost, thanks for the feedback! I understand and will fix all your comments except for the first one, which seems fine to me. When is (x > 0) not the same as (0 <= x)?

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).

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).

Hi danpost. Thanks again! I guess that I made an assumption that I should not have made about the stop() method. I will fix the issues.

That can happen when your Internet connection gets a bit flakey or if you are accessing greenfoot site through a VPN, usually when it happens the scenario takes a long time to load.

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).

@rezendes: The problem is because I am using UserInfo to keep track of information. Java 8 throws a security exception when using storage. See davmac's comments in http://www.greenfoot.org/scenarios/12380

If you can run Greenfoot, you can play JumbledGames. If you Open in Greenfoot you can show me what you have done. If you want online storage see: http://www.greenfoot.org/topics/8200/0