Run any Skill in Manus with one click

dc3-pair

Stars4

Forks0

UpdatedMarch 31, 2026 at 07:32

Find DC3 reference implementation for an RB3 unit. Shows function overlap, DC3 match status, and optionally the DC3 source code. Use to leverage DC3's ~87% complete decomp for shared Milo engine code.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

freeqaz

freeqaz/rb3

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer ProgrammersComputer and Mathematical Occupations·SOC 15-1251

SKILL.md

readonly

name	dc3-pair
description	Find DC3 reference implementation for an RB3 unit. Shows function overlap, DC3 match status, and optionally the DC3 source code. Use to leverage DC3's ~87% complete decomp for shared Milo engine code.
argument-hint	[unit-name] [--source]
allowed-tools	Bash(python3 *), Read, Grep, Glob

DC3 Pair Skill

Find the corresponding DC3 source file for an RB3 unit and show compatibility info. DC3 and RB3 share the Milo engine -- most system/ code is similar or identical.

Arguments

$ARGUMENTS - An RB3 unit name (e.g., CharBones, system/char/CharBones). Add --source to include the full DC3 source code.

Steps

Find the DC3 source file for the given RB3 unit:
```
python3 scripts/dc3_compare.py --filter "$ARGUMENTS" --sort rb3
```
This shows functions that DC3 has at 100% that RB3 can potentially port.
If --source is requested, read the DC3 source file:
- DC3 source is at /home/free/code/milohax/dc3-decomp/src/system/
- Map the RB3 unit path to DC3: system/char/CharBones -> /home/free/code/milohax/dc3-decomp/src/system/char/CharBones.cpp
For a unit summary showing which files have the most DC3-ported potential:
```
python3 scripts/dc3_compare.py --units --filter system/
```

For very low match functions that DC3 has solved:

python3 scripts/dc3_compare.py --filter system/ --max-rb3 50 --sort rb3

DC3 vs RB3 Differences

When porting DC3 code to RB3, watch for:

Name mangling: DC3 uses MSVC mangling, RB3 uses MetroWerks (CW)
Compiler: DC3 targets Xbox 360 (MSVC PPC), RB3 targets Wii (CW PPC/Gekko)
Compiler flags: RB3 uses -O4,p -inline noauto -ipa file; DC3 uses MSVC /O2
Class layouts: May differ slightly due to different compilers/alignment rules
Includes: Header paths are generally the same for system/ code
Assertions: Both use MILO_ASSERT but line numbers differ

Porting Workflow

Run /analyze-function on the RB3 symbol to see Ghidra + current state
Run /dc3-pair unit-name --source to see DC3's implementation
Adapt the DC3 source for RB3 (fix includes, member names, assertions)
Build with ninja and check match with objdiff

Tips

DC3 decomp is ~87% complete -- excellent reference for shared engine code
DC3 source: /home/free/code/milohax/dc3-decomp/src/system/
Only system/ code overlaps significantly; band3/ and network/ are game-specific
Use bin/analyze-function first to understand what the original RB3 code does
Always verify with objdiff after porting -- identical C++ can compile differently under CW vs MSVC

More from this repository

same repository

audio-perf-loop

freeqaz/rb3

Orchestrate a multi-wave, doc-synced investigation loop into (1) AUDIO CORRECTNESS — record the game's output and measure how far it diverges from the expected/ground-truth source audio (the "clipped noise" problem), and (2) ASSET-LOAD PERFORMANCE — profile and attribute the load-time stutters. You act as orchestrator/coordinator: each wave plans+reviews, fans out subagents (via the Workflow tool / ultracode) over independent hypotheses, converges, builds, re-measures, then plans the next wave. Agents hand off through on-disk docs. Use when iterating on web/native audio fidelity or load-stutter perf.

2026-06-094

audio-verify

freeqaz/rb3

Verify the game's recorded audio is the SAME audio as the source song AND is played CORRECTLY (right pitch/speed, not clipped/noise/silent). Decrypts+decodes the source mogg into a ground-truth reference, captures the game output headless, then measures identity (mix-robust chroma cross-correlation + Chromaprint fingerprint), playback rate (resample-search → speed ratio; catches the 'chipmunk' bug), and distortion (reference-free clip/flat-top/wrap). Use after any audio change (mixer, limiter, resampler, decode, gain) to confirm the right song still plays correctly, or to investigate an audio-fidelity report. Native-first; works for web captures too.

