Discussions

Well, it did matter because the method was introduced in version 2.4. So if you used a version before that, this error would have shown up, too.

world

I'm using medibang -a drawing app- to create the words, so i can easily resize the image to make it smaller and more easy to use. I kinda didn't realize the whole data usage part, or just like memory storage it might take for such a thing to load up. Thank you so much for the help. i'll try to resize the image and use it then and report back later possibly.

Oh yeah! Sorry, I forgot basic boolean logic. I always do that :P Thanks!

doesnt matter i got it to work thanks for the help

Actually, and I fell victim to this above (after seeing your code and not realizing the problem), the check is done on a specific object -- not a class at all. However, with the following, your check could be done anywhere: <Code Omitted>Anywhere, provided the check is repeatedly performed (like from within an act method). The check will be 'true' any time any Food actor is clicked

Still I believe developing Greenfoot games with IntelliJ is way more fun. And this Maven based workflow saves a lot of headache.

Thanks a lot Super_Hippa This works fine, thanks!

OK thanks you very much it works now

You probably just need another closing bracket at the end of the class.

Normally the following alone after the movement code would be enough: <Code Omitted>

IHi danpost and super_hippo I got it. I change the doublearea(1, 2, 3) to doublearea(A, B,C) the value that is being collected thank you guys for all of the help

Manually spawn an object (right click on Actor subclass and select 'new ...'); next, save the world (use menubar: Controls >> Save the World). Then, look at the code in the 'prepare' method that was generated. It will show the kind of code required to spawn an actor into your world.

Welcom friend i am new too i dont learn English a lot and my English is bad Welcom bro

We will need to see the entire class code (1) to see where the given code is located; and (2) to see if anything else is causing the issue.