Well, yeah, thats what i'm already doing.  What I'm debating is whether or not to do the same thing across saves and quits.  IT would take up a lot more space, and might be unnecessary.

Update!

http://greenfootgallery.org/scenarios/925 !

I have been working off and on, bit I've finally managed to get Object collisions working!  Currently there are 3 mode for playing around with the 2 boxes.

1)Box: Allows you to drag a single box with a rubber band attached to a corner
2)Drag: You can drag around boxes and throw them.  My favorite, but make sure not to crush the other boxes!!
3)Dice: Attaches rubber bands to both Boxes so you can hang them over your dashboard

Drag is currently the most glitchy, but only if you try to throw the boxes really fast at each other or crush them against the walls.  They all have certain problems as well, so if the simulation freezes, press Q and then press Restart.

Alright, so I have been working hard on implementing the event/hint code section.  Whenever you enter a room with new features, your character might make a comment on how to use the new objects.  And this also can be used for dialogue, ect... I did some revisions of the script, finally gave the Antagonist a name that I liked, and worked on save files.  I'm debated whether or not to include hinted objects in the save file.  In the game, there is a temp list so that you only give hints or comments once, so the user isn't annoyed by constant talking when you enter a room.  I'm just not sure if this should carry on if you quit and restart.

Hi Indubitably (coolest word ever ^^) and welcome to the site!

The problem you are describing is called a memory leak.  when you enter a while loop, the calculator needs to remember that it has entered the while loop, so it will know what to do when it gets to the End.  So what it does is set aside a small pice of memory coresponding to that while loop.  When the program exits the while loop, the calculator is able to get rid of that memory, and everything works great.

The problem arises when you have code like this

While x=0
If A
Goto B
End

Lbl B

When you Goto out of the loop, the calculator is never able to reach the End it needs to in order to get rid of that memory.  As a result, you have this chunk of memory that is never going to be free.  If you continue doing this over and over again, eventually the program is going to get very slow, and eventually crash when the calculator runs out of memory.

I see that you use a lot of Goto's in your program, and while that is not a bad thing, it is very important that you don't Goto out of a Loop, as this causes memory errors, slowdowns, and crashes


By the way, if you want to convert your program to text, you can use this web program called sourcoder
http://www.cemetech.net/projects/basicelite/sourcecoder2.php
It will take in and display your program, and even try to optimize it in some cases.

Hehe, The error means you failed

Welcome welcome welcome!  Glad to see you here

Yeah, if the object was restricted to 8x8 movement, it would be a lot faster.  1: because you are moving 2wice as far every frame, and 2: because you are doing half as many collision detections.  But like TsukasaZX said, this is 83+ version, not SE.