The quest log won't move on: what the diary, the chapter and the story variables mean
Checked against Gothic 1 Classic 1.08k · November 16, 2026
When a mission does not move on in Gothic 1, the diary is the first place players look, and it is the wrong one to fix. The quest log is only the hero's notes: what people say and do follows the story's own state, which the game keeps next to the diary. This guide explains the difference, goes through problems players have reported, lists what to check, and shows what the editor can and cannot change.
The diary is not the story
Every mission and note in the diary is a topic with a status and the lines that were added to it. A mission is Running, Done, Failed or No longer relevant. The game sets the status when the story says so, but the status itself changes nothing: what a person says, and which events have happened, depends on the story's own variables.
That is why a mission marked done does not give its reward, does not let the next person talk to you and does not start whatever should follow. It also explains the opposite case: a mission can sit under Running long after the story has moved past it.
The chapter works the same way. It moves on as the story does, and the next set of missions and people follows from it.
Problems players report
These come from player threads and fan guides on the 2001 game. Each was reported by few people, so this is a list of examples, not a ranking of the most common. Where a report names a fix, it is the players' and not the developers'.
- The mission Xardas the Necromancer is under Failed after the talk with Saturas (chapter 4). Players disagree about whether telling the truth about Xardas would have kept it going. It doesn't: once you have met Xardas, Saturas asks how it went, and either answer that ends the talk marks the mission Failed. The story goes on with Xardas' errand to the banished Orc shaman, so nothing needs fixing.
- The winch in the Old Mine is jammed. A player closed it by accident and it stayed shut. The report that worked was an older save from before it.
- The game freezes after taking an item from the chest on the monastery trip with Gorn. One player says it worked once Gorn was in the room with him, after he had got stuck behind a corner. Wait for your companion before you open it.
- Homer can't be found to hand in the mission Lurker at the Dam. He stands at the dam, where you first meet him, until he moves to his hut in the New Camp, where he sits outside 7:30–21:30 and sleeps inside; he moves there when you hand the mission in, and later in the story when Lee tells you about the dam. He takes the mission only while you carry the Dam Lurker's Claws, which you loot from the lurker. See where everyone is during the day, and check he is alive with the dead-NPC guide.
- Cipher, at the bar on the lake in the New Camp, will not trade or talk during the mission The Swampweed Harvest. He deals only once Balor, the Novice who hands you the weed in the swamp, has named him: offer Balor to go halves and pay him 50 ore for the name. You do not need to hand over the weed for it.
The pattern in these: a person is not where you look, something was done in the wrong order, or a companion is missing. All three are worth checking before anything else, and an older save is the fix when you can't find the cause.
What to check first
- Read the mission's entries from first to last: the last one is what the game last told you to do, and often who to see.
- Is the person you need awake and at their post? People keep a daily schedule, so see where everyone is during the day.
- Is someone the mission needs dead? The dead-NPC guide shows who is gone and how to get them back.
- Did you lose a letter, key or other item the mission handed you? See the lost-item guide.
- Are you in the camp the mission is for? Some missions only exist for one camp, see the camp guide.
- Did you leave a place before finishing there? Some missions end when the story moves on, and are then marked Failed or No longer relevant.
Look and change in the editor
The editor shows what your save holds, for offline single-player saves only.
- Close Gothic and copy the whole savegame folder. The editor keeps no backups, and edits are at your own risk.
- Open the folder's files in the editor and go to the Quest log tab. Search for the mission by a word of its name and read its entries.
- Look at the Chapter in the Character tab, and at the story's own variables in the Script variables tab.
What is safe and what isn't:
- Marking a mission Running, Done, Failed or No longer relevant in the Quest log is safe. It tidies a diary that no longer matches what the story did, and changes the notes only.
- The Chapter is a story variable, and the editor changes it only through the Script variables tab. The game does more than raise a number when the story enters a new chapter, and setting it by hand skips all of it, so people may be missing or in the wrong place. Treat it as a last resort.
- The Script variables tab lists the story's variables under their original names, most of them German. Change only what you know, and use Changed only to see what you altered. A wrong value can break a mission or the story.
- The editor does not show which conversations you have had with each person. When a mission stalls because a person will not say the line that starts the next step, the cause is often there, and no tab changes it.
If you change a variable and the story misbehaves, go back to your copy of the savegame folder. The editor can't tell whether a value is right for your point in the story.