This tutorial is for Next-Gen. If you mod 1.32, follow this guide instead.

What WKit can be used for, that RedKit can’t:

If you need anything described above, get WKit and follow this tutorial. If nothing sounds particularly interesting - skip that step entirely. You can always return to get WKit a bit later.

1. Next-Gen + WKit setup

I strongly recommend you use RedKit as your base editor and only occasionally work with WolvenKit.

In that case, there would be no need for you to uncook game files for WolvenKit separately, as you could use Next-Gen depot generated by RedKit - you will only have to setup the WKit itself.

It also means that you won’t be using WolvenKit for the full pipeline - but it can still be used for cooking new and uncooking existing mods, exporting textures, and importing new stuff.

2. Installing prerequisites:

  1. Download and install ModKit 1.3 (yes, for Next-Gen too)
  2. Follow its regular Installation rules (yes, for Next-Gen too)
  3. (optional) run installation of a collection of legacy VC redistributables

3.1 Installing WolvenKit using RedKit’s depot:

  1. Download WolvenKit 7.2 for Next-Gen
  2. Install WolvenKit to a short path, following same rules as for installing ModKit
  3. Run WolvenKit & follow instructions it gives you
  4. When prompted to select “wcc_lite.exe”, use your ModKit’s modkit/bin/wcc_lite.exe path
  5. When prompted to select “Uncooked Depot Path”, change it to use your RedKit’s generated depot (r4data)
  6. When prompted to update your wcc_lite (ModKit’s main executable), agree to it

3.2 Installing WolvenKit using custom/no depot:

  1. Download WolvenKit 7.2 for Next-Gen
  2. Install WolvenKit to a short path, following same rules as for installing ModKit
  3. Run WolvenKit & follow instructions it gives you
  4. When prompted to select “wcc_lite.exe”, use your ModKit’s modkit/bin/wcc_lite.exe path
  5. When prompted to select “Uncooked Depot Path”, keep it as is (points to ModKit/r4data by default).
  6. When prompted to update your wcc_lite (ModKit’s main executable), agree to it
  7. If you only plan to use WKit sparingly for messing with existing mods, you should be good using no Depot. In that case, move on.
  8. If you plan to make edits from scratch, using actual game files, move to WolvenKit - Generating Depot

4. On Combining Next-Gen WolvenKit + RedKit

  1. If you already have a next-gen Depot prepared by your RedKit, you will be able to use it as a depot for WolvenKit as well. There is no need to create a separate “WolvenKit depot” to use it.
    1. not all WKit functions are working this way (for example, mesh export to FBX is much less stable in Next-Gen WKit than in RedKit or 1.32 WKit)
    2. you can still create new and unpack existing mods with WKit
    3. you can still make and save your edits to C2RW files (like W2ENT etc) → note that WKit doesn’t have complete UI for all types of them
    4. you can use both RedKit and WKit to edit the same file
    5. you can NOT use the same project for both RedKit and WKit as their project structure is a bit different
    6. you can transfer projects in between RedKit and WKit with relative ease