I would think that the movement code of the Enemy objects would be relevant information to be given. Please provide Enemy class codes. I am curious as to why your randomSpawn method is within an Actor subclass, also. Seems to me, that would be a basic game action (not something an actor does).

The move code is just a simple move(4); just in case i'll provide the entire act class: As for why the the randomSpawn() method is in its own subclass, I am quite new to Greenfoot and so I am just looking up code on the internet and and plugging in what I find and trying to see what works while also keeping common coding themes among what I find. I had no idea you could do what you just said.

Using move(4), your enemies will move in the direction they are facing -- generally (maybe 40 different possible angles of movement due to pixel restraints). That is not bad, but can be improved on. As far as moving through the screen, I will give a suggestion later. By having the spawning code where you have it, your chances of spawning will have exponential growth. That is, the more enemies you have in the world, the more chance of spawning one. It will not take long before you will be inundated with enemies. Add an act method to your World subclass (MyWorld) and move the spawning code (method and method call from act) there. Now for, the aforementioned suggestion for movement. One idea would be to limit the addition of the enemies to a central location in your world (not necessarily right in the center) and immediately have it move backward to the edge of the world. That way, it will move normally toward and beyond that initial placement location. You will probably need to determine which edge it will start at as well as how far to move to initially place it at that edge. Make use of the addedToWorld method to perform initial set-up of enemies in the world.

Another way is to just choose a random point along the edge for spawn location and then randomly choose another point between 750 to 1650 pixels around the edge for a target point to turn towards (using the turnTowards method).

I think I had an idea like that before where the enemy would spawn in a corner of the screen and based on which corner it spawned in, it would have its own set of angles it could choose from as not to go off screen. should I do something like that?

It is your choice. If you do not mind them all starting from a corner, go with it.

Just two more things: first is you said that this should a basic game action, does that mean it should be in the world class, or water as I have called it? Second question is should be addedToWorld() in the Water(world) class right?, under private void prepare()?

Yes.

So now I have my addedToWorld() code written up: I also know that the world(Water) class should call the object into existence, so my question is how would I call it into the world class

Looks like an infinite loop waiting to happen. If line 9 assigns any number other than zero on the first time through the do loop, the condition to repeat will never be false. I am not sure how your code will prevent the actors from moving toward the corner they are placed in at times, although the chance is somewhat low. I was thinking you should have the world determine which corner to place each one. It could also immediately rotate them accordingly, thereby not needing to use the addedToWorld method.

So I plugged in that code you gave and and it gave me exactly what I want, thank you so much for your time and help. You helping with this has taught me that I can put stuff like this into the world class, so now I can refer back to this and play around it with on potential future projects. One more question, is the world class a parent class, a tester(child) class, or something else?

Not sure what you are referring to -- your Water class describes a specific type of world; and then there is the World class, which is a base class for all world classes.