Discussions

Can anyone help?

First, I see no code that tries to change the value of any Counter object (in fact, I do not see any "eating" either). Then, I see that the Counter object held by the 'counter' field is not going to be the same Counter object that you place into the world (remove line 34 -- so that the Counter object already created and saved in the 'counter' field is added into the world on the next line).

First, it is strange to see the vertical movement speed ( 4 ) being faster than the horizontal movement speed ( 3 ). Next, with the current code, by not using 'else if' structures, you will are allowing diagonal movement as well. Unfortunately, even though diagonal movement are avoided, some directions will supersede others with that. There are other ways to code key controls that avoid diagonal movement an

You mixed up 'Cactus' and 'Catcus' as you may already noticed.

Yes and you need to change i<4 to i<8.

I fixed with your code danpost. Thank you very much

thank you so much

Write \n at the position you want a new line to begin.

To make the world unbounded: Double click your world subclass. Find the first line in the world constructor and add another parameter 'false', e.g.: <Code Omitted>To make an object remove itself from the world, use the 'this' keyworld: <Code Omitted>

The 'MoveWithPhysics' function is essentially drawing a line segment between my current location, and the new desired location. If this movement line were to intersect any wall, I want to place the player slightly behind the point of the collision (that way he isn't stuck in the wall). As for the fisheye-effect, thanks for the tip. I will look into that. Also, interesting fact about doom. I hadn't realized that.

First, I would add fields for a pre-determined destination grid-square: <Code Omitted>The initial value of these fields should be the coordinate values of the location the actor was placed into the world at. The 'addedToWorld' method can be used for this (so you can use 'getX' and 'getY' to set the value of the fields with). Then, to make things a bit easier, we will alternate between moving horizontally and moving vertically. This will mean only one tu

Thats great, thanks SPower and danpost

Um, assuming that you followed the tutorial word for word, it should work 100% of the time. Double check your code and make sure everything is exactly the same. If all else fails, then paste the problematic code here.

Thank you very much, this solution is great! The actor doesnt seem to stay near the same location in reality though so it works fine. Thanks again!

What are the differences between the classes? Actually, I do not think anything in those classes should be declared as 'static' (as yet), except for maybe the images. Remove all occurrences of the word 'static' in those classes. Note (do not make any changes for this unless you fully understand or get further help on this): I mentioned the images because currently, as your code is, each en