Patch forges and resource identity
Each game’s section below covers what is known of its patch forges.
Ghost Recon Breakpoint
Section titled “Ghost Recon Breakpoint”Breakpoint data mods replace or add resource ClassIDs in patch forges read by the normal archive loader. The three common targets are DataPC patch data, DataPC_Resources patch data and DataPC_extra patch data, but the resource id, not that organizational split, supplies identity. Sourced · GRB · Breakpoint format reference
The community describes no official SDK and relies on AnvilToolkit unpacking and repacking. Extracted filenames use positional numbers; changing such a number does not change embedded ClassID. Replacements preserve an existing ClassID, whereas new resources require distinct identities and references reaching them. Sourced · GRB · Breakpoint format reference
| Filename behavior | Evidence scope | Confidence |
|---|---|---|
| Arbitrary new base name | No general *.forge scan in the analyzed executable |
Sourced · GRB · Breakpoint format reference |
| Numeric patch suffix | Patch scanner parses suffix number, including numbers above one | Sourced · GRB · Breakpoint format reference |
| Backup copies matching the wildcard | Can enter the live patch list | Sourced · GRB · Breakpoint format reference |
| Parenthesis in name | Opener truncates at the first ( in the analyzed code |
Sourced · GRB · Breakpoint format reference |
The archive-resolution page distinguishes global from scoped lookup; higher patch priority is not established as a universal rule for all paths. Sourced · GRB · Breakpoint format reference
Riders Republic
Section titled “Riders Republic”In Riders Republic most patch copies equal their base copies. Of 178,814 Entity identities stored in both a base and a patch forge, 550 have different bodies; all 61,699 Mesh identities stored in both are byte-identical. Among the 550, 78 change body length; four inspected cases add one 25-byte DataLayer action. All 550 keep the same component count and first component header, so those leading fields are not patch-version markers. Observed · RR
Its base/patch data pairing is observed, but custom forge mounting and live replacement behavior are not established by the offline archive reader. Unknown · RR