← ClaudeAtlas

game-mashup-passthroughlisted

Use when making game A show game B's characters, models or effects inside A (a mashup, cross-engine character swap, or companion renderer drawn over a host game), or when a host-mod needs bone reads, a pre-UI draw hook or a ReShade add-on.
SenjuWoo/Ultimate-AI-Starter-Bundle · ★ 7 · AI & Automation · score 78
Install: claude install-skill SenjuWoo/Ultimate-AI-Starter-Bundle
# Game mashup by passthrough Start-up checklist for "make game A show game B's stuff", from a project that reached a working in-game lab build. The settled technical results (offsets, UE4SS fixes, retargeting, HUD split) live in `project-intel/references/game-mashup-melty.md`: load that card next. Engine routes and per-game recon come from `universal-modder` (`mashup-mods` guide). This skill is the order of work and the guardrails; it does not select Melty or any publishing platform (publishing is a separate, explicit request). ## Pick the route (a wrong pick costs days) 1. Passthrough first: the host keeps AI, physics, animation and hitboxes; a script mod names which body to draw; a companion renderer draws the other game's model skinned to the host's live skeleton. Assets come from the player's own installs into a local cache; nothing from either game ships. 2. Loading foreign cooked assets into the host is a dead end (engine-version mismatch, no runtime mesh API, Unity content can never load in Unreal). 3. Check anti-cheat and DRM before anything else. An injected passthrough is not a candidate for a protected online title. A purely client-side cosmetic route may be tolerated; verify the publisher's current policy and warn about the account risk. Never bypass or disable anti-cheat or DRM. 4. Exclude censored variants and any child-like or age-ambiguous character by name before extraction, not after. ## Order of work 1. Recon the companion tree