Also, a method of being able to tell whether someone's online or not. Currently it will only tell you if someone is playing a game or challenging you. If they're using the scenario but aren't in a game and aren't challenging you, you can't tell they're online.

Hey, bourne, you should add so you can see the positions of your enemies ships after a game, because I'll be making misses everywhere, but I can't see where your ships were after you beat me.

@JetLennit gg, took me a while to realize you were trying to write 'Hi'. I made a little smiley face in the corner, although it didn't look very good. XD

Hey, bourne, when your new update on this project comes out, which will allow group chat, you should arrange a time for a bunch of greenfoot users to have a group chat.

I find it funny how above davmac is talking about how shahparacha could possibly have a valid reason for uploading these scenarios, and then immediately after shapparacha basically confesses. Anyways, I believe the solution to this is a fix/update in Greenfoot. When you upload a Greenfoot scenario, I believe that it should 'tag' the scenario once it's been downloaded. This tag should contain the original author of the project, and if someone tries to upload a scenario and their username is not the same as the one stored in the tag, then it doesn't let them. This is simply my suggestion, many other methods can be used to achieve the same goal, but there really aren't many reasons an author would willingly give someone else permission to upload their scenario. I can understand borrowing code from someone, or using their code to understand it, but not re-uploading the same scenario.

Yes, if I was actually going to use this in an application to prevent users from playing a scenario more than a certain number of times, It would be impractical to let those not logged in play, as then users would simply log out to play again. I didn't implement this on this scenario, but if/when I use it with an actual purpose, I will implement it.

I think that the example of the car traversing 'rugged' terrain is more helpful to me than the scrolling world is, as I am (or was) trying to make a game where I needed that kind of car.

Pointifix, w9ndel was uploading this so that danpost and I could help him figure out what the bug in his code was. Please don't get mad at people when you don't even know why they posted it.

It'd take 524,287 steps. I haven't modified it so it goes faster the more rings you use. If you download it, you can use Greenfoot's speed control, but when you put that at the maximum, it's much more likely to make errors, and still takes a LONG time to do 19.