Documentation on Legacy WolvenKit can be found on the Legacy WolvenKit wiki at this link.

Now why would you want to do that? 💔

To completely delete WolvenKit portable delete your chosen installation folder, and the REDmodding folder in your users/appdata/roaming/ directory.

To delete the Installer version you can use Windows default Remove Programs or Features tool. You may then manually delete the users/appdata/roaming/REDmodding folder to remove your preferences as well.

Asset I/O

WolvenKit includes an all-purpose import and export tool for converting assets to game files and vice versa. Our tooling is bespoke allowing for native conversions with extensive options to suit your needs (check or find the list of ).

Base game and user-generated archives can be browsed on the fly, making game dumps obsolete. Our Asset Browser also features instant preview for assets such as meshes and textures.

What is WolvenKit?

Published May 24 2022

<summary paragraph>

Miscellaneous

Published Apr 06 2021

After a long and hectic development process, we are very excited to finally announce the public Beta release of Wolvenkit for Cyberpunk 2077. That's right everyone, Wolvenkit is no longer a myth! Though there have been many delays, we greatly appreciate the community and our patrons and contributors for sticking by us throughout the development process, and for the hard work by the many programmers, artists, and researchers that have made this whole project possible. So many incredible breakthroughs and discoveries have been made in Cyberpunk 2077 modding thus far, and we are excited to see what the community can do with the new capabilities that will be made available with the release of WolvenKit. Modders will now be able to browse game assets, browse, read, and edit most if not all file formats used by the game, manage projects, and more. As this is only the initial release, some features you may expect are still to come in future releases. By choosing to support us, you will be not only be enabling us to continue to develop Wolvenkit and add further functionality and tools for use by the community, but also gain access to exclusive posts and updates on the development process, as well as private community channels, voting power, behind-the-scenes content, and more. Even the smallest amount can help us to continue / spend more time on developing more tools.

WolvenKit has been completely refactored to migrate to a WPF solution from the Legacy WinForms build. Version 0.8.0.1 brings initial support for CDPR's latest video game Cyberpunk 2077. While we are planning to bring feature parity for Legacy WolvenKit versions, for now support for Witcher 3 projects is extremely limited. The initial feature set for the 0.8.x series focuses on the Asset Browser and Project Packing tool which enables us to efficiently rip assets and repack REDengine files into the archive format.

Mod Projects

• Initial implementation of the Project Explorer enables basic asset management for REDengine files added from Asset Browser.

• Initial implementation of the build pipeline. Files inside the Mod directory are packed into Cyberpunk format archive files. Optionally the user can choose to auto-install the packed archive file into their game folder.

UI/UX

• The WolvenKit UI has been completely rewritten from scratch to transfer the code base from WinForms to WPF.

WolvenKit 8.7

Published October 22 2022

WolvenKit 8.6

Published May 24 2022

WolvenKit 8.5

Published March 07 2022

WolvenKit 8.4

Published October 03 2021

Patches

WolvenKit 8.3

Published September 05 2021

Patches

WolvenKit 8.2

Published June 28 2021

Patches

WolvenKit 0.8.0.1

Published April 06 2021

Published Jun 28 2021

WolvenKit 0.8.2 brings massive improvements in key areas. Features such as the Asset Browser have been refactored to be more robust and efficient. This build also features the first scalable content pipeline for importing various assets. Be sure to thoroughly read the Release Notes and check the showcase video!

What is the Nightly?

The Nightly is . Releases are build every day when the code changes (traditionally during the night, but this is CyberPUNK), so you will always have access to the latest and hottest features.

Naturally, the Nightly will have more bugs than the stable version — but you should use it regardless, because we need help catching those bugs.

What is the Log?

The Log is WolvenKit's internal logging service to inform the user of what's happening under the hood. It also shows output from the feature, which will check file connections for you.

If something is not working as expected, take a peak into the Log to check for useful information.

Summary

Created by @JJTurtle Published October 22 2022

Updated Jul 30 2023 by

This guide is intended for the beginning modder, who is still learning, and wants step-by-step instructions on how to fully install and configure their modding tools and asset depot.

To keep things simple, the recommendations in this guide will centralize many of the modding applications, assets, and related resources.

Requirements

Prerequisites

1. Hard disk space for the Depot:

   • For regular operations, <5GB storage will be enough

   • If you want to extract materials and meshes, you should have at least 15GB storage

