Objective
Show that the agent can get from where it stands to a named position using only the screen and the keyboard, and stop there.
Method
The controller reads the character’s coordinates and facing from the game’s on-screen debug text, turns the camera with the mouse, and holds the forward key until it is within a set distance of the target. If it stops making progress it tries a jump, then backing off and sidestepping, and gives up after three failed recoveries.
The pass rule was written down before each test: arrive within 3 units of the target, without a person touching the controls. Keel chose the waypoints. Alexander supervised by stream.
Result
| Test | Distance | Trips | Arrived | End distance |
|---|---|---|---|---|
| Flat walkway | about 48 units each way | 3 round trips | 6 of 6 legs | 2.24 to 3.00 units |
| Steps, 12 blocks of climb | about 40 units each way | 3 round trips | 6 of 6 legs | 2.00 to 3.00 units |
| Road out of town | 298 units each way | 1 round trip | 2 of 2 legs | within 3 units |
The road route took about 40 seconds out and 36 seconds back. One stall on the way out was cleared by a jump. No enemies appeared.
Limits
- One town, one time of day, short distances chosen in advance.
- This is a hand-written controller following waypoints an AI assistant picked. It is not a learned skill and it says nothing about general navigation.
- The controller cannot see water, cliffs or roads. The routes avoided water because a person and an assistant read the map first.
- When the sky is bright behind the debug text, the text cannot be read. The camera is pitched down to keep it over the ground.
Next
Longer routes, and a way to recover when the straight line to the next waypoint is blocked.
Evidence on file
reports/nav_20261110/NAV_RESULT.mdreports/nav_20261110/NAV_RESULT_TEST2.mdreports/nav_20261110/ROUTE_RUN_RESULT.md
These files are kept with the project. Ask if you would like to see one.
