Discussions

Thanks for the help! Can't believe I missed that!

First, get a reference to the actor it wants to follow; then, turn toward it and move toward it. Depending on your scenario, you may need to reset the rotation of the follower back to zero to complete the steps involved. If the follower moves at a slow rate (certainly, if less than 5 pixels per move), you might consider using a smooth mover support class to eliminate any inaccuracies in moving direction.

Thanks!

Replace lines 31 thru 34 in your MyWorld class above with: <Code Omitted> Then, add the following to the MyWorld

If I knew what it was, I would have said so. Since I do not, there is nothing to say currently. It could be anything from too many actors in the world to loading music files frequently to who knows what.

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