We goin' in?

First, install Wolvenkit:

Then, we'll start with :

Let's configure and set up Wolvenkit and all its plugins:

Then, we unbundle those game assets that we need…

Now we're goin' in.

We do that by creating a tiny mod to make sure everything worked OK.

Feel free to skip this step, or hit up the and get cracking.

What's a Home good for?

Welcome

When WolvenKit is launched the Home functions as bulletin board to help you pick up where you left off. Recent mod projects are displayed as a scrolling list of cards which can be directly clicked to get started. Other crucial functions for creating or opening projects are displayed in the right-hand column.

Mod Manager

Manage REDmod installations and deployment

Plugins

Download and update various and extensions for Cyberpunk 2077 modding

Settings

Settings can be accessed from the Home sidebar. Learn more about

Web Content

WolvenKit is capable of displaying web-based content natively. The Home page features several built-in web pages!

Wiki

This Wiki can be viewed from within WolvenKit. Hi WolvenKit users!

GitHub

GitHub can be used to directly track progress with WolvenKit development

Website

Take a peek at our very own website,

Summary

This page explains the main workspace within WolvenKit, the one holding the docking windows for the individual Editor panels.

Editor panels

For an explanation to the editor panels, please see the corresponding sub-pages:

• : Your local game files go here

• : Browse game files or mod files

• / File Preview: Information about the current file

Docking

The docking in WolvenKit is similar to other IDEs such as Visual Studio. All panels can be rearranged by docking to specific areas, or used as a standalone floating window.

Status Bar

The Status Bar along the bottom of the application window contains useful information, such as your WolvenKit version number and the current mod project, and provide the ability to install new updates if available.

Summary

Created: Dec 03 2024 by Last documented update: Dec 03 2024 by

This page describes Wolvenkit's Editor Difficulty Mode.

Where to change it

To change the default, head to Wolvenkit's

To switch it in-editor, use the dropdown in the upper left corner of the .app

Easy

Recommended for beginners. Many properties that you won't want to edit are hidden, other properties that you shouldn't edit are write-protected.

Default

Should show all properties that you realistically want to edit for regular use cases. Autogenerated properties are write-protected, irrelevant properties (e.g. platform) is hidden.

Advanced

The authentic editing experience from <= 8.14. Rawdogging CR2W without protection. Use at own risk.

What is the Tweak Browser?

Based on Wkit v. 8.11.0

The Tweak Browser lets you to search for various elements. For instance, you can utilize the TweakDB Editor ⇗ in CET to locate a weapon record ⇗, then use the identified name to search for the entry in the Tweak Browser in WolvenKit. Once found, you can right-click on the tweak and select 'Add TweakXL Override', once done that you'll create a .yaml file with the tweak array structure.

What is the LocKey Browser?

Based on Wkit v. 8.11.0

LocKey is a localization key designed to identify localized text strings. These keys, such as 'vehicle_enter' (which is not only user-friendly but also has a unique ID used typically), are employed throughout the game. Prior to display, these keys undergo localization to match the language setting of your game.

The LocKey browser allows to search for a specific localized text and reveals the corresponding LocKey (numbers) that, when localized, contains the desired text (string).

You can toggle the script manager via Tools -> Script Manager.

It looks like this:

Adding scripts

Enter a name in the box at the bottom of the panel and click the "Add" button. That will create a new script file in your .

Tabs

General

Contains a selection of runnable scripts for various workflows, e.g.

• Export_Vehicle_Ent when

• Export_Ent for characters (see )

• export_streamingsectors for

Hook

This section contains the settings for

UI

This section lets you add your own UI items.

Audio

Voice-overs & music

Voice-overs and most music are stored as .wem files – you can use the to filter by extension.

When you select an audio file in your Project Explorer or the Asset Browser, the File Information widget will turn into an audio player:

Sound effects

You can import and export sound effects stored in .opuspak files using the Import and Export tools respectively. See this page for a walk-through:

Video

In the past, Wolvenkit used to be able to view videos. However, due to license issues, we had since to remove the plugin.

However, it was only a wrapper around RADTools, which you can also install as external tool.

Converting files to JSON will serialize their content to a .json file in your project's raw folder.

Importing them back will re-create the corresponding file under archive.

This is easiest way to and a perquisite for several modding workflows.

