How do you make computer lose in a pong game?

So me and my partner are trying to make a pong game that's player vs. computer, but we just couldn't figure out how to make the computer lose.

We already have the basic stuff done and it works fine but the computer just never loses. And we also tried slow down the computer peddle using sleep, but whenever the paddle moves slow, the ball also moves slow.

any advice would help! Thanks开发者_高级运维

And we also tried slow down the computer peddle using sleep, but whenever the paddle moves slow, the ball also moves slow.

You need to make it slower by moving it a shorter distance each time it moves.

In the original Pong game, the paddle was perfectly in sync with the ball, that is whenever the ball went down a line, the paddle did too. Obviously, that would make the game unwinnable so the solution used by the developers was to skip an update cycle every few cycles.

In layman's terms, on every frame, you adjust the paddle's location to follow the ball, except on the fifth, tenth, fifteenth, etc. By doing that, your paddle will seem to follw the ball nicely, but with some kind of delayed reaction.

I assume that the computer never loses because it "knows" where the ball is going to go. In that case, why can't you make it go to the wrong place some percentage of the time?

As well, if you just wanted to slow it down, rather than sleeping, you could intersperse "moves" of "don't go anywhere" along with the movement towards what it thinks is the right place to be. So instead of "down 1, down 1, down 1", you could have "down 1, down 0, down 0, down 1, down 0, down 0..." or something along those lines.

I think there is a game site for problems like this https://gamedev.stackexchange.com/. But my answer would be to try and cycle the top speed of the AI bat. And to make the bat short sited. (Only respond to the ball position once it is in its half.)

Computer must make mistakes to lose. The catch is, the mistake must be realistic. If the mistakes seems too artificial, the human player loses interest after a while. The human must believe the cause of the mistake is his good play.

1. The computer may occacionally react late. I mean, freezes when the human hit the ball. This may especially happen if the human hit the ball with the edges.

2. Intentional going slow would be unrealistic. But sometimes the computer may go a little bit slower while defending a ball that would bounce.

3. The computer may plain react to wrong side (for example, go up instead of down) when the ball hit with the middle of the bat.

4. The computer may wait a ball at the wrong place (off by 1), especially if the ball would bounce.

When you use Sleep the whole program stop for some milliseconds. Do you have a game loop ? If so, try decreasing the translation amount, and do not forget to normalize the acceleration vector.

cpuPadlle.Position += amount * acceleration;

Where :

• amount in [0..1]
• acceleration is a 2d vector