Question 1

Why compute the ball path server-side instead of just asking the model where to move?

Accepted Answer

Because the model is bad at the raw version. The README reports that without the computed path, Jev picked the right zone for only 5% of descending balls; with it, roughly 90%, and the target stays inside the paddle's reach. So /api/paddle works out the trajectory including wall bounces and reduces the decision to choosing one of 16 zones 50 px wide, leaving all movement physics in code.

Question 2

Does the TypeSafe key stay out of the browser, and what does leaving the pilot on cost?

Accepted Answer

The key stays server-side. The browser posts only ball position and velocity to /api/paddle at most every 150 ms, and that route queries TypeSafe through the @typesafe-ai/sdk, so the key never reaches the client. What is not documented is a per-request price or a per-session total, and there is no local budget cap beyond the fixed pacing interval.

Question 3

Does the pilot survive multiball, or does it fall apart once the game gets busy?

Accepted Answer

Multiball is handled explicitly: the code picks the ball that will reach the paddle first and the model decides where to go to catch it, with a surprise brick able to split one ball into three and up to 12 balls in play. Stale responses are ignored, so a reply that arrives after the ball was lost does not move the paddle. You can check the behaviour yourself, since the panel compares every decision against the exact computation.

Question 4

I only want the brick breaker, not the AI pilot — do I still need a key?

Accepted Answer

No. The key is only required for the pilot: copy .env.example to .env.local and set TYPESAFE_API_KEY if you want Jev moving the paddle, and it stays server-side behind the /api/paddle route, which queries TypeSafe through the @typesafe-ai/sdk, so the browser never receives it. The game alone is npm install, npm run dev and localhost:3000, on Next.js 16 with React 19, TypeScript and Tailwind CSS 4. One thing to plan for: the in-game interface is in French.

Question 5

What is the game built with, and how do I run it?

Accepted Answer

Next.js 16, React 19, TypeScript, and Tailwind CSS 4. Run npm install then npm run dev and open http://localhost:3000. The in-game interface is in French. The AI pilot additionally needs TYPESAFE_API_KEY in .env.local, copied from .env.example.

Question 6

How often does the pilot ask TypeSafe for a decision?

Accepted Answer

The browser sends the ball's position and velocity to /api/paddle at most every 150 ms. The model picks one of 16 zones, each 50 px wide, and the code moves the paddle toward that zone at the same maximum speed as the keyboard, a speed that follows the ball's speed.

Question 7

What happens with multiple balls or a late response?

Accepted Answer

With several balls in play the code picks the one that will reach the paddle first and the AI decides where to go to catch it. A response that arrives after the ball was lost is ignored and marked as such in the decision log, which can export the last 500 entries as JSON.

Casse Brique TypeSafe

About this project

Highlights

Questions about this entry

More Jev resources like this

From the Jev guides

From the Jev community