Skyrim Start Quest Command: The Complete 2026 Guide to Launching Any Quest Instantly

Anyone who’s spent hundreds of hours in Skyrim knows the frustration: a quest won’t trigger, an NPC won’t talk, or worse, a crucial questline breaks midway through. Maybe a player wants to skip the intro for the twentieth playthrough, or test a mod that affects a specific quest. That’s where the start quest command becomes essential. This console command lets players launch any quest in the game manually, bypassing triggers, fixing broken chains, or simply experimenting with content they’d otherwise miss. It’s one of the most powerful tools in a modder’s or power user’s arsenal, but it requires precision. One wrong character in a quest ID, and nothing happens. This guide covers everything from basic syntax to advanced troubleshooting, complete with the most commonly needed quest IDs and platform-specific instructions for the 2026 edition of Skyrim Special Edition and Anniversary Edition.

What Is the Start Quest Command in Skyrim?

The StartQuest command is a console function that manually initiates any quest in Skyrim, regardless of whether the player has met the normal trigger conditions. It bypasses dialogue requirements, location triggers, level gates, and prerequisite quests.

In practical terms, this means a player can start “The Way of the Voice” without ever talking to the Jarl of Whiterun, launch a Daedric quest without finding the shrine, or activate DLC content immediately after leaving Helgen. The command doesn’t complete quests, it simply adds them to the journal and sets the first objective as active.

This tool is invaluable for several scenarios: fixing quests that won’t start due to bugs, testing mod compatibility, creating alternate playthroughs with custom quest orders, or accessing content that might otherwise be locked behind broken scripts. Bethesda designed the console with modders and troubleshooters in mind, and StartQuest is one of the most frequently used commands for both.

The command works across all PC versions of Skyrim, including the original 2011 release, Special Edition, and Anniversary Edition. Console players on Xbox and PlayStation gained limited access through mods, but the functionality differs significantly from the native PC implementation.

How to Open the Console Command Window

PC Console Access

