Discussions

You probably fall "into" the block and therefore prevent moving left or right because the actor is now touching the block. When landing (or falling and finding that a block is touched), raise the actor up off the block (use y-coordinate of block minus half the height of both actors' images (plus, maybe, minus 1 more pixel) for the new y of the falling actor.

The boolean animateLeft is not good enough for your needs. It only has two states, but you have 3 animation sets (left, right AND idle). An int value would be more appropriate to track which animation is being used. The best values for each set are '-1' for left, '0' for idle and '1' for right. By adding 1 to the animation set value, simple indices can be acquired (0, 1, and 2), which leads to the opportunity of placing the animation sets in an array. Sample code might look like this:

hello, first of all thx for the help. The problem I have now is that the message: 'you won' is shown from the beginning.

oooh, thanks man!

The last way is probably best as only one time is intersection checked, there.

@danpost Thank you.

holy crap ur a savior

thanks alot, your're thr best!!!!!

For vertical image issue, you could just pass a boolean (true/false) value to the constructor indicating the image is to be rotated or not. Another way is the create a reference to those vertical actors before adding them into the world and turn then right there in the loop. For keystrokes, add an act method into your Space class to detect the possible keys. It would essentially be something like this (which is not complete in itself, but shows the easiest way to break down and detect the different key options):

Most people will not go to an unknown or unfamiliar link. Upload to YouTube or just describe what happens and/or is shown here. Are you sure it is compiling repeatedly? Could it be that it is recreating your world repeatedly or you have an infinitely repeating loop, instead? Post your World subclass codes here for review. You may also need to post the classes of any actors you add to your world during world construction.

I think you are now in the position for some refactoring. If I understand your scenario correctly, the robot is the "protagonist", the actor the player controls. So, it seems that the robot is the one that "owns" the money. 1. So naturally the moneyCounter should be moved to the Robot class. <Code Omitted>As you can see, the source code to manage the money counter already got simpl

You must declare a variable before you can initialize it. However, you can place the initialization code on the same line as that which declares the variable. Example is shown in your own code at line 15, which declares the healthG variable as an int and tells java to initialize the field's value to 30 when created for a HealthGirl actor.

Very good! Finally u have learnt it! I m sorry....ignore the above message I m always thankful to u for helping me everytime

How about improving on what you already have?

Try reinstalling