Same IP Character Chat and Text Adventure: How to Explain the Relationship Without Making Players Think Progress Is Shared?
Describe the relationship between the two entry points as "same world, same character identity, each progresses independently," and use a state comparison table on the entry page to clarify what carries over and what does not. The approach has four steps: first define a character profile for the IP as the shared identity foundation for both entry points; then write a separate "state boundary" statement for each entry point; next prepare a can-say/cannot-say table to constrain marketing copy; finally use a fictional dialogue to test whether players form incorrect expectations after reading.
Introduction
Describe the relationship between the two entry points as "same world, same character identity, each progresses independently," and use a state comparison table on the entry page to clarify what carries over and what does not. The approach has four steps: first define a character profile for the IP as the shared identity foundation for both entry points; then write a separate "state boundary" statement for each entry point; next prepare a can-say/cannot-say table to constrain marketing copy; finally use a fictional dialogue to test whether players form incorrect expectations after reading. Below, a fictional teaching example is used to walk through the whole process. The characters, values, and quoted lines in the example are made up for demonstration, not actual test data.
First Distinguish Three Kinds of "Sharing"
Sharing a worldview does not equal sharing progress. Take the fictional "Fog Harbor Post Office" IP as an example: the same post office, the same group of postal workers, the same stretch of city history—this is the worldview layer, and it can be shared. The identity, goals, needs, secrets, initial relationship, arc, and boundaries of the character "night-shift postal worker Lin Chi"—this is the character profile layer, and it can be shared. How many rounds the player has chatted in character chat, which chapter they have reached in the text adventure, and what level of favorability they have with Lin Chi—this is the experience state layer, and the two entry points each store their own.
If these three layers are explained mixed together, players will assume, "I promised in chat to help him find the letter, so he should remember that in the adventure." Therefore, entry copy should be written separately by layer, rather than vaguely saying "the same Lin Chi accompanies you."
Write a Reusable Profile for the Character
The profile only writes the identity layer, not any entry point's progress. It can be filled in according to these seven items:
| Item | Lin Chi's profile content |
|---|---|
| Identity | Night-shift postal worker at Fog Harbor Post Office, responsible for returned and dead letters |
| Goal | Deliver a letter with no recipient |
| Need | Admit that he is also waiting for a reply that will never come |
| Secret | He once withheld a letter that should have been returned |
| Initial relationship | A colleague who has just met the player |
| Arc | From delivering letters for others to being willing to handle his own letter |
| Boundary | Does not make decisions for the player, does not promise anything not explicitly written |
Both entry points reference this profile, but what they reference is identity, not state. In character chat, Lin Chi can remain "a colleague who has just met you," and in the text adventure he can also start from the same initial relationship. The two sides each move forward on their own and do not overwrite each other.
Entry Copy: Write "Independence" on the First Screen
The character chat entry can be written like this:
You play the role of a new colleague at the post office and chat with Lin Chi during the night shift. This place only records your interactions in this conversation. His identity, secrets, and boundaries come from the Fog Harbor Post Office setting, but what you experience with him elsewhere will not automatically appear here.
The text adventure entry can be written like this:
You enter a night-shift story at Fog Harbor Post Office, play a new colleague, and handle returned letters together with Lin Chi and other postal workers. The plot, choices, log, and state belong only to this adventure. Conversations in the chat entry will not change the direction here.
Both passages first give the player an identity, then clarify state ownership. Note that sentences like "will not automatically appear" and "will not change" should be specific about the object, not just say "data is independent," which players will not understand.
Can-Say/Cannot-Say Table
When operations write event pages, push notifications, and community scripts, revise them against this table.
| Can write | Do not write |
|---|---|
| The same Fog Harbor Post Office, the same Lin Chi | Lin Chi remembers what you said in the other entry point |
| The two entry points share the character identity and worldview | Chat favorability will sync to the adventure |
| Each records its own conversation and plot progress | Progress is automatically inherited across entry points |
| The character profile determines his goals and boundaries | He will proactively come find you on a schedule |
| Gifts are symbolic expressions of affection | Sending gifts can unlock core understanding or consent |
| In chat you can send images with text explanations | The system can recognize what is in the image you send |
The purpose of this table is to prevent promotional language from crossing product boundaries. This article is organized by DramaFork and explains according to the current project implementation: character chat and AI text adventure are existing experience directories. Ordinary users currently do not have a self-service creation editor for arbitrary characters or text games, so the copy should not imply that players can create a new Lin Chi themselves.
Use a Dialogue as a Completion Check
After writing the copy, make up a question a player would ask and check the answer item by item.
A player asks: "I told Lin Chi about my sister in chat. Will he mention it in the adventure?"
According to the copy above, the correct answer is: he will not automatically mention it. Because the conversation in chat belongs to the chat entry's state, and the adventure entry only starts from its own initial state. Unless the adventure script itself includes a related plot, Lin Chi does not know about this in the adventure. It should be clearly marked here: Lin Chi "not knowing" is the result of entry state isolation, not a newly added world fact that "Lin Chi has amnesia."
The player asks again: "Then if I help him find the letter in the adventure, will he thank me in chat?"
The same thing will not automatically happen. The two entry points progress separately, and there is no guarantee of shared progress or favorability across entry points. If operations wants to say "there is a relationship," it can only say "the same character, the same set of identity settings," not "the same experience."
Three Easy Pitfalls
The first pitfall is describing "same IP" as "same save." When players see the same character name, they easily assume continuous memory, so the first screen of the entry point must state state ownership.
The second pitfall is writing gifts as a shortcut to relationships. In the setting, gifts are symbolic; they cannot buy consent, nor can they buy core understanding. Copy should not contain lines like "give enough and you can unlock his true heart."
The third pitfall is saying chat attachments can understand images. Attachment pixels stay in the browser and are not sent to the text model. They cannot recognize objects in images and can only respond to the text explanation you write. Therefore, copy can only say "you can send images with text," not "he can understand the photos you send."
Completion Checklist
- The character profile only writes the seven identity items and does not include any entry point progress.
- Each of the two entry points has a state boundary statement, and it is written on the first screen.
- The can-say/cannot-say table covers six categories: memory, progress, favorability, push notifications, gifts, and attachments.
- There are no unimplemented descriptions such as "automatic sync," "cross-entry inheritance," or "come find you on a schedule."
- Use a player question as a check, and the answer is consistent with the copy.
Finally, do one small thing: replace "Fog Harbor Post Office" with the IP you have on hand, replace Lin Chi with your character, write one version each according to the seven-item profile and the two entry copy passages, then delete boundary-crossing sentences against the can-say/cannot-say table.
