DXT1 or DXT5 in the 6th row.pluto build.pluto within the warframe-cache-tools directory.content (managed) folder from warframe-cache-tools into the OpenWF folder of your client. The Bootstrapper will automatically patch the game to use your modified content, and if you ever wanna stop using it, you can simply remove the client's content (managed) folder.Content Replacements folder from warframe-cache-tools into the OpenWF folder of your client. The Bootstrapper will automatically patch the game to use your modified content, and if you ever wanna stop using it, you can simply remove the client's Content Replacements folder.While the main feature of the bootstrapper (dwmapi.dll, wtsapi32.dll, or version.dll) is to use a custom server with the game, it has other features as well.
-The bootstrapper's configuration is in OpenWF/client_config.json relative to your game folder. It has the following fields:
The bootstrapper's configuration is in OpenWF/Client Config.json relative to your game folder. It has the following fields:
fallback_language — If not empty, this language will be used when Warframe.x64.exe is invoked without a language command line argument.fallback_graphicsDriver — If not empty, this graphics driver will be used when Warframe.x64.exe is invoked without a graphicsDriver command line argument.USER message is adjusted to contain nonce=... in the 'realname' field.Metadata Patches are loaded from OpenWF/Metadata Patches.txt, although you can also create a OpenWF/Metadata Patches/ folder and any text file inside of that will be loaded as well.
Metadata Patches are loaded from text files in the OpenWF/Metadata Patches/ folder.
They are generally parsed line by line, with roughly the following steps being taken for each line:
/, a new patch for the given absolute path is started. If the line ends on &, the next line that also starts with / will be added to this patch instead of creating a new patch.