At a glance#
| Journal | SW_FoundDatapad |
| Category | Side Quests |
| Journal entries | 2 |
| Completion branches | No explicit Finished marker |
| Starts by | Record route requires playtest verification. |
Walkthrough#
1. Reach journal stage 0#
Route needs playtest verification. No literal journal setter was found for this stage in the parsed dialogue/MWScript evidence. Follow the surrounding quest context and verify whether this entry is reachable, indirect, optional, or historical.
Expected journal update — index 0: I found the datapad
Technical / QA reference
Journal ID: SW_FoundDatapad
Generated category: Side Quests
Journal entries: 2
Exact journal progression
| Index | State | Journal text | Direct setters found |
|---|---|---|---|
| 0 | — | I found the datapad | 0 |
Record-level trigger map
Stage 0
I found the datapad
Direct setter: No literal Journal <quest> <index> command was found in the current plugin for this stage. Treat this as a QA flag: it may be a developer note, branch reached indirectly, or state written by code outside the parsed MWScript/result-script patterns.
Related records and locations
Generated playtest checklist
-
Start/reach the quest naturally and verify journal index
0is obtainable. -
Reach index
0: I found the datapad - Verify any scripted reward/item transfer shown above actually occurs.
- Verify involved NPCs/objects remain present and usable after the stage transition.
- Verify no unrelated vanilla Morrowind dialogue/quest state appears during the flow.
QA console reference
Current journal state can be inspected with the OpenMW/Morrowind journal tooling for SW_FoundDatapad. Manually forcing journal indices is useful for diagnosis, but does not substitute for testing the scripts/dialogue that normally cause the transition.