Discussions

It is much easier to just re-locate the actor instead off removing and adding a new one.. See what you can do with that information. If you have difficulties with it, show what you tried and ask for assistance again.

Change the line to: <Code Omitted>

Orb issue is fixed, now and updated on site. The problem was that the Scroller class was treating the QActor objects as if they were normal Actor objects (not maintaining their more precise location coordinates). A slight modification to the 'scroll(int, int)' method in the Scroller class to move QActor objects as QActor objects was all that was needed.

That is fine. Now, it looks like you are creating all 4 Hero objects and using the switch to place to proper one in the world. Also, it looks like the choice of hero is held by an int value and the Hero objects are created with a String object. Then the Hero objects use the String value (incorrectly, I might add) to set the fields appropriately for each type hero. I said incorrectly because you are comparing String objects (are they the same object)-- not String conte

An idea I had involves placing all 17 clouds in the world to begin with and uses the transparency of the image of the cloud to temporarily hide a cloud for a short time when it reaches the left edge of the world; then showing back up on the right when its timer has run its course. Create all 17 clouds from in the world constructor. Spawn the clouds into the world with a random x value of: <Code Omitted>This will cause a few to be spawned along the left edge. Have each Cloud object act once after being placed into the world so that

AIGHT! Thanks so much. I haven't been checking up on this, but thanks for your help Dan.

When created or added into world, choose one of the four directions at random and also choose a random distance to move from one to the distance to the edge it will be moving toward. These two choices will need to be maintained in fields to be used each act step. During each act step: set rotation to direction, move and decrease the distance needed to travel and reset rotation back to zero; then, check if the distance left to travel is zero or not -- if so, choose a new direction and distance (the change in direction can be limited to a simple left or right turn, if desired).

In world act method, do this: If no ball in world: * remove all blocks * remove paddle * (re) prepare the world (add blocks, paddle and ball)

It may also be worth noting

Yes -- of course.

My suggestion still stands. You are dealing with another issue there. Post the M4 class codes.

You can't call the getOneIntersectingObject method if the actor is not in the world (line 68). Calling that method calls a different method in greenfoot.Actor which looks like this: <Code Omitted>So since the actor wasn't in the world it threw the exception.

Pause the scenario while in level 2 and while a bullet it in the world. Then right click on bullet and select the Inspect option. Report back exactly what the top-most line of text reads (along the top edge of the Inspection panel).