Let's try two examples. Change a game's speed, then return to Calculator and rebuild its % button.

Goal
Rebuild the game with adjustable speed.

Why reverse engineer it?
To reproduce its acceleration, we need the rule in the running game: how fast it starts, how much it increases and when it stops.

What each part does

  1. 01 · REARead the running game’s scriptReturn its actual code and settings to the agent.
  2. 02 · Your agentRebuild the rule, add a controlUse the recovered acceleration in a small game with a speed slider.
  3. 03 · YouChange the speed and playTry the original acceleration, then choose your own pace.
See the script, checks and how to try the analysis

REA inspected the HTTP browser edition through a local debugging connection and returned the loaded index.js, including its source and digest. 

ACCELERATION: 0.001,
MAX_SPEED: 13,
SPEED: 6

We called the original game’s update function in a controlled browser check, with obstacles and automatic scheduling disabled. After 4,000 updates, speed was 10.0; after 10,000, it was 13.0, rounded to one decimal.

The new mini-game keeps that speed rule. Its drawing, jumping and collision code are a small teaching implementation. Open the lab to see the new code and run the same speed check.

To inspect the target yourself, follow the browser connection steps using the dinosaur page. Give your agent that page URL and your local debugging endpoint, then copy the prompt above.

Inspected speed code · Chromium Authors · BSD license