• Home
  • Blog
  • Gallery
  • Pricing
  • Home
  • Blog
  • Gallery
  • Pricing
Start creating

Create.Play.

Creator blog

Home/Blog/Product workflow

How to Group Issues in a DramaFork Playable Preview: Which Step Should Story, Interaction, and Assets Each Go Back To for Fixes?

When issues appear in a playable preview, don't rush to change nodes. Use a one-sentence symptom record to clearly write down "who saw what at what moment," then determine whether it belongs to story, interaction, or assets. Story issues go back to planning or script, interaction issues go back to interaction nodes, and asset issues go back to storyboard, style, character assets, or video; after changes, only recheck the affected downstream steps, and do not treat a preview that runs successfully as passing release testing.

D
DramaFork Editorial TeamInteractive storytelling and AI production
2026.09.27Estimated reading time: 15 min
Preview screen frozen at a doorway, with diagnostics grouped beside it by script, interaction, and assets.
Article contents
Creator blog
  1. 01Introduction
  2. 02First Write a Symptom Record, Then Group
  3. 03Interaction Issues Go Back to Nodes for Changes
  4. 04Asset Issues Go Back to Storyboard, Style, Character, or Video for Changes
  5. 05Story Issues Go Back to Planning or Script for Changes
  6. 06Minimal Recheck Route After Upstream Changes
  7. 07Completion Check
Back to article top

Introduction

When issues appear in a playable preview, don't rush to change nodes. Use a one-sentence symptom record to clearly write down "who saw what at what moment," then determine whether it belongs to story, interaction, or assets. Story issues go back to planning or script, interaction issues go back to interaction nodes, and asset issues go back to storyboard, style, character assets, or video; after changes, only recheck the affected downstream steps, and do not treat a preview that runs successfully as passing release testing.

The following uses a fictional teaching example throughout: the interactive film game Night Shift at Fog Harbor, whose protagonist is night-shift lighthouse keeper Lin Che, whose goal is to survive until dawn and find out where the missing crew member went, whose secret is that he once abandoned ship and escaped in the same waters, and whose initial relationship with dispatcher Shen Lan is one of mutual distrust. The following characters, numbers, and dialogue are all fictional and do not correspond to any real project.

First Write a Symptom Record, Then Group

A symptom record should include four items: when it occurs, what the player sees, expected content, and the shortest reproducible path. The timing should be written to a specific node, for example "when the options are first displayed after entering node N-07." Do not write "that middle part feels weird," because that cannot be located.

The three records for Night Shift at Fog Harbor can be filled in like this:

No. When it occurs What the player sees Expected Initial judgment
S1 When options appear at node N-03 The three options have almost the same tone At least one option reflects Lin Che hiding his past of abandoning ship Interaction
S2 The video played after choosing "Question Shen Lan" Shen Lan is smiling, but the line is interrogating Expression matches the interrogating tone Assets
S3 Entering N-06 from N-05 It jumps directly to dawn, missing the ship-search process There should be a search segment in between Story

The basis for grouping is "is the error in the text, in the visuals, or in the order of events." The option text in S1 is carried by the node, so it belongs to interaction; the visuals in S2 come from video assets, so they belong to assets; S3 is a missing event, so it belongs to story.

Interaction Issues Go Back to Nodes for Changes

The root cause of S1 is the node copy. Nodes are organized in a table, with one row corresponding to one occurrence position, not a drag-and-drop graph. When modifying, first confirm that the video and conditions attached to that node have not changed, and only change the option text.

Original options:

  • Ask him why he came to the lighthouse
  • Ask him about tonight's tide level
  • Ask nothing

Change to:

  • Ask him why he came to the lighthouse
  • Ask him about tonight's tide level, and incidentally probe whether he knows the White Gull
  • Ask nothing, turn around, and go check the cables

The second option turns Lin Che's secret into a direction that can be probed, and the third option gives an evasive posture. After the change, only recheck the preview segment after N-03, checking whether all three options can enter their respective follow-ups, and do not recheck the entire line.

Asset Issues Go Back to Storyboard, Style, Character, or Video for Changes

In S2, the expression conflicts with the line. First determine whether the input required this expression. The storyboard determines the action and emotional intent in the shot, the style constrains the visual texture, the character assets provide character references, and the video is the actual generated result. In this example, the storyboard already clearly states "serious interrogation," and the reference also has no smiling requirement, but the generated clip is still smiling. You can start by checking this video task first, and you cannot infer from the image alone which frame the model selected internally.

The handling method is to check the corresponding storyboard and reference, clarify the action description if necessary, and then retry this video task separately. If the character reference itself carries an inapplicable expression, go back to the character asset step to modify it, and check other clips that use that reference. After retrying, you still need to look at the actual output; the troubleshooting here does not include timeline or frame-by-frame expression replacement functions.

Story Issues Go Back to Planning or Script for Changes

S3 is missing the ship-search process, which belongs to event structure. First go back to the script and add a search scene between N-05 and N-06: Lin Che checks the cargo hold, discovers the cut cable, and hears footsteps above. After adding it, the goal in planning to "find out where the missing crew member went" has a corresponding passage.

Changing the script will affect storyboard, style, character, nodes, video, preview, and export downstream. In actual operation, only mark the relevant and already completed steps as needing updates, and keep the old data. There is no semantically precise automatic diff, and no one-click confirmation reuse, so manual checking is required: whether the newly added search passage still makes the old storyboard and video expressions valid.