Export as JSON

This option is in the right-click menu:

Import as JSON

This option is in the right-click menu:

Published Oct 03 2021

WolvenKit 8.4 brings major quality-of-life improvements in a relatively small package. Additions to file I/O, browsing user-generated mods, and new options for editing W2RC files can dramatically streamline some modding workflows.

Summary

Created: Jun 17 2024 by Last documented update: Jun 17 2024 by

As of 8.13, Wolvenkit supports the . This means that you don't have to do anything besides configuring your — dependencies will be handled as needed.

What is the depot?

The depot is the folder where Wolvenkit stores anything it needs to export your project files. As of version 8.13, it can handle everything by itself, and you don't need a depot unless you want to browse game data outside of Wolvenkit.

MultilayerMask

You can export and import MultilayerMasks via Wolvenkit.

Created: Dec 03 2024 by Last documented update: Dec 03 2024 by

This page will tell you about keyboard shortcuts and nifty tricks that make working with Wolvenkit easier.

Project Browser

The context menu in the project browser reacts to Shift

You edit the settings for Wolvenkit.CLI by editing appsettings.json in a text editor.

Runnning Wolvenkit.CLI settings will open that for you.

Property Documentation

Summary

Published: Sep 29 by (credit to for spelling out we needed this) Last documented edit: Sep 29 by

This is the Cool Stuff page — a list of things that you had no idea Wolvenkit could do for you.

How do I use the Blender integration features?

The following formats are supported by WolvenKit for imports and exports

• mesh ↔ glb/glTF Rigged and static 3d models can be converted to and from REDengine. For a detailed guide, see . Our I/O supports simple non-targeted skinned meshes for extreme efficiency. Advanced methods support multi-mesh, multi-rig, and material embedded meshes. Meshes with embedded morph targets are automatically included as shapekeys. WolvenKit can also export to virtually any 3d format (non-natively) through the built-in renderer Ab3d. You can read more \

Exporting

1. Extract the textures with uncook -p into a folder of your choice. TGA is recommended for CLI version 1.5.1 (latest).

The majority of communication about WolvenKit happens on our Discord server. Use the following link to join our modding community.

If you want to follow development, look for help with our tools, or contribute, Discord is the place to be. For help with WolvenKit directly, look for the #wolvenkit-support channel.

Published October 22 2022

WolvenKit 8.7 is a major step forward. New features include support for building REDmods, sound modding, and animation modding. The UI has been fully transitioned to a title menu and toolbar setup. Texture I/O is significantly more powerful and robust. Numerous fixes for bugs, issues, and pain-points have been implemented. Check out the full release notes below.

New Features

• Support for Cyberpunk 2077 game version 1.6 Upgrading to WolvenKit 8.7 is mandatory for game version 1.6 and beyond. WolvenKit should handle new game releases more gracefully in the future.

• Support for REDmod

  • Added options for Building and Deploying REDmods

Changes & Improvements

• Texture I/O has been completely refactored Expect improved performance and versatility for users

• Import/Export arguments are now saved When adjusting advanced import options adjustments are saved per-file. For example if the XBM export format for a specific texture is changed from PNG to TGA, the specific XBM will default to TGA for subsequent exports. This behavior is persistent between WolvenKit sessions.

Fixes

• Fixed crash due to game version 1.6

• Fixed absurd UI layout on first launch by including a default layout

• Fixed raw textures not displaying or showing incorrectly within Preview window

As of version 8.11.1, Wolvenkit offers the following plugins:

Cyber Engine Tweaks

One of Cyberpunk's core mods (wiki | Nexus page). Will install the latest version for you.

Documentation about using and developing with CET can be found in the wiki.

Redscript

Another of Cyberpunk's core mods ( wiki | ). Will install the latest version for you.

Documentation about development with redscript can be found in the wiki.

MLSetup Builder

Written and developed by Neurolinked (): A tool for Cyberpunk-specific "texture" editing.

Documentation can be found on under

Wolvenkit Resources

This plugin is necessary to use the 's context menu functionality of "find used files" and "find files using this". It provides the information that Wolvenkit needs to connect those files.

RedMod

CDPR's official interface for modding.

Check the yellow wiki for documentation:

Red4Ext

One of Cyberpunk's core mods (). This will install the latest version for you.

It is necessary as a requirement for e.g. ArchiveXL and TweakXL.

