Discussions

The method call on the right side of line 5 does not return any value (it is a 'void' method). So, you are not assigning anything to the 'run4' variable on the left. Set the variable to a copy of 'run1' using 'new GreenfootImage(run1)', then mirror the new image on the next line.

Yes, I am checking for 60 act iterations -- which is about 1 second -- not 60:

More than where to put 'Greenfoot.mouseClicked(this)', wihich should be ANDed, using '&&", at line 21, is what to use in the 'delay' parameter, which should not be less than one (or rather should not be used at all and a timer should be introduced).

That is correct. I did not know that. But I agree with danpost. Check if you are using it in your act method. I don't think you are.

Ok I've made it, thanks a lot!

Great way to look at it. Merry Christmas.

In the overriding method add the following line: <Code Omitted>

Either in the act method or a method which you call from the act method. There is nothing wrong about just putting it into the act method.

Why not this: <Code Omitted>where 'touchingColor' returns a boolean value indicating the touching state. The parameters would be any information the method might need in order to make the determination on that state. So, the answer to your question is --- Yes. I really do not want to appear so blunt, vague or general about it; but usually, help can only be given in proportion to the amount of information provided.

If you were to put a comment on the 'canSee' method, it should read: <Code Omitted>The center being the location gotten from '(getX(), getY())'. So, the 'shootPlayer' method will need to use something else to determine when to fire. It will also need another condition to limit how often a projectile is fired when the player is in range. This can be a random chance thing or a regular or randomized timer.

Thankyou Super_Hippo and nolttr21

Got it working -thank you!

This is before your moving things around. What I see here is that you move and then check for collision. But the 'originalX' and 'originalY' are acquired after moving; so, it is like -- good luck moving back. That is, they acquire the new coordinates of the actor -- not the original ones.. Now, with the new code, I see you checking collision before moving. How is this to work if the actor is

I would, first off, think that line 4 would show an error and the project would therefore not compile. Also, line 15 looks like it may produce some errors during specific circumstances. It also looks like a single sheep could produce an abundance of new sheep when eating grass. Insufficient code was given to determine why you are getting your current behavior. Please show the code for the entire Sheep class.