Funscript tools

Funscript Validator: will this file play?

Drop in any .funscript, from AutoScript Sync or anywhere else. The validator reports what stops a file playing or makes it play badly: invalid JSON, missing or malformed actions, timestamps out of order or repeated, positions outside 0 to 100, and moves faster than the speed limit you set for your device. When it finds a problem it offers a repaired copy: sorted by time, duplicate times merged, positions clamped to 0 to 100 and rounded. Moves that are too fast are reported but left as they are.

Open the Funscript Validator

Report Studio: what did the generator do?

Report Studio opens a .funscript and, optionally, the gen_*.json report the desktop app writes after each generation. From the script alone it shows duration, strokes per second, stroke depth and a speed histogram. With the report loaded it adds the engine's findings, motion-type shares and the anchor-election scores. It reads the files in your browser and makes no network calls.

How to read a generation report in Report Studio, or go straight to the Report Studio tool.

What both tools expect

Both read the common funscript layout: an actions list of {at, pos} points, at in milliseconds and pos from 0 to 100. Report Studio assumes the actions are already sorted by time; files the app saved always are, but a hand-edited file may plot wrongly until you run it through the validator. The funscript format reference explains every field.

Read next

• The funscript file format, field by fieldWhat the tools are checking against.
• Funscript troubleshootingWhen a script plays wrongly, what to check first.
• What stays on your PCEvery connection the desktop app makes, and what it sends.