Discussions

Yes -- but you would not put it in the Shield class. The only thing the shield should do is absorb damage and remove itself. Use the Spaceship class' act method to put it in: <Code Omitted>

You currently cannot create a Pedestrian object (which includes a Villager object) without a direction parameter. The simplest way to rectify the situation is to add the following to the Pedestrian class: <Code Omitted>Now when created without the direction, it passes control to the constructor w

Thank you so much! This helped a bunch, and saved a lot of time.

What mechanism do you want for aiming and triggering?

You may want to see my Value Display Tutorial scenario. It has a section on non-textual display of values and specifically touches on this type of visual counter.

Thanks! I have solved the problem. Sorry for the late response.

The equal sign on line 23 is the problem.

Thank you a lot!

The problem is with the code in your Attack and Attack2 act methods. The 300 milliseconds is 3/10 of one second -- and, you have the object being removed from the time it was created. Well, the internal clock of the computer continues to run even when your scenario is not running.

This kind of problems often occurs when static attributes are used. (e.g. "TestWorld.notes" should be non-static). A static attribute is bound to the class itself instead of the object. So, if you have two testworlds, the static modifier means that you have only one value for notes that is used by both testworlds. So, if notes is changed by one testworld, the change interferes with the other testworld, too. Especially, if you restart your program and a new testworld object is created, it still continues to use the same (already used) notes value that was used in the first run. In constr

I did not research it; but, I believe that it returns a java.awt.Canvas object. Being as you cannot upload anything using the java.awt package without running into security issues in javascript/HTML, any scenario using that package will fail to work on a

Thanks for the help, it doesnt give me the error anymore. The fact that the attack will hit the player creating it wont matter, because it will only affect P2.

Nevermind, I made it work. Thanks for the help a lot!