Discussions

The score updating for recency was actually bourne's idea that I implemented recently. The store() method seemed to be not storing properly during my initial testing, but it must have been a different problem in the code. Thanks for the clarification!

@rdlatimer I don't think you are right. When you press act, every object will run the action act(). When you press the run button, Greenfoot simply runs the act() action for every object in the world, the whole time. So actually, the run button in Greenfoot just runs a loop where every object will run the act() method. I hope this lets you understand Greenfoot al little better. (If you're wondering where I got this information: from the Greenfoot book)

Ok; you implement "scrolling" by moving everything to the left (or right). In Greenfoot this could be as simple as getting all the objects (World's getObjects() method) and then looping through them and adjusting their position. You should use an unbounded world so that objects can move out of the world bounds. It's a bit more complicated if you need the background to scroll as well, but to start with you could use a plain background to avoid that problem. This technique isn't particularly efficient, but

Math.hypot(x, y), thanks for sharing that! Yeah the abs() is redundant now that you mention it. And yeah I changed it to Actor instead of Object once I realized I need to call some methods within them. Thanks :D!

Great, thanks for the help, much appreciated.

Download and check out this side scroll demo. That should get you going.

No worries, I've finally figured it out :)

Hit the 'Compile' button. (Hint: whenever the classes have this stripey look, they need to be compiled.)

well i cant take credit for this. i did get these ideas from the book. but i understand now what to do. i think the major mistake that i was that i put the increment of a inside the if statement. my mind kind of went towards that but for some reason i didnt try it. thanks for the reply.

Thank you very much I know how it works now.

Looks like you could try to catch the ThreadDeath Error that happens when you refresh/close, not sure how hard it would be.

There is the system command: System.currentTimeMillis() which returns (as type 'long') the current time in milliseconds (if that is what you are looking for). (Download and check out my Millisecond Timer scenario).

The easiest thing to do is on each act cycle: 1) turn left (keep hand on left wall) 2) move(1) 3) if (blocked) move(-1) (wall was still there) 4) turn right 5) move(1) 6) if (blocked) move (-1) (wall in front now also) 7) turn right 8) move(1) 9) if (blocked) move(-1) (Oh no! dead end) 10) turn right 11) move(1) (back from whence I came) After step (1), you could make use of a 'for' loop to repeat 2 through 4 (4 times -- once for each direction). There are a few advanced mazes that this will not work for (they would have a path that goes forth and completes a cycle back to itself