Discussions

In a simple variable assignment line like the following: <Code Omitted>The return type of 'methodName', or any literal, or the result of any expression evaluated on the right side, must be of type 'VarType'. If the method returns a boolean value, which the method 'isTouching' does, then that value

You might want to see this discussion.

Nevermind, I resolved it, found out that worlds already had world-related methods already at the disposable.

Could you please send your debug-log and the description of how you get the error to us, as described in: http://www.greenfoot.org/support ?

It works, thanks!

I am trying to make this work as well. I cut and past from bonney, still no luck. I tried the sound recorder and it works fine, Greentfoot recognizes the mic. Any help would be appreciated. <Code Omitted>

You have only shown one of the two mentioned here. As far as the Counter class, it is a waste of cpu time to recreate the image of the Score object every act cycle when the score only changes once in a while. Change 'act' to 'updateImage' and do the following:

thanks alot!!!!! u helped me with this game (: (: (; (; thnxxxxxxxxxxxxxxxxxx

if (atEdge()) getWorld().removeObject(this);

thanks got it . problem solved, thanks

There is the 'setLocation' method. When touch occurs, you can use it to separate the two actors so they are not touching. But, you will need to do more to ensure that the zombie does not immediately move back into the chased and cause more lose of health before some time (your preference as to how long) has elapsed.

I solved it with a by decompiling the library a dirty solution. So I still want to know the proper solution

Don't worry i used what you gave me earlier and put it into display3() THANK you very much.

This is probably not perfect, but an example how to do it for the left side. The problem you will be facing is that if you for example walk in one direction and change the direction, the image may change a few act-cycles too late. To avoid that, you could use a field to track the current direction and if the direction is changed, you set the 't_animation' to 9, so the first image is used instantly.

I think this is because the compiler doesn't now exactly what is wrong just which line and the type of mistake so it can't always give you the exact world in which the mistake was made. And you can see which type of syntact error there is on the bottom left