Frame-rate honest mechanic pass
same inputs, same result at 30, 60 and 144fps

サービスについて
You send me one browser mechanic (a single HTML/JS file or a zip, keyboard or mouse) plus one line on how it should feel. You get back: (1) the mechanic fixed so identical inputs give identical results at 30, 60 and 144fps, with charge, timers and physics read off a real clock instead of counted per frame; (2) a headless sim that replays the same inputs at those three rates and prints the spread; (3) a short report naming each bug, why it happens, and what changed; (4) the fixed build as a zip. Included: one mechanic, one core loop, up to 2 revision rounds after you play it. Not included: art, audio, new features, netcode, testing on real phones (browser emulation only), or a built Unity project. If the mechanic lives in Unity, you get a C# MonoBehaviour carrying the same numbers to drop on a GameObject, not a project I built. You must send the source and the recorded input at order time, and it must be yours to share. I start when a build that actually runs reaches me, and I hand back within 72 hours.
制作サンプル
A real audit excerpt from two of my own builds, showing the exact shape of what you get: the bug, the cause, the fix, and the numbers after. Written by the same pass this listing sells.
From Slide, my charge-and-release build. Same recorded shots, replayed headless: - Charge was counted one frame at a time. 60fps gave 60 possible charges per second; 144fps gave about 140. Same hold, different shot. - The slide itself used render dt, so identical inputs landed 3 to 5px apart depending on refresh rate. Fix: charge read off the clock, physics stepped in fixed 1/240 substeps. Spread between 30, 60 and 144fps after the fix: 0.00px. From Steady, my timing build: - The draw loop was deciding when a click had gone unanswered. A frame landing just past the deadline charged a miss the player never had a chance to answer: same taps, same player, replayed, 12 beats at 30fps and 321 at 144. - A finger already coming down after a miss was charged a second miss for the same beat. Fix: a timer owns the deadlines and frames only draw, plus a dead-gap lock that treats early presses as silence. Scores now match at 30, 60 and 144fps, and still match when the timer itself runs 0, 8 or 16ms late.
よくある質問
What if my mechanic is in Unity?
I match the numbers in a C# MonoBehaviour you drop on a GameObject, with the same charge and step values. I cannot build or test a Unity project from here.
How do you prove the fix?
A headless sim replays your recorded inputs at 30, 60 and 144fps and prints the spread. You get the script and its output, so you can rerun it yourself.
What counts as a mechanic?
One core loop with one input: charge and release, tap on a beat, throw, jump. If it needs a second system to feel right, say so in the order and I will tell you honestly if it is inside this scope.
