Discussions

Nice thx and the information about the 60 act cycles is also very usefull.

Sorry, but that is not a possible solution. In fact, it has the same failings as the initial issue -- a NullPointerException error will be thrown on line 5, here. You cannot call a method (getObjects, removeObject or any other World method) on the returned value of

Yes, I have used this code in my project. Thank you for your time I appreciate.

The field name should probably actually be curTime, meaning the current time. It, as well as lastAdded, whose value is the actual time that an enemy was last added into the world, should both be declared somewhere. Since the lastAdded field needs to be retained through multiple act steps, it must be declared outside the method:

Show your code.

Sorry, the "exact same appearance" thing was weird. It works now, thanks!

You create two objects of Army1 and Army2. Each. And you pass the ones to the LineOfSight object which aren't added to the world. Remove the prepare method and add army1 and army2 to the world that you create in line 5 and 6.

Not sure why you mention this. I was not saying to remove line 25 or anything like that.

This does the same: <Code Omitted>

I think the problem is that the level counter is always initially one every time you create a new Levels object. I do not think it to be a very simple fix. Maybe you should take a look at my Super Level Support Class Demo scenario. It might lead you in the right direction.

<Code Omitted>

They open this discussion instead of the real one which isn't helping you at all.

I don't know what question 9.69 is or how exactly the code looks (I am looking at asteroids-3 right now, so the counter is already there, just not functional). You have the space, the rocket, bullets and asteroids. The world instance should create and add a counter to the world (to itself). It should also keep a reference to this counter. Then, when you want to add points to the counter (e.g. a bullet hits an asteroid), you get the reference to the counter from the world and add one point to the counter.

It does it in the same act-cycle. So it won't be visible there if it immediately moves back. Otherwise, you had to replicate the isTouching method instead of using the current location, use the one which it would have after moving. But that is really unnecessary. To the first question. You could exit your method with an error message if x or y are greater than 7.

I have no clue what "pikel" is. However, make sure that there are no needless transparent areas around your images. As an alternative, you can use methods which do not take the image into account, but only the position of the object.