Discussions

Thanks.

Thank you very much. It works.

Wait nvm it's suddenly working?

Wow that is actually really smart Thank you :D

Thank you

sounds familiar :)

I understood ... I'll test. Thank you for now

Thanks!

Sorry for the late answer, everything is working now thank you anyways

Works great. Thank you so much both of you!

That's right super hippo u don't know shit

You used 'under' the line before, so you can't use 'ground' in the next one. You will also need a == instead of = in line 36.

e.g. Level 1 has 20 meteors, level 2 has 30, level 3 has 40, level 4 has 50 and level 5 has 60 and these meteors need to come from the top randomly

I think the minimum size for uploading a scenario is 1 pixel by 1 pixel. The width of the frame in which an uploaded scenario is placed, however, is limited by the GUI control frame below the scenario. The scenario itself is still whatever size you made it. It only looks bigger because the background is white and blends into scenarios with white backgrounds. I would think that there should be a frame around the scenario itself, though -- which seems to be

Sounds like you need both a boolean field to track the state of the "space" key as well as an int field to time the delay after the key is released. If the int field is not zero, do not do anything except decrement the timer and exit the act method. Otherwise, the following should be done. The die should only be rolling when the boolean field indicates the key is up (timer is zero). Anytime the boolean field does not match the current state of the key, then the key was either just now pressed or just now released (there was a change in the state of the key) (again, timer is zero). Negate