> For the complete documentation index, see [llms.txt](https://omori-modding.gitbook.io/wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omori-modding.gitbook.io/wiki/getting-started/decryption-and-playtest-generation/dev-tools.md).

# Dev Tools

A tool helpful for debugging mods

## **Disclaimer**

This guide assumes that you are already familiar with OMORI mod development, and that you know where some files need to go. You should also already know [how to fix your OMORI installation](/wiki/getting-started/decryption-and-playtest-generation/resetting-installation.md), in case you break it.

Furthermore, [some mods might not work in SDK mode.](#user-content-fn-1)[^1]

## **Installation**

To get [dev tools](https://flaviocopes.com/browser-dev-tools) in OMORI, which can be very helpful in debugging your mod, you need to do a few steps:

1. Download the SDK edition of the exact same NW\.js version that OMORI is using 
   * For OMORI v1.0.8 - [nwjs-sdk-v0.29.0-win-x64.zip](https://dl.nwjs.io/v0.29.0)
2. Drag all your files into the OMORI folder and choose replace / overwrite
3. Add this code to *www/js/main.js* to disable SDK mode protection:

   ```javascript
   window.navigator.plugins.namedItem = function() {
       return null;
   }
   ```
4. Rename OMORI.exe to something else, like OMORI\_old.exe, and rename the new file nw\.exe to OMORI.exe
5. Launch the game and press *F12* to open the dev tools.

[^1]: *For example,* [*Painful Bossrush*](https://mods.one/mod/painrush) *will check for SDK mode and stop working if detected.*