On PC, opening the console is straightforward. Press the tilde key (~), located directly below the Escape key on most US keyboards. On UK and European keyboards, this might be the grave accent key (`) or a different key depending on layout.

When the console opens successfully, the game pauses and a dark translucent overlay appears at the bottom of the screen with a blinking cursor. Players can now type commands directly. The interface shows a history of previously entered commands that can be scrolled through using the Page Up and Page Down keys.

Some keyboard layouts require different keys. German keyboards often use the ^ key, while French layouts might use ². If the tilde key doesn’t work, check the game’s key binding settings or search for keyboard-specific solutions for Skyrim Special Edition.

The console remains open until the player presses the tilde key again. Any command entered takes effect immediately upon pressing Enter, and the results appear either in the console output or directly in the game world.

Console Commands on Xbox and PlayStation

Native console access doesn’t exist on Xbox Series X

|

S, Xbox One, PlayStation 5, or PlayStation 4. Bethesda locked down console commands on these platforms to prevent achievement exploits and maintain platform stability.

But, mods like Cheat Room (available on Bethesda.net) provide limited quest manipulation on consoles. These mods offer menu-driven interfaces that replicate some console command functionality, though they’re far less precise than typing commands directly. Players won’t get access to the full range of quest IDs or advanced commands like SetStage, but basic quest starting is possible for major questlines.

Nintendo Switch has no console access and no mod support that enables command functionality. Switch players are limited to vanilla gameplay with no command-based workarounds.

The Basic Syntax: StartQuest [QuestID]

Understanding Quest IDs

Every quest in Skyrim has a unique identifier called a Quest ID or Editor ID. These IDs are alphanumeric strings that reference specific quest records in the game’s data files. For example, the main quest “Bleak Falls Barrow” uses the ID MQ103, while the Dark Brotherhood’s “Sanctuary” quest uses DB02.

The basic command structure is simple:

StartQuest [QuestID]

For instance, to start the Thieves Guild questline, players would type:

StartQuest TG00

The command is not case-sensitive, so startquest tg00 works identically to StartQuest TG00. But, the Quest ID itself must be typed exactly as it appears in the game files, spaces, underscores, and alphanumeric characters all matter.

When executed correctly, the console returns a confirmation message and the quest appears in the journal under the appropriate category (Main, Miscellaneous, Daedric, etc.). The first objective becomes active immediately, and any associated markers appear on the compass and map.

Common Syntax Errors to Avoid

The most frequent mistake is typing the Quest ID incorrectly. A single wrong character, confusing the letter O with the number 0, for example, causes the command to fail silently. The console won’t display an error: it simply won’t start the quest.

Another common error is including brackets in the actual command. The syntax StartQuest [MQ103] is incorrect. The brackets in documentation indicate where to insert the variable, but they shouldn’t be typed. The correct format is StartQuest MQ103 with no brackets.

Players sometimes confuse Quest IDs with Form IDs. Form IDs are hexadecimal codes (like 000A2C94) used for items, NPCs, and other objects. Quest commands require the Editor ID string, not the numerical Form ID.

Spaces within Quest IDs are rare but exist for some miscellaneous quests. If a quest ID contains a space, it must be typed exactly as documented. But, most quest IDs use no spaces and rely on alphanumeric combinations like MS01, FFRiften20, or DLC1VQ01.

Finding Quest IDs: Your Complete Resource Guide

Using the Help Command to Search Quests

Skyrim’s console includes a built-in search function that displays Quest IDs matching a keyword. The help command syntax is:

help "keyword" 4

The number 4 filters results to show only quests. For example, typing help "dragon" 4 returns all quest IDs containing the word “dragon,” including MQ106 (Dragon Rising) and various dragon-related radiant quests.

The help command is invaluable when a player knows part of a quest’s name but not the exact ID. Searching help "thieves" 4 reveals all Thieves Guild quest IDs, from TG00 through TG09, plus radiant quests like TGRQ and TGRShell.

Results appear in the console output as a scrollable list. Each entry shows the Quest ID followed by the quest’s internal name. Players can then copy the ID and use it with StartQuest. The console allows scrolling through results with Page Up and Page Down, but long result lists can be cumbersome to navigate.

One limitation: the help command only searches quest names as they appear in the Creation Kit, not the display names players see in their journal. “Diplomatic Immunity” appears as MQ201Party in the help results, which isn’t immediately obvious.

Essential Quest ID Databases and Wikis

For comprehensive Quest ID lists, external resources surpass in-game searching. The Unofficial Elder Scrolls Pages (UESP) maintains the most complete and accurate database of Skyrim quest IDs, updated regularly to include Anniversary Edition content.

UESP’s quest pages list both the display name and Editor ID for every quest, organized by category (Main, Faction, Daedric, Miscellaneous, etc.). Each quest entry includes prerequisite information, which helps avoid starting quests that break due to missing earlier steps. For modding utilities and tools that help manage quest data, dedicated software can extract Quest IDs directly from game files.

The Skyrim Wiki (part of Fandom) also catalogs Quest IDs, though its accuracy varies depending on community contributions. Cross-referencing between UESP and the Wiki helps verify Quest IDs for obscure or bugged quests.

For players working with advanced combat tactics, console commands can test quest-specific gear and buffs without playing through entire questlines. Many databases at Nexus Mods also include quest ID information in mod descriptions, especially for quest mods that add new content. Mod authors often list Quest IDs in readmes or on the mod page to help users troubleshoot conflicts.

The Creation Kit itself is the ultimate reference. Players with modding experience can open Skyrim’s master files (Skyrim.esm, Update.esm, and DLC files) to browse every quest record. This requires downloading the Creation Kit from Steam, but it provides access to every Quest ID, objective, and script in the game.

Top Quest IDs Every Skyrim Player Should Know

Main Questline Quest IDs

The main questline uses the prefix MQ followed by a number. These are the most commonly needed IDs when players want to skip Helgen, test endgame content, or fix broken progression:

• MQ101: Unbound (the Helgen intro)
• MQ102: Before the Storm
• MQ103: Bleak Falls Barrow
• MQ104: Dragon Rising
• MQ105: The Way of the Voice
• MQ106: The Horn of Jurgen Windcaller
• MQ201: Diplomatic Immunity
• MQ202: A Cornered Rat
• MQ203: Alduin’s Wall
• MQ204: The Throat of the World
• MQ301: Elder Knowledge
• MQ302: Alduin’s Bane
• MQ304: The Fallen
• MQ305: Paarthurnax
• MQ306: Season Unending

Starting MQ104 (Dragon Rising) is popular for alternate start playthroughs since it enables dragon spawns and Shouts without going through Helgen.

Faction and Guild Quest IDs

Faction questlines use distinctive prefixes that make them easy to identify:

Companions:

• C00: Take Up Arms
• C01: Proving Honor
• C03: The Silver Hand
• C05: Purity of Revenge
• C06: Glory of the Dead

College of Winterhold:

• MG01: First Lessons
• MG02: Under Saarthal
• MG03: Hitting the Books
• MG06: Containment
• MG07: The Staff of Magnus
• MG08: The Eye of Magnus

Thieves Guild:

• TG00: A Chance Arrangement
• TG01: Taking Care of Business
• TG02Startup: Loud and Clear
• TG05: Scoundrel’s Folly
• TG08A: Blindsighted
• TG09: Darkness Returns

Dark Brotherhood:

• DB01: Innocence Lost
• DB02: Sanctuary
• DB03: With Friends Like These
• DB08: Bound Until Death
• DB11: Hail Sithis.

For players following comprehensive quest progression paths, these IDs allow skipping problematic early quests or testing late-game faction rewards.

Daedric Quest IDs

Daedric quests reward powerful artifacts and are frequently started via console when shrines won’t trigger properly:

• DA01: The Taste of Death (Namira)
• DA02: The Only Cure (Peryite)
• DA03: A Night to Remember (Sanguine)
• DA04: Discerning the Transmundane (Hermaeus Mora)
• DA05: Ill Met by Moonlight (Hircine)
• DA06: Boethiah’s Calling (Boethiah)
• DA07: The Cursed Tribe (Malacath)
• DA08: Pieces of the Past (Mehrunes Dagon)
• DA09: The Break of Dawn (Meridia)
• DA10: The House of Horrors (Molag Bal)
• DA11: A Daedra’s Best Friend (Clavicus Vile)
• DA13: Waking Nightmare (Vaermina)
• DA14: The Whispering Door (Mephala)
• DA15: The Black Star (Azura)
• DA16: The Mind of Madness (Sheogorath)

Note that some Daedric quests have level requirements. Starting them via console bypasses the level gate but may cause dialogue or reward scaling issues.

DLC Quest IDs (Dawnguard, Dragonborn, Hearthfire)

Dawnguard quests use the prefix DLC1:

• DLC1VQ01: Awakening (Vampire questline start)
• DLC1HV01: Dawnguard (Dawnguard faction start)
• DLC1VQ04: Bloodline
• DLC1VQ08: Unseen Visions

Dragonborn uses DLC2:

• DLC2MQ01: Dragonborn (main DLC start)
• DLC2MQ02: The Temple of Miraak
• DLC2MQ03: The Fate of the Skaal
• DLC2MQ04: Cleansing the Stones
• DLC2MQ06: At the Summit of Apocrypha

Hearthfire has minimal questing but includes:

• BYOHHousePurchase: Purchase land for homebuilding

Players building optimal character builds often use console commands to access DLC content early for specific perks or gear.

Advanced Quest Command Techniques

Using SetStage to Jump to Specific Quest Objectives

While StartQuest initializes a quest, SetStage advances it to a specific objective. This is critical when a quest starts but won’t progress, or when testing a particular quest stage without playing through earlier objectives.

The syntax is:

SetStage [QuestID] [StageNumber]

For example, to jump to stage 20 of “The Way of the Voice” (MQ105):

SetStage MQ105 20

Stage numbers are not arbitrary, they correspond to specific quest objectives as defined in the Creation Kit. Most quests use increments of 10 (10, 20, 30, etc.), but this isn’t universal. Finding the correct stage number requires consulting UESP or the Creation Kit.

SetStage is more surgical than StartQuest and is essential for fixing quests that are active but stuck. If an NPC won’t trigger the next dialogue or an objective marker won’t clear, advancing to the next stage manually often resolves the issue.

One warning: using SetStage to skip stages can break quest scripts. If stage 30 expects that stage 20’s script ran and stored certain variables, jumping directly to 30 may cause errors. Always save before experimenting with SetStage.

Combining StartQuest with Other Console Commands

Console commands stack, allowing complex workarounds for broken quests or creative playthroughs. Here are powerful combinations:

StartQuest + MoveTo Player: Start a quest and teleport the associated NPC to the player’s location. Useful when a quest giver is stuck or inaccessible. First, use help "NPC name" 4 to find their reference ID, then:

prid [RefID]

moveto player

StartQuest + SetObjectiveDisplayed: Manually display a specific objective if the quest starts but doesn’t show any markers. Syntax:

SetObjectiveDisplayed [QuestID] [ObjectiveNumber] 1

StartQuest + CompleteQuest: For testing, players can start and immediately complete a quest to check rewards or unlock follow-up quests:

StartQuest MQ103

CompleteQuest MQ103

This is particularly useful for mod testing when a new quest depends on vanilla quests being completed.

StartQuest + ResetQuest: If a quest breaks after starting, ResetQuest clears all progress and allows a fresh start:

ResetQuest [QuestID]

After resetting, use StartQuest again to retry from the beginning. This often fixes quests with corrupted variables or broken scripts, though it erases all progress on that specific quest.

Troubleshooting Common StartQuest Issues

Quest Won’t Start or Shows as Already Completed

If StartQuest executes without error but the quest doesn’t appear in the journal, the quest may already be flagged as completed or disabled by another mod. Check the quest status with:

GetQuestCompleted [QuestID]

If it returns 1, the quest is marked complete. To reset and restart it:

ResetQuest [QuestID]

StartQuest [QuestID]

Another issue: some quests are aliases or parent quests that don’t appear in the journal directly. For example, radiant quests use shell quests that spawn instances. Starting the shell quest (like TGRQ01) may not produce visible results because it needs parameters set by the radiant quest system.

For players encountering early-game issues, many quest problems stem from rushing console commands before meeting prerequisites. Some quests expect certain variables or game states to be set before they function properly.

Fixing Broken Quest Chains

Quest chains with dependencies can break if started out of order. Starting TG05 without completing TG01-TG04 will likely result in missing dialogue, incorrect objectives, or NPCs who won’t interact properly.

When a quest chain breaks:

1. Identify the prerequisite quest using UESP or the Creation Kit.
2. Complete the prerequisite using CompleteQuest [QuestID] for each earlier quest in the chain.
3. Use SetStage on the broken quest to advance past the problematic objective.

Example: If TG05 (Scoundrel’s Folly) won’t progress because Mercer Frey won’t talk, complete the previous quests first:

CompleteQuest TG01

CompleteQuest TG02Startup

CompleteQuest TG03

CompleteQuest TG04

StartQuest TG05

This satisfies the game’s internal checks and often unsticks the quest. For detailed optimization techniques that prevent quest chain issues, proper save management is critical.

Quest Conflicts and Script Errors

Mods that alter quests can conflict with StartQuest commands. A mod that changes MQ103’s objectives will clash with the vanilla StartQuest command, potentially causing the quest to start with broken objectives or missing markers.

To diagnose mod conflicts:

1. Load the game without mods (or with a minimal load order).
2. Test the StartQuest command in the clean environment.
3. If it works, re-enable mods gradually to identify the conflicting mod.

Script errors sometimes appear in the console output after using StartQuest. Messages like “cannot run script” or “property not found” indicate that a script attached to the quest is broken or missing. This often happens with improperly uninstalled mods that left orphaned scripts.

Fixes include:

• Using LOOT (Load Order Optimization Tool) to sort mod load order and identify conflicts.
• Cleaning save files with Fallrim Tools (formerly Save Game Script Cleaner) to remove broken scripts.
• Reinstalling or updating mods that affect the problematic quest.

For ongoing quest issues, communities at Twinfinite frequently document mod conflicts and provide workarounds specific to popular mod combinations.

When to Use StartQuest vs. Alternative Commands

StartQuest is ideal for launching quests from scratch but not always the best tool for every situation. Understanding when to use alternatives prevents unnecessary complications.

Use StartQuest when:

• A quest won’t trigger naturally due to a bug.
• Testing mod content that adds new quests.
• Creating an alternate start playthrough with specific quests active.
• Skipping early questline entries to access later content.

Use SetStage instead when:

• A quest is already active but stuck on a specific objective.
• Skipping a single bugged objective while preserving quest progress.
• Advancing a quest without manually completing objectives (e.g., skipping a fetch task).

Use CompleteQuest when:

• A quest is hopelessly broken and needs to be marked finished to unlock subsequent quests.
• Testing builds that require quest rewards without playing through the content.
• Cleaning up the quest log after using multiple console workarounds.

Use ResetQuest when:

• A quest started incorrectly and needs a clean restart.
• Variables or scripts became corrupted mid-quest.
• Testing a quest multiple times for mod development.

For players following strategic gameplay approaches, choosing the right command for the situation saves time and avoids creating new problems. StartQuest is powerful but blunt, it won’t fix a quest that’s already broken, and it can cause issues if prerequisites aren’t met.

Best Practices and Important Warnings

Save Your Game Before Using Console Commands

This is non-negotiable. Console commands can irreversibly alter game state, corrupt quests, or introduce script errors that persist across saves. Always create a hard save (not a quicksave) before using StartQuest or any other command.

Best practice: create a dedicated “console testing” save slot separate from main playthrough saves. Name it something obvious like “Pre-Command MQ104 Test.” If the command breaks something, load this save instead of losing hours of progress.

Some commands cause delayed effects that don’t appear immediately. A quest might start fine but break two hours later when a script fails to execute properly. Having a clean pre-command save allows rolling back without investigating which command caused the issue.

Achievement and Trophy Implications

On PC (all editions), opening the console disables achievements for the current play session. The achievement system re-enables after closing the game and restarting, but any achievements earned during a session with console use won’t trigger.

There’s a workaround: the Achievements Mods Enabler (SSE) mod on Nexus Mods removes this restriction, allowing console use and achievements simultaneously. This mod is widely used and safe, though some players prefer the vanilla achievement system as a challenge.

On Xbox Series X

|

S and PlayStation 5 (Special Edition and Anniversary Edition), mods disable achievements entirely. Console commands accessed through mods like Cheat Room carry the same penalty, no achievements while any mods are active, regardless of what they do.

Achievement hunters should complete achievement runs first, then use console commands on separate playthroughs. The trade-off is stark: console access provides unlimited flexibility, but it permanently flags saves as modded and removes achievement eligibility on consoles.

Conclusion

The StartQuest command transforms Skyrim from a sometimes-buggy open world into a fully controllable testing ground. Whether fixing a broken quest chain, skipping content for the twentieth time, or accessing DLC content early, this single command opens doors that Bethesda never intended to gate behind bugs or broken triggers.

Mastering Quest IDs, understanding the difference between StartQuest and SetStage, and knowing how to troubleshoot conflicts separates casual console users from power users who can resurrect any questline. The key is precision, one wrong character in a Quest ID, and nothing happens. But with the right ID and proper syntax, players control Skyrim’s entire quest structure.

Save early, save often, and never use console commands on a save players aren’t willing to lose. The flexibility is immense, but so is the potential for breaking things. With that in mind, the command console becomes less a cheat tool and more a necessity for anyone serious about modding, testing, or simply refusing to let a bug ruin 200 hours of progress.