NUP & DUMP REPAIR

Project ReLink compiles exclusively against one verified game revision: Program ID 0400486024DEC000 with Update v131072 installed (main NSO Build ID E0F3CCFAF50065AE4EA01EB5AEB13B1A45DA3348), and automatically repairs damaged scene cliff actors via mods\00-dump-repair.

0400486024DEC000Required Program Title ID
v131072Mandatory Installed Update
e0f3ccfaMain Executable Short Build ID
00-dump-repairAutomatic Damaged-Scene Fix
High-resolution silicon die lithography showing deterministic instruction paths
Static AOT lifting maps exact instruction addresses from build E0F3CCFAF50065AE4EA01EB5AEB13B1A45DA3348 into C.

Accepted Game Input Formats & Version Check

Why static recompilation requires exact binary offsets and how to run make_game.py --check before compiling.

Why Only Update v131072 (Build e0f3ccfa) Works

Unlike dynamic emulators that interpret arbitrary game revisions, Project ReLink translates specific function boundaries, jump tables, and graphics hooks inside nx2/lift.py. An unpatched base image (v0) or an incomplete folder dump has different function addresses and will be rejected cleanly by the launcher before any files are written.

The Project ReLink launcher automatically scans Downloads, Desktop, and Documents for compatible .nup packages, or lets you drag a .nup file or select unpacked romfs and exefs folders manually. Developers and power users can run a zero-install preflight check from PowerShell:

python -I nx2/make_game.py --nup "C:\path\your-game.nup" --check
Verification Field Expected Value in Project ReLink
Program Title ID 0400486024DEC000
Update Version v131072 merged or present in unpacked exefs/romfs
Main NSO Build ID E0F3CCFAF50065AE4EA01EB5AEB13B1A45DA3348
Accepted Containers .nup package OR directory holding romfs + exefs
Source File Safety Read-only inspection; your copy on disk is never altered

Automatic 00-dump-repair Cliff & Rock Fix

Starting in v0.6.1 and made universal across dumps in v0.7.9, Project ReLink detects damaged RomFS scene archives automatically.

Symptom 1: Black Cliffs in Hyrule Field

Some extraction tools corrupt baked cliff geometry inside RBake_Scene archives, producing pitch-black cliff walls around Hyrule Field and Zora River even when Vulkan shaders compile cleanly.

Symptom 2: Infinite-Loading Blurry Boulders

Truncated mipmap streams in damaged actor packs leave boulders stuck at low-resolution placeholder textures while background streaming threads retry endlessly.

Automatic Stand-In Mod Generation

During installation (or when pressing Repair game copy in the launcher), tools/dump_check.py and tools/dump_repair.py synthesize clean stand-in assets inside mods\00-dump-repair\romfs\ using intact textures already present in your own copy.

Universal Repair in v0.7.9

Project ReLink v0.7.9 broadened dump_repair.py so every known variant of damaged RBake_Scene cliff and rock pack is repaired deterministically without sharing copyrighted assets.

Recommended PC Hardware

Verified storage and controller upgrades matched to AVX2 static compilation, 60 GB build scratch space, and dynamic HUD button prompts.

Hardware note: As an Amazon Associate we earn from qualifying purchases at no extra cost to you. Project ReLink requires an AVX2 CPU, 16 GB RAM, ~60 GB free NVMe SSD space during compilation, and an XInput/SDL controller.

Samsung 990 PRO 2TB PCIe 4.0 NVMe SSD

Sustains high random I/O across the 60 GB C compilation workspace and 16-minute first-boot Vulkan pipeline generation.

Check on Amazon

WD_BLACK SN850X 2TB NVMe Internal SSD

Dedicated secondary game drive for fast ASTC texture streaming and async background shader cache reads in Hyrule Market.

Check on Amazon

Xbox Wireless Controller (Carbon Black)

Native XInput support with automatic Xbox HUD glyph replacement (prompts\keytex.bin) and radial Item Wheel stick targeting.

Check on Amazon

8BitDo Ultimate 2C Wireless Controller

Drift-resistant Hall Effect sticks ideal for Project ReLink circular stick deadzone tuning (0 to 50%) and quick R/L item cycling.

Check on Amazon

Project ReLink FAQ

Direct engineering answers verified against the GPL-3.0 pixl27/ProjectReLink repository and release artifacts.

Where do I get the .nup file for Project ReLink?

You must dump Title 0400486024DEC000 and Update v131072 from your own legally purchased hardware and game copy. Neither pixl27/ProjectReLink nor this documentation site hosts, links to, or distributes game files, keys, or dumping utilities.

How do I trigger dump repair on an existing Project ReLink installation?

Open ReLink.exe (the launcher) in at least v0.7.9 and run Update or rebuild against your game copy; tools/dump_repair.py writes the repaired stand-in files into mods\00-dump-repair and records each loaded mod in relink_log.txt.

Can I disable 00-dump-repair after re-dumping a clean .nup?

Yes. In Project ReLink, any folder inside mods\ whose name starts with - or _ (such as _00-dump-repair) is skipped at startup, or you can rebuild from your clean .nup.