2026-06-084

stack-layout

freeqaz/rb3

Diff stack-frame layouts between target and base for a function. Labels base-side slots with source variable names from a MWCC DWARF recompile. Identifies SWAPPED pairs (decl-reorder candidates), SHIFTED slots, DIFFER (different variables in same slot), and TGT_ONLY / BASE_ONLY (extra/missing locals). Filters out callee-save slots.

2026-05-274

data-diff

freeqaz/rb3

Diff a DATA symbol (vtable, pointer/jump table, string pool, static initializer) between the target and the decompiled build, showing byte differences and — for each relocation slot — which function/symbol each side points to. Use when a data symbol is below 100%, or to see exactly where your decompiled vtable diverges from the target (which slot resolves to the wrong function). This is the diff counterpart to /vtable and /resolve-vcall, which only read the target.

2026-05-274

resolve-vcall

freeqaz/rb3

Resolve a single virtual-call slot to its function symbol. Given `class, sub-object offset, slot`, returns the mangled symbol at that slot of the named class's MWCC vtable. Use when objdiff shows a vcall mismatch and you have the three numbers off the asm but don't want to dump the whole vtable.

2026-05-264

vtable

freeqaz/rb3

Dump a class's MWCC vtable from build/SZBE69_B8/obj/*.o. Shows every sub-object table (primary + each base), slot index, byte offset, and the mangled function symbol. Use when objdiff shows a `lwz r12, OFF(r12)` mismatch and you need to map the offset to a virtual method, or when verifying a header's virtual-function order against the compiled binary.

2026-05-264

name	dc3-pair
description	Find DC3 reference implementation for an RB3 unit. Shows function overlap, DC3 match status, and optionally the DC3 source code. Use to leverage DC3's ~87% complete decomp for shared Milo engine code.
argument-hint	[unit-name] [--source]
allowed-tools	Bash(python3 *), Read, Grep, Glob

DC3 Pair Skill

Find the corresponding DC3 source file for an RB3 unit and show compatibility info. DC3 and RB3 share the Milo engine -- most system/ code is similar or identical.

Arguments

$ARGUMENTS - An RB3 unit name (e.g., CharBones, system/char/CharBones). Add --source to include the full DC3 source code.

Steps

Find the DC3 source file for the given RB3 unit:
```
python3 scripts/dc3_compare.py --filter "$ARGUMENTS" --sort rb3
```
This shows functions that DC3 has at 100% that RB3 can potentially port.
If --source is requested, read the DC3 source file:
- DC3 source is at /home/free/code/milohax/dc3-decomp/src/system/
- Map the RB3 unit path to DC3: system/char/CharBones -> /home/free/code/milohax/dc3-decomp/src/system/char/CharBones.cpp
For a unit summary showing which files have the most DC3-ported potential:
```
python3 scripts/dc3_compare.py --units --filter system/
```

For very low match functions that DC3 has solved:

python3 scripts/dc3_compare.py --filter system/ --max-rb3 50 --sort rb3

DC3 vs RB3 Differences

When porting DC3 code to RB3, watch for:

Name mangling: DC3 uses MSVC mangling, RB3 uses MetroWerks (CW)
Compiler: DC3 targets Xbox 360 (MSVC PPC), RB3 targets Wii (CW PPC/Gekko)
Compiler flags: RB3 uses -O4,p -inline noauto -ipa file; DC3 uses MSVC /O2
Class layouts: May differ slightly due to different compilers/alignment rules
Includes: Header paths are generally the same for system/ code
Assertions: Both use MILO_ASSERT but line numbers differ

Porting Workflow

Run /analyze-function on the RB3 symbol to see Ghidra + current state
Run /dc3-pair unit-name --source to see DC3's implementation
Adapt the DC3 source for RB3 (fix includes, member names, assertions)
Build with ninja and check match with objdiff

Tips

DC3 decomp is ~87% complete -- excellent reference for shared engine code
DC3 source: /home/free/code/milohax/dc3-decomp/src/system/
Only system/ code overlaps significantly; band3/ and network/ are game-specific
Use bin/analyze-function first to understand what the original RB3 code does
Always verify with objdiff after porting -- identical C++ can compile differently under CW vs MSVC