Hmm... Nice to see someone else follow up on the RTS genre. I like the resource collection design, and the construction too. I would suggest improving the pathing by either forcing the units to move directly to the target point, or by making the movement smoother in general. I haven't looked at the code, but my guess is that you are using a four way movement system. Bumping this up to eight way would smooth out a lot of the wrinkles. A piece of advice: If you aren't very artistic, get a friend to make images. Almost all mine were done by friends. I am interested to see how this turns out. Are you planning on doing isometrics? If you are, I could give you some tips based on another Greenfoot isometric I am doing. Also, are you going to try for a scrolling world? I have thought some about it for my own RTS, and was forced to give it up for time and speed constraints, but I could give you some tips on that too.

I was making a game like this.... Beat me to it ; )

In this version, the engineer has his own resources (Yes, there can be multiple engineers!), but I did not add code to deduct from his resources whenever he is building. I'll update it and engineer's resources will be deducted, and I'll use the 8-way system for random movements with the enemies.

Right. The first thing you should know if you are going to make an Isometric game is that is is "impossible". Greenfoot does not support manual layering (mostly). The only way Greenfoot does it's layering right now is based on what order the units were added. What this means is that if you want your isometric terrain to hide stuff behind it, you will need to re-add your objects ~every act sequence. Now, the downside to this is that if the Greenfoot code changes the way it orders objects, your game would need _serious_ changes. However, I don't see this happening that soon, so I would say go ahead with it. The exact way to do all that is a bit complicated, but I could try and post an example sometime soon. There is a plus side though: Isometrics mean re-writing the code to the extent that a scrolling map is almost easier than a static one.

I had a thought regarding isometrics: I believe that a small re-write of the Greenfoot world code, or possibly just an extra addObject method with a layer parameter could work. Dunno, but maybe I'll look into it next week, when I have a little free time.

Zerg! you forget the fantastic command of setPaintOrder, which allows you to set The order in which Greenfoot paints objects onto the world, thus solving your entire conundrum.

Paint order doesn't work for isometrics: you want to have some objects in front of a wall, and some behind, and then you want to have the objects switch layers later. Right now, the only way to do this is by re-adding EVERY object in the world over again in a different order. I am still looking into the world's code for class layering in hopes of maybe finding out how it works.