Resident Evil 2 Remake Modding Guide (2026): Install Mods, Edit Textures, Create Models & Write Lua Scripts

By Posted on

Resident Evil 2 Remake (2019) is built on Capcom’s RE Engine. With the right tools, PC players can change costumes, textures, lighting, interfaces, cameras, and selected gameplay behaviors. Better still, you do not have to be a programmer to install your first mod. This guide starts with a clean game installation and progresses to building a real, editable REFramework Lua script, making a texture replacement, and preparing a model-editing workspace in Blender.

There is one rule that matters more than anything else: check which game build a mod was made for before installing it. The original DirectX 11 (Non-RT) build and the newer rendering branch can use different asset paths and file versions. A mod that works perfectly in one branch may silently fail or crash in the other.

Scope and safety: These instructions concern legitimate PC copies and local, single-player customization. Back up saves, use trusted sources, scan downloads, and obtain permission before redistributing another artist’s assets or Capcom’s extracted game files. Tools and menu labels can change; consult the linked project documentation if yours differs. Nothing in this guide requires bypassing DRM, modifying the game’s executable, or downloading copyrighted game archives from third parties.

1. Choose the kind of mod you want to make

Project What you can change Experience Main tools Suggested first attempt
Install an existing mod Costumes, interface, models, audio, visuals Beginner Fluffy Mod Manager Install one compatible costume or UI mod
Script a small feature Debug panels, optional UI, more advanced runtime behavior Beginner–intermediate REFramework, text editor Build the Lua panel below
Recolor a texture Fabric, signs, weapon surfaces, interface graphics Intermediate RETool, image editor, RE texture converter Edit an extracted albedo texture
Replace a 3D model Props, clothing meshes, selected character parts Intermediate–advanced Blender, RE Mesh Editor Import an existing RE2 mesh, make a small edit
Advanced game edits Prefabs, material settings, animation, behavior Advanced REFramework developer tools, specialist editors Start only after asset-replacement basics work

The beginner path: first launch the unmodified game, then install exactly one mod, then run the sample Lua script. Do not install fifteen mods at once: isolated tests are much easier to troubleshoot.

2. Essential downloads and reliable resources

Download software from the original author or project’s official page whenever possible. Do not mistake an old RE2-specific mirror for the current Fluffy Mod Manager release; the author links users to the newer central Nexus page.

Tool or resource What it is for Required? Official / project link
Fluffy Mod Manager Install, enable, disable, and organize many RE2 mods Yes, for most asset mods Current Fluffy Mod Manager on Nexus
Resident Evil 2 (2019) Nexus Mods Browse mod downloads and check author requirements Yes, for ready-made mods RE2 Remake mod library
7-Zip Open ZIP, 7z, and RAR downloads Recommended 7-Zip downloads
REFramework Runtime scripting, in-game tools, camera and debugging features For Lua mods REFramework GitHub · Releases
REFramework documentation Lua, ImGui, callbacks, scripting examples For scripting Documentation
RETool (FluffyQuack) Extract RE Engine PAK files; texture conversion workflows For asset editing FluffyQuack tools
RE2 PAK filename lists Resolve filenames when extracting archives For extraction Ekey REE.PAK.Tool
Blender Create and edit 3D models, UV maps and materials For mesh editing Official Blender downloads
RE Mesh Editor Blender import/export for RE Engine meshes and MDF2 materials For mesh editing RE Mesh Editor GitHub
RE Asset Library Browse and selectively extract game assets inside Blender Optional, useful RE Asset Library GitHub
Noesis + RE MESH plugin Inspect meshes and textures and convert supported formats Optional alternative Noesis · RE MESH plugin
GIMP / Paint.NET Edit images and, with appropriate support, DDS files For texture editing GIMP · Paint.NET
RE Engine Modding Wiki Current community installation, file format and export instructions Strongly recommended Haven’s Night documentation
Resident Evil modding community Discussion and troubleshooting Optional Resident Evil Modding Boards

Tool-compatibility note (2026): The RE Mesh Editor author has announced the end of official support, and the companion RE Asset Library repository is archived. Their last published versions may still be useful, but should not be assumed to support every future Blender or game update. The RE Mesh Editor README requires Blender 4.3.2 or newer and warns that Blender 5.1 had a serious performance problem for mesh imports/exports at the time of its notice. For a conservative starting point, try Blender 4.5 LTS with the documented add-on release, then test your specific asset. Check the repository’s warnings rather than blindly installing the newest Blender.

