Short answer: The Problems tab of the Forge dock is one list of every issue in your project - a missing asset, a jump to a scene that doesn't exist, a construct that needs a look. Each row is written in plain language, and clicking it jumps you to the exact event or script line involved. Severity and consequence are separate things: a warning never stops you from working, and the rows that would actually block saving or publishing say so explicitly.
What a row tells you
Each row leads with a short headline and a severity marker - error, warning, or info. Expanding the row reveals the full description and any follow-up actions. When something would actually stop you, the row carries an explicit consequence chip such as "Will not save until fixed" - if a row doesn't say that, it's advice, not a blocker.
When the same problem occurs several times in one scene (say, ten references to the same missing image), they collapse into a single row with a numbered jump chip for each occurrence, so the list stays readable.
Two ways to group the list
A switch at the top of the panel picks how the list is organized:
- Scenes - one collapsible group per scene. This is the triage view: work through a scene's issues top to bottom while you're editing it.
- Types - one collapsible group per kind of problem. This is the sweep view: fix every "unknown asset" across the whole project in one pass, then move to the next type.
Severity filter chips carry live counts, so you can hide info rows and see at a glance how many real errors remain.
Jumping to the problem
The whole row is a button: click anywhere on it and Forge jumps to the first occurrence - selecting the event on the timeline, or landing on the script line. Rows with multiple occurrences show a jump chip per instance so you can visit each one. The same headlines appear on script problems in the Script view, so a problem reads the same wherever you meet it.
Warnings never block you
Severity says how serious an issue is; consequence says what it prevents. They're deliberately separate. Most issues - including everything at warning level - never stop you from editing, saving, or playing your project. Only the rows that explicitly state a consequence stand between you and saving or publishing, and fixing exactly those rows clears the path.
Imported projects and warnings
Projects imported from Ren'Py often arrive with a list of warnings. That's expected - it's the importer being honest about what needs a human look rather than guessing silently. An imported project with warnings is still fully editable and playable; work through the list at your own pace, using the Scenes grouping to clean up as you touch each scene.