Repository navigation
Fighter Recompiler Amendment 1
github-actions[bot] edited this page Nov 13, 2026
·
1 revision
Scope: the owner's milestone-6 decisions, as the Fighter recompiler plan asks ("the decision is recorded as an amendment page"). Progress lives on Fighter recompiler status.
Date: 2026-11-13, after Reptile shipped as a product Fighter option (PRs #209, #210).
| Question (plan, milestone 6) | Decision | Source |
|---|---|---|
| Which fighters come next | Rayden (MKT fighter 24) | Owner: "Can we continue with Rayden, now?" |
| Rayden's power slots | Lightning (D,F + LP) → Ice Blast; Teleport (D,U) → Directional Ice; reversed Lightning (D,B + LP) → Air Ice Blast; Torpedo (B,B,F) → Ice Clone; Shocker (hold HP, release) → Ice Shatter; Slide and Super Slide stay; Freeze on Contact removed; Polar Blast deferred (as for every fighter) | Assistant proposal, owner: "The Power slots are okay" |
| Whether automatic recognition of MKT machine code is worth building | Not decided; default not yet (moves keep being read with the reading aid and written as data) | Assistant proposal; no owner answer yet |
| Which Sektor legacy modules to migrate | Not decided; default not yet | Assistant proposal; no owner answer yet |
- The plan's guidance was that fighters sharing images and behaviours with done ones (robots with Sektor, ninjas with Reptile) are cheaper. Rayden shares neither; his teleport can use Sektor's teleport as a reference and his lightning the generic projectile.
- Rayden follows Reptile's milestone-4 steps: body, inputs, specials one by one, icons and description, then the product option.
MKMSZR current documentation · Wiki source: wiki/ · Evidence/archive: ChatGPT Library MKMSZR Research · Product source: smeagol44/MKMSZ-Randomizer
Orientation / Project
- Home
- Contributor start here
- Project status
- 1.0 requirements and roadmap
- Runtime validation status
- Architecture overview
- Research methodology and evidence
- Glossary
Core Technical Reference
- Core runtime and native payload
- Memory and allocation map
- Function registry
- Address and patch-site registry
- Data structures and encodings
- Resource and overlay system
- Address quick reference
- Testing and CI
Randomizer / Product Systems
- Stage flow and selector
- Pickups and stage-local randomization
- Global item materialization and solvability
- Persistence, inventory and lifecycle
- Lifecycle static closure / unbuilt v05
- XP and progression
- Native HUD and UI
- Presentation and branding
- Audio system
- Palette and recoloring
- Web patcher and product
Stage Reference
Gameplay / Enemy / Donor Research
- Enemy randomization
- Player actions and special moves
- Fighter recompiler plan · status
- MKT compatibility overview
- MKT adapter primitives
- MKT fighter asset translation
- Sub-Zero ↔ Sektor animation mapping
- Sektor takeover proof history
- Toasty audio research
- Toasty visual research
- PS1 research
- N64–PS1 comparison
- N64 -> PS1 port planning and strategy
History / Failures / Superseded Material