TweakXL

One of Cyberpunk's core mods (). This will install the latest version for you.

For documentation, check ->

RedHotTools

Will install the Wolvenkit plugin of for you.

For install and usage documentation, check ->

What is the Properties viewer?

The Properties Viewer is used to provide extra information about selected files from within the Asset Browser or the Project Explorer. The Properties Viewer can also generate instant previews for REDengine texture and mesh files.

Using the Properties viewer

Mesh Preview

Mesh files can be previewed by selecting them within the Asset Browser or Project Explorer.

Controls

• Hold and drag Left Mouse Button to rotate the mesh

• Hold and drag Right Mouse Button or use Mouse Scroll to zoom

• Hold and drag Middle Mouse Button to pan

Image Preview

Image files can be previewed by selecting them within the Asset Browser or Project Explorer. The image previewer is capable cropping, flipping, and markup. While the markups will not get saved to original file, they can be exported by using the save button.

Audio Preview

Audio files can be previewed by selecting them within the Asset Browser or Project Explorer.

Video Preview

Double click BK2 files in the Project Explorer or right-click them in the Asset Browser

Space to play / pause Esc = End video Use the bottom bar to scrub through the video.

Summary

This page contains information on the general use of Wolvenkit's command line interface. For more specific information, please see the corresponding sub-pages:

• Settings

Help

• Display general help/list all commands: --help

• Display help for a specific command: archive -h

Using WolvenKit Console globally

You can now install and update the Wolvenkit Command Line Tools (wolvenkit.cli) as a dotnet global tool. The console can be used anywhere directly from the command line, with no custom installation, and easy update.

Open command prompt/powershell and type in:

dotnet tool install -g wolvenkit.cli

WolvenKit Console can now be run from anywhere using CMD/Powershell:

wolvenkit.cli uncook -p "D:\SteamLibrary\steamapps\common\Cyberpunk 2077\archive\pc\content\basegame_1_engine.archive"

For updates to WolvenKit console, open CMD/Powershell and type:

dotnet tool update --global wolvenkit.cli

Video Guide for launching CLI

Processing files in bulk

To process multiple .archive files (for e.g. extracting duplicate textures), write yourself a batch file:

Unlike music and voice-overs, sound effects in Cyberpunk 2077 are stored inside .opuspak files, which are described by a single sfx_container.opusinfo file.

Exporting sound effects

In order to export sound effects, you need to have the sfx_container.opusinfo file in your project. Find it in the and .

