You create a Car object, but show a cars class. Cannot do anything about the counter until it is known what you are doing there. Remove act(); from the Level2 class constructor and then take the first 3 lines in act and move them to the prepare method.

Please refer to my Scrolling Tutorial scenario. It does not specifically cover mouse-at-edge action, but other than that, it will not be any different.

Starting off with a big game is probably not the best idea. I'd recommend you to start with the basics of Java, and then slowly start making bigger and bigger projects. But a game already is not a good start I think

I am sure your terminal is showing a IllegalStateExcption error. Line 16 calls the isAtEdge method, which fails when eat1 (line 15) causes the bullet to be removed from the world. You just need to make sure the bullet is still in the world first. Change line 16 to: <Code Omitted>

Remove the first word (Counter)in line 29 of your BossBattle class. Next time, copy/paste the terminal output -- it contains a code trace which usually helps in finding the error.

Your solution might work (with some minor adjustments) if not for two issues. The first one is that you probably have multiple lobsters in the world. A boolean field like hits would only detect (a) crab intersect any, but unknown, lobster; or (b) crab not touching any at all. That is, it does not track which lobster is intersecting. So, if a 2nd one touches while one is already inte

you tell him dan post :) i am ernie

I am th fan of yours i am ernie you are great greenfoot man yes yes

Use an array for the individual die values: <Code Omitted>then sort them in ascending order and iterate thru them to find the straights:

Apparently, you have not initialized a variable called disk before trying to reference it: <Code Omitted>Once it is initialized, you will need an assignment statement: <Code Omitted>to possibly acquire a reference to a disk object. Then your if statement will have a chance to be true as well as false (provided your assignment may or may not actually a

No code, no details -- No help. Always include related codes and specifics. The code should include some attempt at trying to accomplish what you are having difficulty with.

Hier noch mein Code Versuch: Ich habe eine Variabel deklariert boolean treffer = true; In der Methode public void lookforcrab() { If (canSee (Crab.class) && treffer) { Crab krabbe1 = (Crab) getOneObjectAtOffset (0,0,Crab.class); If (krabbe1 == null) { treffer = false; } If (treffer) { krabbe1.lebenszeit(-1); } If (Crab.anzLeben == 0) { Eat(Crab.class); Greenfoot.playSound(“au.wav”) Greenfoot.stop(); } } }

Cheers Hippo