Discussions

One thing that can go wrong is that the condition to loop remains true indefinitely -- so, execution is "stuck" in the loop. It will make it seem the scenario is "frozen" as the process never completes.

That helps, thank you!

Sorry mate, didn’t test run it. Good that you figured out how to fix it

You can adjust the propability of objects spawning in line 10 by increasing 20, and you can decrease the maximum time between spawns in line 37 (what cache is set to)

Remove line 48, as it will delay everything -- not just the Igloo actor. You only need one control value for spawning strawberries -- not two ( "i" and "whileOff" ) -- keep 'i': <Code Omitted>(the above to replace from line 27 to 48). Raise "75" in line 25 to something in the mid to high 90s.

Got it

It would be better to have just one class where the input key values are variable, using a constructor with input key parameters.

Show entire page of MyWorld class codes. Oh, line 3 above, given by me, is flawed. It should be: <Code Omitted>

Thanks so much. It worked!

And sorry becaz the reply has no relation to the topic

Use class name (ComplexNumber) for static method calls. Use instance variable name for non-static method calls. The mod method is not static, therefore: <Code Omitted>If you had a static mod method (which you do not -- at least, I did not find one in the class), then you might have something like this: <Code Omitted>

Thank u!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! U wasted a lot of ur time i teaching a newbie After looking at the code i knew that my basic is not strong and i have to strive more(actually i knew it already) I have not been taught java. I m learning on my own and my basic is not so strong to understand ur code. Lastly i would like to say u that; when i will be a genius like u then i shall look that how u made fps Initially i thought that fps would be easy and easy to learn but now its not easy for me or a beginner

True.

The statements in your act methods are not actions (not anything that would be done repeatedly). The first line in both act methods need to be removed, first and foremost. It is almost never wise to create an object in a class that describes (or defines) that type. The second lines only need to be done once, during the creation of said object. That means you can move both those lines to their respective class constructors. As far as the "gravity" issue, you will need to post the SharedResources class codes (so we know what you are working with).