3. Identify your Resident Evil 2 Remake version

In June 2022, Capcom introduced an updated version with ray tracing and enhanced audio, while offering the earlier DirectX 11 Non-RT version through a Steam beta branch. Many older RE2 mods specifically target that original build. Capcom’s Steam announcement describes the rollback procedure.

Version Typical asset root What to look for in mod descriptions Good reason to choose it
DX11 / Non-RT natives/x64/ Non-RT, DX11, old version, classic You want to use a compatible older mod
Updated / RT-capable branch natives/STM/ (often shown as natives/stm/) RT, DX12, next-gen, updated You want mods explicitly built for the newer branch

The folder naming is a useful clue, not a complete compatibility test. Mesh, material and texture formats can differ too. Renaming x64 to STM alone is not a universal conversion method.

To select the older branch on Steam:

  1. Open Steam → Library.
  2. Right-click Resident Evil 2 and select Properties.
  3. Open Betas.
  4. If the branch remains available, select dx11_non-rt. No access code was required in Capcom’s published instructions.
  5. Allow Steam to finish updating. Launch the game once before modifying it.
  6. To return to the default branch, choose None in the beta selection.

Changing branches can reset some graphics options. It can also invalidate previously installed mods, so disable mods before switching branches. If the branch list differs from these instructions, follow the options currently shown by Steam instead of downloading unofficial old game binaries.

4. Prepare a clean installation and back up your saves

Locate the game folder

In Steam, right-click the game and choose Manage → Browse local files. On a typical Windows Steam installation, it resembles: 

C:\Program Files (x86)\Steam\steamapps\common\RESIDENT EVIL 2 BIOHAZARD RE2\
    re2.exe
    re_chunk_000.pak
    ...additional PAK files...

Your actual Steam library may be on a completely different drive. Treat the Steam shortcut as the reliable way to find it.

Back up saves and settings

For a typical Steam installation, save data is found under: 

<Steam installation>\userdata\<your Steam user ID>\883710\remote\win64_save\

Exit the game and Steam before copying these files to a dated backup directory. Do not delete or edit the original save files. Steam Cloud is helpful but is not a substitute for a separate backup: a bad change can be synchronized too. You may also copy re2_config.ini from the game directory if it exists.

Verify game files before the first mod

In Steam, use Properties → Installed Files → Verify integrity of game files. Do this before installing mods, not casually while asset mods are enabled: file verification may overwrite or reset modified archives. Confirm that the unmodified game opens and a save loads normally.

5. Install your first mod with Fluffy Mod Manager

This is the easiest way to get started, and it does not require programming.

  1. Download the current manager from Fluffy Mod Manager’s central Nexus page. Download a current release from the author’s page rather than relying on old RE2-only uploads.
  2. Extract the archive to a convenient folder outside the game installation, for example D:\GameModding\FluffyManager\.
  3. Run the manager executable. Select Resident Evil 2 Remake (the exact display name can vary), then point the manager to the game executable or directory if it does not detect the installation.
  4. Visit Resident Evil 2 mods on Nexus. Choose a simple mod with recent comments and a clear compatibility statement. Read its Description, Requirements, Files, and Posts sections.
  5. Download the mod’s intended archive (.zip, .7z, or .rar). Do not run an unexpected .exe installer attached to a purported costume or texture mod.
  6. While Fluffy Mod Manager is open, drag the supported archive onto the manager window, or place it in the manager’s folder for the selected game. A common legacy layout is FluffyManager\Games\RE2R\Mods\; check the current manager’s actual location rather than creating guessed folders.
  7. Find the mod in the manager and enable/install it. Read any message about replacement slots or required dependencies.
  8. Launch the game and visit the scene where the change should appear. For a costume replacement, select the correct character and costume slot. Some replacements will not be visible in every costume or cutscene.
  9. Test for several minutes. If everything works, install the next mod one at a time.

Avoid conflicts: Two texture or costume mods that replace the same asset path cannot both win. The second mod may overwrite the first, or installation may fail. Fluffy Mod Manager handles many file changes and backups, but it cannot make two incompatible replacements compatible.

How to uninstall an asset mod

Close the game. In Fluffy, select the enabled mod again or use its uninstall control. Launch the game and confirm the default asset returns. If the game was updated while mods were installed, use Fluffy’s documented archive recovery steps: uninstall mods, then use Re-read Game Archives after game files are clean. Use Force Uninstall only for the patch-mismatch recovery situation described by the tool documentation, not as a routine first step.

6. Install REFramework for Lua scripts and in-game tools

REFramework is different from Fluffy. Fluffy is primarily a mod installer and manager; REFramework provides a runtime hook, scripting engine, and developer interface. Some Lua mods require REFramework even if they are packaged for Fluffy.

  1. Download a build supporting Resident Evil 2 from the project’s Releases page. Consult the project’s README if you need a newer development build.
  2. For a normal non-VR installation, extract only dinput8.dll from the correct build archive into the directory containing re2.exe. The official README specifies this single-file method.
  3. Start RE2. The REFramework interface should appear or be accessible with Insert (the default toggle key in its UI).
  4. Explore the interface without changing everything at once. REFramework includes optional camera and field-of-view features and a Lua script runner, but availability depends on the build and game state.
  5. If something fails, read the generated re2_framework_log.txt (when present) and consult the project’s troubleshooting documentation.

Uninstalling REFramework: Exit the game, then remove the dinput8.dll you placed there and any script you installed. Do not delete unrelated files. If another mod also uses a dinput8.dll hook, follow both projects’ compatibility instructions rather than overwriting DLLs at random.

7. Make your first real mod: a Lua information panel

This tutorial produces a working read-only in-game panel. It is intentionally harmless: it changes no health values, save files, enemy behavior, or game assets. Once it works, you know your Lua loading path and REFramework API setup are correct.

Step A — Create the mod folders

Make this folder tree in a separate workspace: 

BeginnerInfoPanel/
├── modinfo.ini
└── reframework/
    └── autorun/
        └── beginner_info_panel.lua

Step B — Add the Lua script

Create beginner_info_panel.lua with Notepad, VS Code, or another plain-text editor. Do not let Windows save it as .lua.txt. 

-- BeginnerInfoPanel: a small read-only REFramework mod.
-- The callback runs when Script Generated UI is visible.
local show_message = true
local clicks = 0

re.on_draw_ui(function()
    imgui.text("Resident Evil 2 Remake - My First Lua Mod")
    imgui.text("This panel is loaded by REFramework.")

    local changed, value = imgui.checkbox("Show beginner tip", show_message)
    if changed then
        show_message = value
    end

    if show_message then
        imgui.text("Tip: Enable and test only one asset mod at a time.")
    end

    if imgui.button("Count a test click") then
        clicks = clicks + 1
    end

    imgui.text("Test clicks: " .. tostring(clicks))
end)

What the code does:

  • re.on_draw_ui(...) registers a function for REFramework’s generated script UI.
  • imgui.text(...) displays labels without modifying game state.
  • imgui.checkbox(...) returns whether the checkbox changed and its updated value.
  • imgui.button(...) responds to a click; clicks is a temporary in-memory counter that resets when the script reloads.

This uses documented REFramework callbacks and ImGui functions; it does not depend on guessed RE2-specific game object names.

Step C — Add optional mod metadata

Create modinfo.ini as a plain-text file: 

[Mod Info]
name = Beginner Info Panel
version = 1.0.0
author = ExampleModder
description = A harmless Lua panel for learning REFramework.

[Options]
category = Scripts

The metadata helps organize the mod in managers that understand the standard structure. It is not itself the Lua code, and modinfo.ini is not a requirement for REFramework to run an autorun script.

Step D — Test manually before packaging

For the quickest test, copy only beginner_info_panel.lua to: 

<RE2 game folder>\reframework\autorun\beginner_info_panel.lua

If the folders do not exist, create them. Start RE2, open REFramework with Insert, expand Script Generated UI, and locate the script’s controls. Click the button and watch the counter increase. If the panel does not show, check that REFramework loaded, the file ends in .lua, and the script is in the autorun directory. The script may also be reloaded from REFramework’s script facilities depending on your installed version.

Important: An autorun script displays these ImGui controls inside the REFramework menu. It does not automatically draw permanent text in the game’s main HUD.