Minimal Recheck Route After Upstream Changes

After the three symptoms are fixed respectively, the recheck scope is determined by the layer changed:

  1. Only node copy changed: recheck the preview segment of that node and its direct successors.
  2. Only video assets changed: recheck the playback effect of the node to which that video is attached.
  3. Script changed with a new passage: recheck the storyboard, video, and nodes corresponding to the new passage, as well as its connection with the preceding and following nodes.
  4. Character assets changed: recheck all videos and preview segments that use that character.

When rechecking, use the same symptom record to fill in the results, for example S1 is recorded as "changed, the three options have distinguishable tones," S2 is recorded as "the corresponding video has been retried, and the actual expression matches the interrogation," and S3 is recorded as "the search segment has been added, and the connection from N-05 to N-06 is complete." These are still fictional filling examples, and actual projects should record according to observed results.

Completion Check

  • Each symptom has when it occurs, what is seen, expected content, and the shortest reproduction path.
  • The grouping conclusion points to a specific step, and does not say "adjust the whole thing again."
  • Changing nodes only touches nodes, changing video only touches video, and unrelated steps are not affected.
  • After upstream changes, only mark the relevant completed steps as needing updates, and keep the old data.
  • The recheck scope corresponds to the changed layer, and rerunning the entire line is not treated as the only method.
  • A preview that can play continuously does not mean release testing has passed; after export, it still needs to be checked according to the asset package instructions.

This article was organized by DramaFork and is explained according to the current project implementation. The playable preview is used to check the connection between nodes and assets, and does not replace playability verification after export. A successful ZIP does not mean playability verification has passed; localhost on someone else's computer points to their local machine and cannot be used as a universally accessible domain.

Next step: pick a preview symptom you recently encountered, fill in one row according to the table above, write down when it occurs and the shortest reproduction path, and then decide whether it goes back to story, interaction, or assets.

Explore product capabilities Play interactive stories

Updated 2026.10.04

Explore this topicMaking interactive filmsCharacter and worldbuilding
PLAY / DISCOVER

Related works and experiences

Browse the works index
Interactive film · Concept preview

The Black Rose Witness

Caught between a mafia marriage and a deadly testimony, a witness must decide whom to trust before the truth turns violent.

Interactive film · Concept preview

Elevator Thirteen

An elevator keeps stopping on a thirteenth floor that should not exist, where a missing reflection may know how to escape the loop.

Interactive film · Concept preview

Last Train to Tomorrow

The last train runs toward two futures: a thriving city and a ruined world. Your choices decide its final stop.

Interactive film · Concept preview

One Bed Left

One intensive-care bed remains and several patients need it. Every clinical decision carries a human cost.

Continue reading

Browse more articles
A character reference sheet, costume fabric, and silhouette studies are checked around the same collar detail.
Product workflow2026.09.26 · 15 min

What to Check Before Confirming DramaFork Character Assets: Identify the Person First, Then Check Emotion and Shot Fit

Do four things first, then decide whether to use a character image: identify identity anchors, break down costume states, write action requirements, and list scene conditions. Only when all four steps pass does the image enter the usable pool; if it only passes the "looks good" test, rework is likely later in the video and preview stages. The following uses a fictional teaching example: the character is Shen Yan, an adult postman, and the story takes place in a windy harbor city. The names, numbers, and quoted lines are all made up and are only used to demonstrate the order of judgment.

A character lowers a paper boat onto an empty desk, completing the missing action between adjacent storyboard frames.
Product workflow2026.09.25 · 13 min

DramaFork Storyboard Misses an Action: Why Later Assets May Not Match

When a storyboard misses an action, first check the exit of the previous shot against the entrance of the next shot. For example, at the end of shot 7 the paper boat is still in Lin Wan's hand, but at the start of shot 8 it is already on the table, with no action of putting the paper boat down in between. The author needs to add this transfer, then check whether nodes and videos still use the old description. Changing only the text of the later shot cannot prove that already completed segments change along with it.

An old film reel remains intact beside a newly edited action sketch, with a reviewer judging whether it can still be reused.
Product workflow2026.09.28 · 14 min

DramaFork Shows "Needs Update" but the Old Assets Are Still There—How Should Creators Judge Whether They Can Still Be Used?

"Needs update" only means that this change touched a dependency of some completed step. It does not mean the old assets have already been replaced, nor does it mean they are necessarily wrong. What you need to do is manually verify: is what was changed the fact that the old assets are expressing? If the fact expressed by the old assets still holds, they can continue to be used; if the fact they express has already been changed, they need to be redone or at least changed to be consistent.

From a story to a playable world.

Create interactive narrative games with DramaFork: connect scripts, characters, shots, and choices into a playable first version.

Explore & play

  • Explore gallery
  • Interactive film
  • Text game
  • Character IP
  • Rankings
  • Works index

Create & collaborate

  • My creations
  • Film studio
  • Text-game studio
  • Character studio
  • Creator partnership

Reading room

  • Creator blog
  • Story topics
  • Article archive

Story guides

  • Interactive storytelling
  • Making interactive films
  • Designing text games
  • Character and worldbuilding

Plans & credits

  • Pricing
  • Credits

Policies & support

  • Privacy
  • Terms
  • Cookies
© 2026 DramaFork/DramaFork · Interactive narrative games
Press Enter to send, or drag away and release.