Discussions

Oh, i should've had calculated that was it, (the demo had an option for bigger region).

Seems quite clear to me: Oh. and -- your welcome. Note: I just noticed I missed the parentheses after the getRotation's in my code.

Presuming nextlvl is your button, it looks like you are adding the button into the world right at the start. I presume that no actor will be in the world after all items have been clicked on. Therefore, if you add the button at that time, the condition to add the button goes away (the fact that no actors are in the world). So, you can simply add something like this:

Change <Code Omitted>to <Code Omitted>

The shm is not in the installation folder, it is the project.greenfoot file which you open when you open your scenario in Greenfoot. (Unless this is different with a Mac, I use Windows.) But for your problem: Try to increase the world size and/or decrease the number of objects you add and/or decrease the minimum space between objects. In a bad case, an object can't find a possible place and it keeps searching for it forever. If the total number of objects doesn't matter that much, you could also do something like this in the addedToWorld method. Then it will stop search

Thank you very much! It works now. :D

Removing every "static" from your code would be a good start. None of these variable should be a class variable. Also, a Shuriken is not a Character and a Fireball is not a Boss. So they shouldn't be subclasses. I don't really understand this sentence. In your code, I only see the Shuriken checks if it hit the Boss (hurt method). Obviously it will also hurt the boss if it is only hitting a Fireball because your Fireball is a subclas

The merge sort algorithm basically cuts lists in half and sorts them. You won't be able to implement the algorithm without creating more lists in the process. The Wikipedia article is pretty helpful I would say: https://en.wikipedia.org/wiki/Merge_sort

Try it. Use the Act button for testing. (I presume that the method is being called from the act method).

Although I am not too familiar with Python, I doubt, in general, one is much more difficult than the other. I would guess that it would depend more on the individual (preference in style and previous programming knowledge).

I am a bit lost in your code to be honest. What is the purpose of the State class and its subclasses? Why don't you just put that in the world subclass? It is also weird that you have several variables in which you save the world, but you still use 'getWorld' instead most of the time. I couldn't reach 6000 points yet, so I have no clue what is causing it. Is anything special happening at 6000? Lag usually happens if too many actors are in the world at the same time. For example if actor A is spawning another actor A every act cycle, then the scenario will basically stop after a second. By th

Thanks for the code Super_Hippo! That helped my figure out that when I was clicking inspect sometimes I was also clicking on the object (I feel dumb now) and that's why it seemed like the Pause button was changing it because when I clicked play it would register that click.

OK thank you.

With my Levels support class, the main Levels world was only meant to be created once at the very beginning of a run. All other Levels objects were to be from its subclasses. The Levels class itself was intended to create a header world and be a place where all common methods and fields can be maintained (it seems your er# fields might be a candidate for promotion to the Levels class). You may want to create a separate world for the level selection process.