Client/Boostrapper Installation

To use OpenWF, you only need to download the dwmapi.dll and put it in your game's installation folder (the one where Warframe.x64.exe is in).

• As long as this DLL is in the game folder, you can double-click Warframe.x64.exe to start the game with OpenWF.
• Opening the game's launcher will revert it back to normal.

The DLL is fully documented here, but the most important point is that, while the game is running, you can visit http://localhost:61558/ to manage options, cheats, and scripts.

Next steps: By default, the DLL redirects requests to localhost — meaning the same machine you're playing on — so you'll either need to set up a server or change the server_host to point to a different machine that's already got a server running. You can use a public server if you don't need to be able to play offline and have full control.

Server Prerequisites

• Git (Download)
• Node.js (Download)
• MongoDB (Download)

Server Installation

1. Run git clone https://openwf.io/SpaceNinjaServer.git in a command prompt to download SpaceNinjaServer in the current working directory
2. Open the SpaceNinjaServer folder (cd SpaceNinjaServer)
3. Run copy config.json.example config.json to create a config.json from config.json.example
4. (Optional) Edit the config.json to match your MongoDB settings (if not default) and however else you would like to configure the server
5. (Optional) If you want stripped assets (~622 MiB) which the client will request from the server on-demand (most notably, ability videos), run git clone https://openwf.io/0.git in the static/data folder
6. Run npm i (or npm install) to install library dependencies
7. Now, to start the server, run npm run dev (if this is too slow on your machine, you can use npm run build followed by npm run start)

Server Update

1. Run git pull in the SpaceNinjaServer folder
   • You may see an error if you cloned SpaceNinjaServer from GitHub — to fix this, run git config remote.origin.url https://openwf.io/SpaceNinjaServer.git
2. (Optional) If you have the stripped assets, run git pull in the static/data/0 folder
3. Run npm i (or npm install) to synchronize library dependencies
4. Now to start the server again, run npm run dev (if this is too slow on your machine, you can use npm run build followed by npm run start)