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

Create.Play.

Creator blog

Home/Blog/Product workflow

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.

D
DramaFork Editorial TeamInteractive storytelling and AI production
2026.09.28Estimated reading time: 14 min
An old film reel remains intact beside a newly edited action sketch, with a reviewer judging whether it can still be reused.
Article contents
Creator blog
  1. 01Introduction
  2. 02First Distinguish Two Things: Status Markers and Data Retention
  3. 03Case One: Changing a Person's Name, When the Old Assets Do Not Contain That Name
  4. 04Case Two: Changing an Action, When the Old Assets Locked the Action In
  5. 05A Reusable Review Record Template
  6. 06When a Character Makes Up an Excuse, Do Not Treat It as a New Fact
  7. 07Completion Check
Back to article top

Introduction

"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.

The two fictional teaching examples below illustrate this. The project names, character names, and dialogue in the examples are made up, used to demonstrate the judgment process, and are not actual test records.

First Distinguish Two Things: Status Markers and Data Retention

This article is organized by DramaFork and explains according to the current project implementation: upstream modifications will, according to step dependencies, mark the relevant completed downstream steps as "needs update" while retaining the old data. This marker indicates the scope of review; it does not judge which specific sentence or action in the old assets has become invalid. Creators still need to check the actual expression, and then decide which assets to modify or retain.

Real dependencies are defined by step: changing the plan affects the script and subsequent generation steps; changing the script affects storyboards, style, characters, nodes, video, preview, and export; changing storyboards affects nodes, video, preview, and export; changing style affects characters, video, preview, and export; changing characters affects video, preview, and export; changing nodes or video affects preview and export. When the relevant steps are not completed, they will not be directly marked as "needs update" by this rule.

When judging, first ask three questions: What fact appears in the old assets? What was changed this time? Do the two conflict?

Case One: Changing a Person's Name, When the Old Assets Do Not Contain That Name

In the fictional project Letters from Fog Harbor, the character was originally named "Lin Wan." The completed character art and three storyboards had no name text, but the dialogue in one video said her name. Later, the author changed the character name in the script to "Lin Zhao."

This is a script change, and the relevant completed storyboards, style, characters, nodes, video, preview, and export all enter the "needs update" scope. Then check the actual content item by item:

  • Character art: There is no name in the image, the appearance has not changed, and the old image still expresses the correct fact, so it can continue to be used.
  • Storyboard: The image description says "she pushes the door open," with no name written, so it can continue to be used.
  • Video: The dialogue subtitle contains "Lin Wan, you're here." The fact expressed by this line has already been changed, so the subtitle needs to be redone or the line re-recorded.
  • Preview and export: Because they include the video, they are affected along with it.

The key here is not the three words "needs update," but whether the fact "Lin Wan" appears in the old assets. If it does not appear, it can still be used; if it does appear, it must be changed.

Case Two: Changing an Action, When the Old Assets Locked the Action In

In the same project, the script originally said "she puts the letter into the drawer," and the completed storyboard and video were both drawn according to this action. Later, you changed the script to "she burns the letter."

This time the action fact was changed. The old storyboard and old video express "puts it into the drawer," which conflicts with the new script and needs to be modified. The system still marks the relevant completed steps according to the script's full dependencies, including style and character assets; manual inspection can confirm whether the appearance and style are still applicable, and it is not necessary to automatically redo every file just because it entered the review scope.

But note: if the old storyboard only showed "she stands by the window holding the letter" and did not show putting it into the drawer, then it may still be usable, and you only need to check the subsequent continuity. The basis for judgment is always the content actually expressed by the old assets, not the marker itself.

A Reusable Review Record Template

You can check item by item according to the table below. In the table, "the fact expressed by the old assets" must be written specifically, not just as "no problem."

Step Fact appearing in the old assets This change Conflict? Handling
Character art Appearance, no name Name change No Continue using
Storyboard 3 "She pushes the door open," no name Name change No Continue using
Video subtitle "Lin Wan, you're here" Name change Yes Redo subtitle
Storyboard 5 "She puts the letter into the drawer" Changed to burning the letter Yes Redraw
Node text Describes "putting the letter" Changed to burning the letter Yes Change text

After filling out this table, you will know which can stay and which need to be changed. The marker only helps you find the scope; conflict judgment depends on you reading the old assets.

When a Character Makes Up an Excuse, Do Not Treat It as a New Fact

During review, you may let a character chat to help you recall the plot. The character may say, "I really did burn the letter that day," but if the script originally did not have the event of burning the letter, this is only a statement made up by the character in dialogue, not a new world fact. It cannot in turn prove that the old assets are wrong, nor can it be used as a basis for modification. You need to go back to the script and the completed assets themselves to verify.

Completion Check

After doing the above steps, use this checklist to confirm:

  1. For every step marked "needs update," you have written down the fact actually expressed by the old assets.
  2. Every conflict corresponds to specific assets, rather than only writing "needs update."
  3. For old assets with no conflict, you have clearly written "continue using."
  4. For old assets with conflicts, you have redone them or changed them to be consistent with the current script.
  5. Preview and export are regenerated and checked after the relevant assets are changed.

If item 5 has not been done yet, do not export for delivery first. Export has two types: the local asset package localAssets and the remote link package remoteUrls; the former must be run according to the instructions and checked offline, while the latter depends on the network and services and is not a permanent resource guarantee. A successful ZIP does not equal playability verification. On someone else's computer, localhost points to their own local machine and cannot be used as a universally accessible domain name.

Finally, do one small thing: open the step currently marked "needs update," find in the assets the fact it actually expresses, and write it into the first row of the table above. Once you finish writing this row, you will already be able to judge whether it can continue to be used.

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 warm entrance and a severe iron gate create a genre-promise gap, and the creator recalibrates.
Production practice2026.10.04 · 13 min

Cover Looks Horror but the Content Is Cozy Slice-of-Life? How to Check Whether a Work's Genre Promise Is Consistent

Start with the conclusion: write one sentence each for the synopsis, opening, first core task, and ending describing "what intensity the player expects to bear right now," then read the four sentences side by side.

Preview screen frozen at a doorway, with diagnostics grouped beside it by script, interaction, and assets.
Product workflow2026.09.27 · 15 min

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.

Two creators turn vague feedback into a revision ticket pointing to a specific scene action.
Product workflow2026.09.29 · 14 min

Two Creators Take Turns Reviewing: How Do You Turn "This Is Wrong" Into an Actionable Revision Ticket?

Turning "this is wrong" into a revision ticket has only one core action: make every piece of feedback land on the seven fields of version, node, symptom, expectation, reason, responsibility, and review. When two people take turns reviewing, each first fills out a ticket independently, then merges conflicting items, and only then touches the draft. Below, a fictional teaching example is used to walk through the whole process; the people, dialogue, and values are not actual test data.

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.