Spielerando

I told my AI the jump feels floaty, but it cannot do much with that

Feelings do not give an AI anything to change. This helper turns a recording of your hero's height into the numbers that describe the jump, including the peak that falls between two recorded moments, so your next message holds facts.

Why this works

A recording only has a position per frame, and the real peak usually sits between two of them. Fitting a curve through the three points around the top recovers it, so the measured height matches what the player saw.

When not to use it

If the jump was designed from numbers in the first place, read them from the settings instead. Measuring is for when the feel and the settings disagree, or when nobody remembers the settings.

In the full entry

  • What to build, step by step
  • Starting values and the reason for each
  • 3 common mistakes and the fix
  • 44 lines of example code with 4 checks that pass
  • How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "I told my AI the jump feels floaty, but it cannot do much with that" (read_entry work-act-describe-floaty-jump-in-numbers) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP