EDGEQUEST / DOCS

Getting started

EDGEquest is the EDGE quest maker for Cyberpunk 2077, a VS Code extension. You read the game’s quests in plain words, and you write your own as a story: EDGEquest makes the game’s quest files from it. This page takes you from installing it to playing your first quest.

What you need

What Why
Windows 10 or 11, 64-bit, and Cyberpunk 2077 2.5 The game EDGEquest reads and writes for
VS Code 1.70 or later (or VSCodium, or EDGEkit) EDGEquest is an extension for it
REDcode for Cyberpunk 2077 Finds the game, installs REDbridge (0.11.0 or later) and the .NET 10 runtime, makes the WolvenKit project, and packs and installs your quest
ArchiveXL in the game Adds your quest’s phase, journal and texts to the game
Optional: EDGEwave Finds, plays and makes sounds for your quest
Optional: REDnode Plays music cues in the running game, so you can hear them from the picker

Install

  1. Install REDcode, and let it find the game and download REDbridge.
  2. Install EDGEquest: in VS Code’s Extensions view (Ctrl+Shift+X), search for EDGEquest and click Install. Or download it from Nexus Mods, extract it, and in the Extensions view choose …, Install from VSIX… and pick the .vsix.
  3. Click the EDGEquest icon in the activity bar. The first time, EDGEquest builds its quest index from your game in the background (about a minute and a half; the status bar shows it), and again when the game updates.

EDGEquest uses REDcode’s game folder and REDbridge. When REDcode is not running, it finds them itself (settings edgequest.gamePath, edgequest.bridgePath).

Read a game quest

Reading a quest you know is the quickest way to learn how the game builds quests, and where its places, music cues and facts are.

Write your first quest

  1. In REDcode, make a WolvenKit project (REDcode: New Project), or open one.
  2. Run EDGEquest: New Quest…. Give a title and an id (lower case, such as door_mystery), and the first time, your modder name.
  3. EDGEquest writes door_mystery.quest.yaml at the top of the project from its template, opens it on the Storyboard, and makes the quest’s game files.

The template already plays: its objective sends V to the apartment door in Megabuilding H10, and when V gets there a short scene plays with a choice that leads to one of two endings.

On the Storyboard, each card is a beat, titled with its journal objective. Arrows show where each choice leads. Click a card for its page:

Every change goes into the story file. Open YAML shows the text, which you can edit directly. The story file describes everything it can hold.

Saving makes the quest (or EDGEquest: Make Quest). Problems show in the Problems panel at their line. While a story file is in front, the status bar says when it was last made and what is left on its checklist.

Play it

  1. In REDcode, Pack and Install the project.
  2. Start the game and load a save from before you installed the quest.
  3. The quest’s objective shows in the journal. Follow its marker.

To change it, edit the story, save, pack and install again, and load the save again. If something does not work, EDGEquest: Check Quest Mod… on the project names what is wrong, and EDGEquest: Show Log shows what EDGEquest did.

Good to know

For assistants

edgequest-mcp gives AI assistants such as Claude Code the same quest maker. With Claude Code:

claude mcp add edgequest -- npx -y @edgemodders/edgequest-mcp

Then ask it, for example, to start a side quest where V finds something odd at the apartment door. It writes the story file, makes the quest, and works through the checklist; you watch the Storyboard change.