A modding framework and mod collection for Tomb Raider Remastered I-III and Tomb Raider Remastered IV-V. Built on Frida injection with an Electron shell.
Focused on Tomb Raider Remastered I-V.
Prerequisites: Node.js (18+)
git clone https://github.com/burn-sours/burns-mods-framework.git
cd burns-mods-framework
npm install- Launch the game
- Run
npm run start - Click Launch in the shell
npm run buildProduces a portable executable in releases/.
Mods live in src/mod/ and follow a naming convention:
mod.js— Default mod (loaded on startup)mod.{name}.js— Named mod (e.g.mod.no-fall-damage.js)ui.html— UI panel formod.jsui.{name}.html— UI panel formod.{name}.js
The shell displays a dropdown to switch between all available mods. See docs/FRAMEWORK.md for the full API reference and examples.
burns-mods-framework/
├── docs/
│ ├── FRAMEWORK.md # Builder API & runtime reference
│ ├── CONTRIBUTING.md # Contribution guidelines
├── src/
│ ├── framework/ # Core framework (main branch only)
│ └── mod/ # Mod files
│ ├── mod.js # Default mod (Template Mod)
│ ├── mod.{name}.js # Named mods (e.g. mod.no-fall-damage.js)
│ ├── ui.html # UI for mod.js
│ └── ui.{name}.html # UI for mod.{name}.js
└── media/ # Icons and assets
main— Core framework, docs, and curated mods.mod/<name>— Each mod gets its own branch. Best mods get merged to main.framework/<name>— Framework/docs changes, merged to main via PR.
Mod releases are published from their branch as pre-releases on the Releases page. Each release is tagged to its mod branch (e.g. mod/unlimited-ammo/v1.0).
All modding knowledge lives in docs/. If it's not documented, we don't assume it works.
All patch data definitions — variable names, function signatures, parameter descriptions, and behavioral observations — are entirely the interpretation of Burn and the project's contributors based on reverse engineering. They may be incomplete or inaccurate.
Other community resources such as TRosettaStone, OpenLara, or Croft Engine may offer deeper or more accurate explanations of certain game mechanisms.
All contributors are welcome to improve the understanding of the game — better descriptions, corrected signatures, newly discovered variables — it all helps the project and everyone who enjoys it. Put in a PR!
See docs/CONTRIBUTING.md for guidelines, code standards, and PR process.
- Discord
- Support Burn
- Burn's Multiplayer Launcher (separate project)