Discussions

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

The problem is due to the limitations of the screen and the speed of your CommandMissile actors, which is one. The pixels in the screen are arranged in rows and columns. When moving one pixel, there are a limited number of ways the movement can be made -- horizontally, vertically or diagonally (to one of eight pixels). This drastically reduces the number of angles that the missile can travel at. There are a couple of ways (at least) that you can compensate for this; one is to track the location coordinates of the missile with more precision and the other is to save the starting location of

Sorry -- I wrote that out a bit quickly. Line 4 above should be: <Code Omitted>

THANKS FOR THE HELP that was the main issue causing my error and I'll go in and fix up that other stuff too.

Please show the code for the class this 'addedToWorld' method is location within. Also, show what code you are using to add the Skull actor into the world.

its ok now thanks anyways

You should start a new discussion thread on your issue -- not revive one that is over two years old. Also, you need to supply the codes you are currently using (the class of the enemy and the class of the playerheroes).

Thank you soooooo much!!!!!

ok thanks danpost :)

It's okay I was just joking with you :D I love you SPower <3

If you do not have very many sound files and they are all fairly short, then I would suggest keeping a reference to all of them in a class array, like (let us say the code is in a 'MyWorld' class): <Code Omitted>Then: <Code Omitted>and: <Code Omitted>

<Code Omitted>

It may be that you are using the 'getKey' method instead of using the 'isKeyDown' method with boolean fields to track the state of the keys.

You will not visually be able to tell whether the world changed or not because you are re-creating a copy of the same world. You could right click on the world after compiling and select 'Inspect' from the options; then run the scenario, press the "e" key and then pause the scenario; finally, right click on the world and select 'Inspect' again. At that point, if you have two "Inspect" windows open then they were different worlds. You should probably combine line 32 with line 34 so that you are not unnecessarily creating a new 'world' world every act cycle: