Onimusha: Way of the Sword mods include camera tools, graphics controls, and optional combat assists on PC. Start with the feature you want, then install its required loader and files. REFramework scripts, Fluffy packages, and Vortex extensions use different installation steps, so placing every download in the same folder will not work.
This guide covers Windows PC installations and links to the actual mod download pages. Keep demo and full-game packages separate, and check compatibility again after a game update. For PC requirements and storefront details, use the Onimusha: Way of the Sword Steam guide.
Choose an Onimusha mod by its purpose
A framework supplies the environment that another mod needs, while a script supplies a particular change. A manager helps organize installation, but some packages still need an additional activation step. Use the table to choose a starting point before downloading several overlapping tools.
| Your goal | Starting download | Important condition |
|---|---|---|
| Adjust the camera or run Lua mods | REFramework | Install the build intended for this game |
| Change lighting and advanced graphics | Graphics Enhancement | Requires REFramework |
| Add optional combat assists | REFramework Cheat Menu | Includes a script and cursor plugin |
| Organize packages through Vortex | Onimusha Vortex Extension | Fluffy activation remains necessary for its packages |
| Run a mod specifically requiring DaMoWang's framework | Custom REFramework | Follow that mod's exact dependency |
Prepare the PC installation
Make a separate copy of your saves before experimenting with gameplay changes. Keep the downloaded archive and a short list of files you add, including their original locations. These precautions give you a way to reverse your own changes without guessing which files belong to the game.
- Launch the unmodified game and confirm that your usual save loads.
- Close the game completely before copying or replacing mod files.
- In Steam, right-click the game, choose Manage, then Browse local files.
- Confirm that the folder contains
OnimushaWotS.exebefore following instructions that say “game root.” - Check whether the download targets the demo or retail game and whether it names a required build.
- Add one mod, launch the game, and check its intended feature before adding another.
Keep your first check short and repeatable. Use the same save, location, display settings, and movement when comparing the game before and after installation. A menu opening successfully is useful, but you should also check the actual feature during normal play.
Install REFramework and Lua scripts
REFramework provides a Lua scripting environment alongside camera and display tools, including field-of-view, free-camera, and ultrawide controls. Its Onimusha download page uses Insert to open the overlay. The project's REFramework downloads and release notes distinguish stable releases from newer nightly builds.
- Download the appropriate Onimusha REFramework archive.
- For the normal non-VR installation, extract
dinput8.dllinto the game root. - Launch the game and press Insert to check the overlay.
- Close the game before adding a mod's
.luafile toreframework/autorun. - Put a required native plugin in
reframework/plugins, following the package instructions. - Relaunch and check the script's own controls; these can differ from the framework key.
REFramework normally creates the autorun directory when it loads, and scripts there load during initialization. Its manual also allows individual scripts to run through ScriptRunner → Run Script. If the framework cannot use the game directory, its Onimusha page documents %APPDATA%/REFramework as the fallback location for its files.
Do not replace a working loader merely because a second archive contains another copy. Compare the dependency instructions and version before accepting an overwrite. If the instructions require a different build, save your existing setup so you can restore it as a complete combination.
Custom REFramework compatibility
DaMoWang's custom framework page identifies Steam retail Build 24769601 as its verified baseline. It supplies the runtime required by that author's dependent mods and adds no standalone gameplay feature. That statement does not establish compatibility with every later patch or with the demo.
The package offers an installer and a manual method that places its dinput8.dll beside OnimushaWotS.exe. Its removal instructions preserve the loader while other dependent mods remain. Treat the standard and custom downloads as alternative dependency choices, and follow the mod you actually intend to use.
Graphics Enhancement installation and tradeoffs
Graphics Enhancement exposes RTGI, RTAO, and additional shadow, reflection, and screen-space controls through REFramework. Install its Onimusha_WotS_Graphics_Enhancement.lua file in reframework/autorun, then look in the overlay's Script Generated tab. Its ray-tracing controls require ray tracing to be enabled in the game settings.
Higher shadow settings can use more VRAM, and disabling level of detail has a performance cost. Stronger denoising can soften detail, while temporal effects can produce ghosting during movement. RTGI can also darken enclosed areas; the Ambient Boost control does not guarantee that every scene will look right.
Try one graphics change at a time, especially if you are already close to your preferred frame rate. Check a dark interior as well as an outdoor scene, and move the camera instead of judging only a still image. The Onimusha RE Engine and PC graphics guide provides the broader technical context for graphics settings.
Combat assists and appearance changes
The Cheat Menu offers optional resource cheats, Issen assistance, automatic soul absorption, and appearance swaps. Its default menu key is tilde (~), and its toggles begin disabled. This is a separate control from REFramework's Insert overlay.
- If you have not installed REFramework, complete the framework installation above first. If REFramework is already installed, keep the existing loader as instructed by the menu package.
- Copy
onimusha_qol.luaintoreframework/autorun. - Copy
ref_cursor.dllintoreframework/plugins; the menu requires it for cursor use. - Launch, press tilde, and enable only the option you intend to try.
Easier Issen still requires your input, while Always Deflect still requires holding block. Appearance swaps change the visible mesh without writing an unlock to the save, and their selection is not saved. DLC appearances require the corresponding DLC to be owned and installed.
Choose whether you want help with a specific action or a broader change to combat before enabling several assists. Check the Onimusha difficulty settings guide if the built-in options may already suit your needs. For ordinary progression rewards, use the post-game unlocks guide rather than treating a temporary appearance swap as a permanent unlock.
Vortex and Fluffy installation steps
The Onimusha Vortex Extension installs Fluffy Mod Manager and REFramework as supporting tools. Its description lists Steam, Epic, and Steam Demo support, but an individual mod still needs to match your game version. Loose Lua scripts go directly to autorun; Fluffy packages need to be enabled through Fluffy after deployment.
- Install the extension through Vortex and select the correct game installation.
- Install your chosen package using its instructions.
- Deploy it in Vortex.
- For a Fluffy package, use the notification or Dashboard tool to launch Fluffy.
- Enable the mod in Fluffy, then start the game and check the result.
Vortex deployment alone therefore does not complete every installation. For packages such as upscalers or ReShade files, the extension describes a separate Binaries / Root Folder type and staging-folder extraction. Apply that route only when it matches the package instructions, rather than changing every mod to the root-folder type.
Diagnose a missing mod or crash
Start with the last change you made and preserve any error message before altering the setup again. Record the game build, framework version, mod version, and the action that triggered the failure. Those details make a useful comparison when a combination worked before an update but fails afterward.
| Symptom | First check |
|---|---|
| No framework overlay | Confirm the correct game folder and loader build |
| Overlay opens but script is absent | Check the autorun location and accidental nested folders |
| Cheat Menu cursor fails | Check the required cursor plugin |
| Vortex package has no visible effect | Confirm its Fluffy activation step |
| New graphics settings look worse | Restore the last setting and compare the same scene |
| Crash began after adding several mods | Return to the last working setup, then add them individually |
REFramework's troubleshooting documentation requests the complete re2_framework_log.txt and, for crashes, reframework_crash.dmp when present. Script startup errors can appear in a message box, while newer nightly builds can show callback errors in ScriptRunner. Preserve those details before cleaning up files so the failure can be investigated.
Remove mods without deleting shared files
Close the game and remove the individual mod through the method used to install it. For manual files, use your installation list and original archive to identify what you added. Keep shared components if another installed mod still requires them.
For Graphics Enhancement, remove its installed Lua script, its Onimusha_WotS_Graphics_Enhancement.json data file, and its profile folder if present. Match the actual installed filename because the download page uses different spacing in its installation and removal text. Keep a copy of settings you may want to reuse before deleting them.
Removing dinput8.dll temporarily disables REFramework from the game folder. A complete framework cleanup also removes its directory, configuration, logs, and crash dump, which can affect every mod using that installation. Reserve that broader cleanup for removing the entire framework setup, then launch the game again to confirm normal behavior.