With the opusinfo selected in the Export tool (if you don't see the file, press Refresh), you should now see the export options on the right.

The important field for us here is "Selected for Export". Click the three dots on the right to open a selection window where you can choose which hashes to export. Click the hash you want and press the arrow button pointing right to add it to selection.

Once you've selected what you want, press Finish to confirm the selection and back in the Export tool press "Export Selected". The sounds you've chosen should now be in the raw folder of your project. You will find two files for each of the sounds, one is origin .opus and the other is .wav. You can usually ignore the .opus file.

Importing sound effects

To import back a sound effect, all you need is the sound file in .wav format with the exact same filename it had when you exported it. It should also be in the same folder (raw).

You can usually leave the default settings as they are. After pressing "Import selected", your project's archive folder should now contain a new modified sfx_container.opusinfo and one or more sfx_container_XXX.opuspak (XXX being a number). The opuspak contains your new sound (and other sounds too).

Depot Generator

Tool for building a depot, a collection of extracted game assets to use them in other tools such as .

Sound Modding Tool

<info>

Script Manager

See for details

Import Tool

See for details

Export Tool

see for details

Hash Tool

<to be done>

Settings

Where can I submit feedback or bugs?

• Reach out on Discord! We have a dedicated channel for WolvenKit issues.

• Check out the page to view, track, and submit new issues.

What is the Asset Browser?

The Asset Browser is used to navigate, search and filter Cyberpunk 2077 game files so you can transfer these to the The Asset Browser eliminates the need for uncooking the entire game installation, as individual files can be pulled directly from archive files.

Wolvenkit is scriptable using javascript and its internal API. With it you can automate tasks such as exporting, as well as make changes to files programmatically.

Interested in contributing code?

Please do! Fork the project and please commit your changes in small incremental steps with descriptive messages. Code quality is not the biggest concern but refrain from simple mistakes. It's a good idea to create an issue when implementing a feature so people don't work on the same feature/issue in an asynchronous manner.

Archives

A comprehensive list of jargon you might see on this Wiki or around our community. This glossary is not alphabetical, so be sure to use your browser search function to find what you're looking for. (CTRL+F for most applications)

General

What can I do with WolvenKit?

The page provides a broad look at what's possible to achieve with WolvenKit.

What are long filepaths, and why do I need them?

This wiki focuses on workflows that are central to WolvenKit. You can find much more knowledge and documentation in the wiki, for example the Modding Guides section:

What is the WolvenKit Console?

WolvenKit Console is the core "Modkit" that drives the WolvenKit application. The Console supersedes the original CP77 Tools application created by rfuzzo. The same core functionalities of WolvenKit are available from command line for simplicity and extendibility for power users.

Published Mar 07 2022

WolvenKit 8.5 ushers in a new era for mod development. The File Editor now supports editing buffers for the .ent and .app formats. Buffer editing opens the doors to countless new possibilities for modders. Virtually all aspects of the UI have been streamlined and refreshed with quality-of-life improvements.

Known Issues

• Some TGA image previews may be incorrect All TGA's exported from WolvenKit will be previewed correctly within the Properties window. However TGA's exported from other applications with bottom left Origin will appear inverted. This is only an issue with the image preview tool with the TGA format. The texture will not be inverted when imported as an XBM.

Asset I/O

What's New

• MLMASK I/O has been streamlined The default format for mask I/O has been changed from DDS to PNG. Additionally mask textures are now placed into a subfolder using the original mlmask file name. When exporting .mlmask files WolvenKit will automatically generate a file within the raw directory. The content of the masklist is automatically generated for convenience. Masklist files now accept absolute and/or relative paths. For example: Absolute Path Q:\projects\Judy\files\source\raw\base\characters\main_npc\judy\textures\ml_s1_001_wa_shoe__judy_masksset.mlmask\0.png Relative Path ml_s1_001_wa_shoe__judy_masksset.mlmask\0.png

Texture I/O

• Default export format is now TGA After careful consideration the Import/Export tool will now export TGA by default. The flow chart below demonstrates the necessity of this change. DDS imports and exports remain unchanged in version 8.5.

• Keep is now disabled by default Starting with version 8.5 textures will no longer be rebuilt by default. Standalone textures that don't require an original XBM will be created instead. There are numerous benefits: - Texture resolution/size will be updated automatically on import - Standalone TGA imports work flawlessly - Checking DDS compression is not necessary - High quality 32bpp RGBA compression is always used The drawback is that standalone textures will not preserve the isGamma boolean. This boolean must be set true for all color texture imports.

• Support for isGamma Standalone texture imports now expose the isGamma boolean, meaning color textures can be correctly displayed as sRGB. The isGamma boolean is set to false by default, meaning the user should manually check the box for color textures. We plan to automate this process with an upcoming patch.

Development

Dependencies

• Upgraded to Visual Studio 2022 Visual Studio 2022 is now required to compile WolvenKit.

• Upgraded to .NET 6 The .NET dependency was upgraded from .NET 5 to .NET 6. Users can download .NET 6 from the following link:

File Editor

What's New

• Support for editing buffers Buffers can now be edited and saved with WolvenKit! Currently .app and .ent buffer editing is supported. All properties can be modified including floats, strings, and paths. This opens the doors to countless new modding possibilities.

• True native file editing WolvenKit is now capable of adding and removing elements of REDengine files within the document editor. Various options for adding or removing elements have been added.

• Improved file handling Numerous quality of life enhancements have been implemented: - An asterisk (*) is added to the file name tab when unsaved changes are present - A confirmation dialogue has been added for closing edited files without saving - A

Redesigned File View

• Tree View replaces List View The left-hand navigation panel now uses a beautiful and intuitive tree view. Tree view elements are organized in a sensible way, rather than a flat list.

• Collection Editor has been removed The Collection Editor introduced with version 8.4 has been removed. The right-hand properties panel now displays editable-content efficiently without a floating window.

• Default engine values are now displayed Properties that are not written to file display REDengine default values. These values are automatically inserted by the game at runtime when left unset. Inherited default values are marked with italic font and darkened text.

Fixes

Miscellaneous

• Fixed bugged mesh previews for new installations of WolvenKit

Mod Projects

• Packing and Installing have been separated into separate actions Pack Project - Compiles mod project without installing (New) Pack & Install - Compiles mod project and installs to Game Directory

• The tweak directory folder structure is preserved Any user-created folder structures for tweaks are preserved by the WolvenKit installation process. Tweaks and folders are installed exactly as they appear within the tweak project directory.

UI/UX

Project Explorer

• Added filtering to Project Explorer The Project Explorer can now be filtered by directory. SOURCE | All project directories (default) archive | Archive directory raw | Raw directory scripts | Script directory tweaks | Tweaks directory PACKED | Internal WolvenKit folder for mod deployment. Can be used to install extra files.

• Added flat file view to Project Explorer A flat file list toggle button has been added to the Project Explorer which displays all project files in a simple alphabetical list without folders.

Miscellaneous

• WolvenKit mod projects (.cpmodproj) can be opened directly Mod projects can now be opened natively from Windows Explorer. The WolvenKit installer will automatically assign mod projects to be opened with WolvenKit. For WolvenKit portable, double-click any .cpmodproj file from Windows Explorer, then locate wolvenkit.exe.

• Replaced Ribbon with menu bar (optional) Added a streamlined menu bar as an alternative to the Ribbon. Moved contextual actions to their respective editors.

• Streamlined Home view

Section Brief

Configure the WolvenKit (wkit) application and MlSetupBuilder (mlsb), and make sure the Asset Browser loads the game's assets.

Configuring Wolvenkit

If your Wolvenkit is already configured (because you have followed the ), then you don't need to do anything here.

Otherwise, please do that now or use the to configure Game Executable Path and (optionally) Depot Path.

Installing Plugins

1. In Wolvenkit, click on

2. Click on

3. REDMod should already be installed. If it isn't, please follow the instructions .

1. Now that all plugins are installed, you can configure (but read the blue box first). This step is optional; you don't need to do it at this time, but you won't be able to make full use of the plugin if it is not configured.

For detailed configuration instructions, head to -> ->

Testing

Let's make sure that your game path is configured correctly and that Wolvenkit can access the files:

1. Click on Continue to Editor
2. Open the Asset Browser

1. After several seconds, a success notification will appear and the asset folder structure will appear on the left. This means WolvenKit was able to access the Cyberpunk archive and extract the game assets.

Congratulations - everything is working! If you haven't done this during the full prep, now is a good time to . Otherwise, you can move on to !

What is the Project Explorer?

The Project Explorer is primarily a tool for organizing and navigating mod project files. The Project Explorer gives a constant tree view of all mod project files which streamlines the modding workflow significantly. There are four main WolvenKit directories inside the Project Explorer.

Project Explorer Tabs

You can switch between different tabs at the top of the project explorer (see the red arrow on the screenshot below). Their function (and content) will be explained in the next sections.

Archive

Only shows you files under your_wolvenkit_project/source/archive.

Contains files that will be bundled into your mod's .archive file. For more information, check the documentation under ->

Raw

Location: your_wolvenkit_project/source/raw.

Your (dirty?) working directory. Contains files that will not be part of your mod, as well as exported files. For more information, check the documentation under ->

Resources

Location: your_wolvenkit_project/source/resources

Contains control files for your mod. For more information, check the documentation under ->

Source

Location: your_wolvenkit_project/source

Will show you everything under your project's source folder. No context sorting.

Using the Project Explorer

WolvenKit features a bespoke which is capable of opening and modifying any REDengine file. Double-click any file within the archive directory of the Project Explorer to open the document viewer. Non-REDengine files which are typically stored in the raw directory can be accessed with the Project Explorer as well. Files such as blend, psd, png, and many more can be opened with the preferred system application. For example, double-clicking a .tga file will open the file with the users system preferred image application.

Any file within the Project Explorer can be moved by dragging and dropping. Additionally files can be copied by holding Control while dragging and dropping.

Context Menu

Right-click any file within the Project Explorer to explore the Context Menu.

Open in MLSetupBuilder

Requires MLSetupBuilder plugin for WolvenKit. Install by navigating to the Toolbar panel.

Export to JSON/Import to JSON

Writes any REDengine file within the archive directory to human readable JSON format, as a mirrored file within the raw directory. JSON files can then be modified and converted back to REDengine format from the context menu by right-clicking the JSON file.