portals-pose-tuner

Pose Tuner

A procedural pose is a pure function of numbers (carry tables, grip offsets, recoil shares) and inputs (pitch, kick, scoped). No authored clip can be "the" gun-holding animation, because the hold has to survive things a clip cannot know — camera pitch, strafe direction, recoil, scope state. Those numbers get found by running the game and changing them, so the Pose Tuner puts a panel in the running game that binds the live tables the frame loop already reads: a slider mutates the table in place and the very next frame shows it.

Read references/pose-tuner.md for the full API, the panel reference, and the caveats. It pairs with $portals-guardian-avatars — bone editing targets a Guardian rig, and its export is the boneAdjust shape avatar.animations.load takes.

It is a dev tool, not runtime

Portals stamps it into drafts at _portals/dev/pose-tuner.js (same origin, so the strict game CSP is satisfied) and strips the whole _portals/dev/ prefix out of published bundles. So the import is gated and its rejection caught, or the published game throws on load:

if (new URLSearchParams(location.search).has('poseTuner')) {
  try {
    const { createPoseTuner } = await import('./_portals/dev/pose-tuner.js');
    tuner = createPoseTuner({ title: 'My game', storageKey: 'my-game-tuner' });
  } catch { /* published build — no dev tools */ }
}

For local development, download the same bytes from https://portals.to/portals-sdk/pose-tuner.js into the project's _portals/dev/ directory. Files under _portals/ are managed by Portals and never upload, so the local copy cannot drift into the bundle.

Wiring

Every touch point no-ops when tuner is undefined, so these lines can stay in the shipped source:

tuner?.table('HEAVY_CARRY', HEAVY_CARRY);            // bind the live table, mutated in place
aimWeapon(avatar, tuner?.apply(inputs) ?? inputs);   // forced inputs override pitch/kick/scoped
const dt = tuner?.dt(rawDt) ?? rawDt;                // pause / single-step / slow-mo