Noyb's picture
Game File: 

It's pong, except the ball contains a second game of pong. Scoring a goal in either game awards you a point and resets that ball only. First to ten wins. The outer layer has a few special rules (can influence the ball's path by hitting it with a moving paddle, and the ball's velocity increases with every paddle hit up to a maximum speed) that the inner layer does not. Note that the two games aren't one-to-one representations of each other and very quickly get de-synced.

Not entirely sure if I played a game like this before. Was fun to make regardless.

Player 1: W/S
Player 2: Up/Down

- Fixed a silly bounds error that prevented the inner paddles and ball from moving in the entire outer ball.
- Fixed an asymmetry in the paddle positions.
- Added a short delay before either ball starts moving at the beginning of the game.

Event Created For: 
Made For: 
An event


kirkjerk's picture

this is (this is (this is

this is (this is (this is beautiful))

This is brilliant. On top of

This is brilliant. On top of being clever in its own right, it solves a problem we didn't even know Pong had: all that down time between hitting the ball and waiting for it to be returned. I've only simulated the proper 2-player game so far, but it feels great juggling all four sides of both games at once.

(But it strikes me in

(But it strikes me in retrospect that this resolves down into being the functional equivalent of Pong with two balls, doesn't it? Though maybe not quite. Probably best not to underestimate the effect of a) the ball-behavior changes needed to keep the inner/smaller game simplified, and b) the sort of divided attention necessary to keep track of both games at once, something that wouldn't at all feel the same if the two courts were laid on top of each other.)

(Oh, a tagline: keep your eye on the ball.)