Step E — Distribute it as a Fluffy-compatible archive

After the manual test, remove the manually copied Lua file to avoid duplicate loading. Place the modinfo.ini and reframework folder at the root of a ZIP, named something like BeginnerInfoPanel-v1.0.0.zip. An inspection of the ZIP should show modinfo.ini and reframework/ immediately, not additional accidental nesting. Import it into Fluffy and enable it. REFramework remains a separate requirement.

The accompanying downloadable starter ZIP for this guide contains these two small example files only; it contains no game assets, third-party DLLs, or executables.

8. Understand RE Engine files before editing anything

File or folder Plain-English explanation Beginner advice
re_chunk_000.pak and patch PAKs Archives containing game assets Extract copies; do not edit them directly
natives/x64/ Common replacement root for the original RE2 build Match the extracted file path exactly
natives/STM/ Common replacement root for the updated build Check compatibility before using an older mod
.tex.* An RE Engine texture with a versioned suffix Preserve the original suffix after conversion
.dds / .tga / .png Editable intermediary image formats These do not replace a .tex.* in-game by themselves
.mesh.* Mesh, skeleton-related data and geometry Import/export with a supported RE Engine tool
.mdf2.* or related material files Material properties and texture references Changing a mesh alone might not update the material
.chain.* Physics chains for hair, clothing and similar parts Keep the correct original rig and chain mapping
.pfb.* Prefab data linking game objects and components Advanced; do not edit blindly
reframework/autorun/*.lua Lua scripts loaded by REFramework A safe first programming project

Pay attention to patch archives. If a texture appears in both a base PAK and a later patch PAK, the later game version can contain the asset actually in use. Extracting an outdated copy and assuming it is current is a common reason for black screens or broken replacements. Keep your extracted assets in an external workspace, not mixed into the live game folder.

9. Extract the original game assets using RETool

You only need extraction when creating a texture or model mod; it is not needed for installing a normal downloaded Fluffy mod.

  1. Download RETool from FluffyQuack, and extract it to a work directory such as D:\GameModding\RETool\.
  2. Download a matching filename list from Ekey’s REE.PAK.Tool repository. In that repository, check the appropriate game’s list files; lists must match the game/build closely enough to resolve useful names.
  3. Find RETool’s provided extract-pak.bat. Open it in a text editor and change the referenced .list filename to the file you downloaded. Preserve the rest of the shipped command unless you understand its options.
  4. Make sure there is enough free disk space. Archives can expand into many thousands of files.
  5. Drag a copy of the PAK file—or use the original as read-only input—onto extract-pak.bat. Allow extraction to finish before opening its output folder.
  6. Repeat for relevant newer patch archives. When the same logical path exists in multiple archives, use the compatible, up-to-date version as your editing source.
  7. Find a suitable texture or model. Copy just the files relevant to your project into a separate mod workspace.

The community’s Extracting Game Files guide includes the exact RETool batch-file workflow and explains that a -skipUnknowns option skips files whose names could not be resolved. You normally do not need to change that option for your first edit.

Alternative: The RE Asset Library can browse/extract RE Engine assets through Blender, subject to its documented compatibility requirements and archived-maintenance status.

10. Create a simple custom texture replacement

A texture is an excellent first asset mod because you can see a visual difference without altering animation rigs. Choose a nonessential, easily recognizable surface (such as a poster or clothing fabric) rather than a complex face, normal map, or packed material mask.

Stage 1 — Find and inspect the original texture

Use the extracted files to locate the texture. Record its complete path, exact filename, and suffix. For example, an original-build file might be in a structure such as: 

natives/x64/sectionroot/.../YOUR_TEXTURE_NAME.tex.10

This is a structure example, not an existing RE2 asset that you can paste and load. Replace the placeholder with the real path you extracted. Newer versions may use natives/STM/ and different suffixes. Never invent the missing path from memory.

Open the texture with Noesis and its RE MESH plugin, or use a compatible texture workflow provided by RE Mesh Editor. Export to DDS or TGA while preserving all required channels.

Stage 2 — Make a controlled edit

  1. Open the exported image in an editor with the appropriate DDS/TGA support.
  2. Duplicate the original layer and save a separate project copy.
  3. Recolor a small but obvious area; do not resize the texture during your first test.
  4. Preserve the alpha channel and the original width, height, and channel semantics.
  5. Save a working editable copy, then export the required DDS/TGA version.

Why alpha matters: RE Engine often packs multiple material properties into different image channels. An ALBM texture can include albedo color in RGB and metalness information in alpha; other maps use the channels for different masks. Replacing all channels with a flat image can ruin reflections, transparency or roughness. See the community’s texture format and channel guide.

Stage 3 — Convert back to the game’s native texture format

A .dds is not automatically a .tex.* file. Use the RE Mesh Editor texture conversion tools (with the active game/build set correctly) or Noesis’ documented export-over-original method to convert the edited file to a versioned RE Engine .tex format. When the tool asks for an original reference texture, select your unmodified extracted original, not a random texture of the same dimensions.

Check the converted file’s suffix, dimensions, mipmaps and compression. A texture that renders black or purple can indicate a bad conversion or mismatched format, not merely a wrong install location.

Stage 4 — Package the replacement

Copy the converted, properly named RE Engine texture into a new mod folder while preserving the exact path below natives/: 

MyFirstTextureMod/
├── modinfo.ini
└── natives/
    └── x64/                 # use STM for a matching updated-build asset
        └── sectionroot/
            └── ...actual extracted subfolders.../
                └── YOUR_TEXTURE_NAME.tex.10

This tree is illustrative: the real path and extension must come from your extracted asset. Zip the mod so its root contains modinfo.ini and natives/, then import it into Fluffy Mod Manager. Disable competing texture mods, install this one, and verify the result in-game. Revert, adjust the texture, and repackage until it works.

Common error: Packaging MyFirstTextureMod/MyFirstTextureMod/natives/... with an extra folder may cause a manager to miss the replacement. Open the archive to confirm the actual layout.

11. Edit a model in Blender: a beginner-safe roadmap

Model replacement is more demanding than recoloring. The mesh may include multiple levels of detail, vertex groups, bones, material references and cloth/hair physics. Do not start by deleting a character’s skeleton or replacing the entire rig.

  1. Install a compatible Blender build. Follow the active RE Mesh Editor README for its minimum Blender version and current caveats. A conservative option is a supported Blender 4.5 LTS install rather than an untested major upgrade.
  2. Install RE Mesh Editor. Download the add-on ZIP from the repository’s instructed download method (not necessarily its Releases tab). In Blender, open Edit → Preferences → Add-ons → Install from Disk and install/enable the add-on.
  3. Choose the correct RE2 target. In the add-on’s settings, distinguish the original RE2 build from the updated/RT build. Keep the extracted source files and export target consistent.
  4. Import a small original mesh. Use an extracted prop or a documented example asset first. Import associated materials where available. Save a .blend project before changing anything.
  5. Make a tiny change. Move a small group of vertices or adjust a harmless prop shape. Avoid changing armature names, bone IDs, vertex group names, UV layouts or required LOD structure for your first experiment.
  6. Export the mesh in the correct game format. Read add-on validation messages and preserve the expected original asset name and version suffix.
  7. Keep materials and textures together. If you changed UVs or material bindings, export matching .mdf/.mdf2 and texture files as required. Do not assume one mesh file is the complete mod.
  8. Package with the original asset path. Install through Fluffy and test the correct object or costume slot in-game.

For real character swaps, read the step-by-step Custom Model Importing Guide before working with skeletal rigs and physics. The community guide covers model import/export, weight transfer, materials and associated assets in far more depth than a single starter example can safely reproduce.

12. Troubleshooting table: symptoms, causes, fixes

Problem Most likely causes Recommended fix
Mod appears enabled but nothing changes Wrong RT/Non-RT build, incorrect slot, wrong archive root Check the mod description and target costume; inspect natives/ path
Game crashes immediately after installing a mod Incompatible asset version, conflicting DLL or broken conversion Disable the last mod; remove only newly added hook files; test the clean game
Fluffy says PAK files changed after an update Steam patched an archive while manager had old cached state Follow manager recovery instructions; uninstall mods and re-read clean archives
Texture is black, white, strangely shiny or transparent Broken alpha/masks, wrong DDS compression, incorrect native TEX conversion Re-export from the original; verify channels, texture version and mipmaps
Mesh is invisible or distorted Wrong mesh suffix, missing materials, broken bone weights/LOD Check target build, export warnings, skeleton, MDF and texture paths
Two costume mods interfere Both replace the same asset Test separately or use patches designed for those specific mods
REFramework menu never appears dinput8.dll absent, wrong folder/build, hook conflict Confirm dinput8.dll is next to re2.exe; inspect README/log
Lua code has no visible effect Wrong autorun folder, .lua.txt file, Script Generated UI closed Check file extension, load path and REFramework UI; inspect script/log errors
Game behaves strangely after Steam verification Manager state no longer matches archive state Stop adding mods; restore a clean state and refresh manager archive information
FPS drops or streaming stutters after HD textures Very large texture replacements, missing mipmaps, forced high-res assets Re-enable original textures, reduce size and preserve appropriate mipmaps

For installation recovery, follow the community’s Installing Mods guide and Troubleshooting page. For script errors, check REFramework documentation.

13. Test your mods like a developer

Use a tiny release checklist for every change:

  • The game launches without the mod.
  • The game branch (DX11 Non-RT or updated) matches the mod.
  • Save files were backed up before testing.
  • The archive has the correct root folder structure.
  • The target asset or Script Generated UI actually displays the change.
  • The result survives a restart and a few minutes of normal gameplay.
  • Disabling the mod restores the original behavior.
  • Third-party requirements, credits and redistribution permissions are documented.

A useful folder structure for your own projects: 

D:\GameModding\RE2\
├── backups\
├── extracted-assets\
├── projects\
│   ├── beginner-info-panel\
│   └── my-first-texture\
├── exports\
└── release-zips\

Keep game assets, working files and release archives separate. Your ZIP should contain only the files necessary to reproduce the mod, not Blender backup files, personal save data, entire extracted PAK archives or copyrighted textures from other creators without permission.

14. Where to find mods, examples and deeper learning

Frequently asked questions

Can I mod Resident Evil 2 Remake without programming?

Yes. Installing a compatible existing mod through Fluffy Mod Manager is usually a graphical, no-code process. Editing textures requires an image editor; Lua scripting is optional.

Is Fluffy Mod Manager the same thing as REFramework?

No. Fluffy installs or manages compatible mod packages. REFramework loads a DLL hook, provides runtime tools, and can execute Lua scripts. Some mods need one, some need the other, and some need both.

Are old RE2 mods compatible with the ray-tracing update?

Not automatically. Always check whether the mod targets DX11/Non-RT or the updated branch. Changing x64 to STM does not, by itself, convert every internal file format. See the community conversion resources before attempting format migration.

Will mods work on consoles or Game Pass?

This is a Steam PC-focused guide. Console mod support and other PC storefronts differ in file layout, permissions and availability of runtime hooks. Do not apply Steam paths or DLL instructions to those platforms without a separate verified guide.

Will uninstalling a mod delete my save files?

Normally a well-behaved costume or texture mod should not touch saves, but gameplay scripts and save-related tools can change state. Back up your save folder first, and never treat a mod manager as your only backup.

Can I publish my own mod on Nexus Mods?

Yes, provided you comply with the game’s terms, the hosting site’s rules and asset permissions. Share your original changes and the required mod files. Do not upload another creator’s assets or complete Capcom game archives without permission. Explain the exact game build, installation method and dependency requirements.

What should I learn next?

Once the sample Lua panel and a single texture replacement both work, explore Blender’s RE Mesh Editor, material definitions, model rigs and REFramework’s object explorer. Progress in small, reversible steps.

Final thoughts

Resident Evil 2 Remake modding is much easier when you separate installation, runtime scripting, and asset authoring. Begin with a clean, backed-up game. Match the mod to the correct build. Install one change at a time. Then learn by creating an original Lua panel and a small texture replacement before attempting full character models or complex gameplay systems.

For most beginners, that method is more valuable than a folder full of untested mods: it teaches you how the files fit together, how to recover when something breaks, and how to build modifications that other players can actually install.

Editorial note: Tool repositories, file versions, Steam beta availability and mod requirements can change. The linked original project pages should be treated as the authoritative source for download instructions and compatibility. This tutorial does not distribute RE2 game content.

Leave a Reply

Your email address will not be published. Required fields are marked *