I am still doing some play testing with chapter 4 to try to help people not get stuck as often, so I think I will definitely be adding more torches, and possibly a small piece of code to add torches if you are stuck in the dark without any. And that 'general notice' spamming is me experimenting with some scripted scares actually XD Nothing to worry about ^^

This method does lag a little for me, but I think it's because you are creating a whole new GreenfootImage and looping through it pixel for pixel. It would be *much* faster to skip the GreenfootImage part and just sample the pixels needed to produce the magnified part

You didn't include Graphics g = buff.getGraphics(); panel.paint(g); That is actually important you know :P

It may be an undocumented and unsupported command, but I think it should stay :D How else can we do crazy things like hiding the mouse and scroll wheel access! And yeah Duta it might be tricky to make sure the magnifying glass isn't included, but I think it might be able to work.

You might be interested to know that you actually can gain access to the Image the world displays (including actors). The code would be as follows; JPanel panel = WorldHandler.getInstance().getWorldCanvas(); BufferedImage buff = new BufferedImage(panel.getWidth(),panel.getHeight(),java.awt.image.BufferedImage.TYPE_INT_RGB); Graphics g = buff.getGraphics(); panel.paint(g); Through that code you are able to generate a Graphics and a BufferedImage that have the data of the World Image. There is no easy way to transform this data into a GreenfootImage as far as I can see, but you can easily access individual pixel color, which would make your scenario work extremely well I think. No matter how many actors on the screen, your code would still be running at the same speed, since you wouldn't need to redraw any of the actors.

Good to hear! Yeah I fixed the terminal output and the Maintenance problem, but I didn't do anything else, so I wonder what fixed it for you o.O Were you able to get it to quit reliably?

Hmm well the numbers were probably some leftover debugging code I couldn't find, but the quitting expectantly sounds strange. Could you check the debug log to see if there were any Greenfoot crashes?

Whoops good catch on the name-code and the console garbage. I have not experienced the random quitting though, was this in Greenfoot or in Browser? What OS were you using?