Roadmap
What works today, what we're building next, and what stays research until it earns its place.
Read the menus. Publish the settings.
The part working now. We launch a PC game, walk the settings screens, and record each setting: name, value, menu path, and screenshot.
Play the game. Measure what each setting costs.
Next, tests need to leave menus and capture useful frame-rate data from real gameplay. The Decky plugin returns here as a read-only way to surface recommended settings once those recommendations exist.
Pick an FPS target. The plugin handles the rest.
Once enough benchmarks land, the Decky plugin can offer one choice when a tested game launches: apply recommended settings for 30, 40, 45, or 60 FPS?