yay the difficulties brilliant theres a little bug where if you sorta squash the ball into the wall it go's really weird up and down but still brilliant

Encountered a situation in the level with the row of invinsible bricks. If no breakable bricks remain in the general area above the unbreakables, the ball can bounce back and forth repeatedly in the same pattern and will not ever return to the bottom half of the screen. A random, but infrequent, small turn could fix this.

@danpost Thanks for your suggestion. I will look into fixing that bug as soon as I can. @lux Nice score. @hotrails Thanks!

@danpost Thanks for your suggestion. I will look into fixing that bug as soon as I can. @lux Nice score. @hotrails Thanks!

And then it happened: the ball bounced back and forth repeatedly in the same pattern between a wall and a side of the paddle. At 50.000 I decided to write this instead of going to see a score go overboard ;)

It is possible to clear it, but it would take 2 updates to complete the process; plus it would take lux to play it between the updates. The first would be to add 'if (score > myInfo.getScore() [b]|| "lux".equals.myInfo.getUserName()[/b])' so when lux plays it, that score, no matter what it is, will be saved in the UserInfo data. And the second, to remove what was added; so a worse score by lux will not be saved.

Well, I don't think it needs to be that complicated, danpost. Since you can easily get a list of the top players from your scenario by using UserInfo.getTop(0); - the first element in this list will be lux' info. You can then easily set the score back to zero.

@trash1000, First, the UserInfo data can only be changed if you are logged in as that user. Second, if the scenario is programmed to save the score if, and only if, the new score is larger than the previous high score, then it needs to be adjusted somehow to allow a smaller value to be saved. If this is made a permanent option as 'erdelf' suggested, then only one update is neccessary. If this route is taken, I would also suggest a verification of deletion somehow.

@danpost Thanks for your explanation, I didn't know it's impossible to change the score of other users without being logged in to their accounts. I decided to implement the "right click to delete score with verification" method @erdelf suggested. This way it's not limited to lux and people can score more than 400000 points.

To avoid this kind of glitch, you should check the direction as well as location, like in the following: private void checkWalls() { if( (deltaX < 0 && getX() < getImage().getWidth()/2) || (deltaX > 0 && getX() >= getWorld().getWidth()-140-getImage().getWidth()/2) ) { Greenfoot.playSound("sounds/cling_1.wav"); deltaX = -deltaX; } if(deltaY < 0 && getY() <= getImage().getHeight()/2) { Greenfoot.playSound("sounds/cling_1.wav"); deltaY = -deltaY; } } Also, the last few lines in your act method can be removed.

There is also a problem that arrises when the ball bounces back and forth between to non-removable bricks. A small random change in direction would fix that.

@danpost Thank you, I used that method and didn't get problems with the ball anymore! For your second problem, I already had that random change in direction built into the game. I made it a little bit less infrequent now, so it should not take so long until the ball comes out of a hopeless situation.

Schau doch in den Quelltext (Klasse Ball). Die Physik dahinter ist nun wirklich nichts großartiges - Einfallswinkel gleich Ausfallswinkel. Das ist keine große Berechnung.