lmao got em

If on a Windows system, try hovering over task bar icon; then, move to mini-image and right click to select "Maximize".

There is another, actually 4, indexOf methods in the String class. Make use of stringName.indexOf("phrase", position) where position is where in stringName you want the search to start.

It is quite straight-forward: <Code Omitted>

Take a look at your checkDeath method. You got through all rotation to do pretty much the same thing as the following if with getOneIntersectingObject -- quite redundant. Remove lines 59 to 98. Next, notice that you ask about death right after it could possibly be changed. Better coding would be to just do what needs done when it is changed (as by copy/pasting lines 106 thru 111 to be inserted at line 103. In fact, that way, you would not need either variable death or redbike/bluebike.

Maybe a misunderstanding here. I did not mean each time the car intersects (hits, or first comes in contact) with an oil slick. I meant the continuous intersecting of the same hit. For one car/oil slick collision, there will be some time of interaction. This will most undoubtedly take a number of act cycles. I was asking if these things that you want done, we to be executed once per collision (regardless of how long the intersecting lasts) or executed once for each

Please show an example of what you are referring to (definitely not explained well).

If you mean make multiple health bar classes -- not an idea worth considering. Keep it simple. Have one class to display a bar. Create how ever many bars you need from that one class.

Download/install the Greenfoot application. Run it and select 'Scenario>New Java Scenario...'; give it a name and click the 'Create' button and, !voila!, you have created a scenario. Granted, it does not do much (rather, anything); but, you will be on your way. Just add some code (at minimum).

You are calling moveAround from the constructor, which is executed only once before the created actor is placed into a world. This question should point you in the right direction to fix the issue.

Well, it is either keyboard controlled or not (two possibilities). So, a boolean field in the class of the controlled actor seems to be what is needed. If there is a possibility that the controlled actor might change to be a different instance, then an Actor field in your World subclass could do the trick (or a static one in the class of the controlled actor).

A way to do this would be to randomly pick a direction. Then create a counter and make the object move in the random direction for <counter> act cycles. When the counter hits 0 you pick a new random direction and fill up the counter again.

I WAS NOT OF THE MEANT TO OFFEND, I AM ERNIE WHO IS VERY SORRY