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

Create.Play.

Creator blog

Home/Blog/Creation tutorials

Team Competition Text Games: Why a Shared Total Isn’t Enough

The team still has stamina, yet no one can take the final leg. An original three-person relay shows how individual stamina, strengths, substitutes, and rest shape assignments.

D
DramaFork Editorial TeamInteractive storytelling and AI production
2026.11.19Estimated reading time: 12 min
An original three-person relay: teammates spread out a route map in the exchange zone, one takes the baton, another sits down to rest, and the final stretch lies in the distance.
Article contents
Creator blog
  1. 01Introduction
  2. 02Start by Making the Teammates Three Individuals
  3. 03Put Stage Requirements Alongside Each Person’s Remaining Stamina
  4. 04Give Rest a Cost and a Clear Effect
  5. 05Make Disagreements Affect Who Does the Task, and Allow Refusal
  6. 06End with a Results Sheet Readers Can Understand
Back to article top

Introduction

“The team has four stamina points left. You can continue.” But after the system says this, the next stage requires two people to participate at the same time. All four points belong to one person; the other two are exhausted.

If the work tracks only a single total, this situation is easy to gloss over: deduct four points from the team, and everyone finishes the course as though nothing happened. The competition appears to have teammates, but a shared health bar still determines what they can do.

What makes a team competition worth writing is precisely who still has energy, who is suited to the next leg, and how long everyone is willing to wait for someone. The original three-person relay below illustrates this. It discusses fictional gameplay only and offers no real-world training advice.

Start by Making the Teammates Three Individuals

The team consists of A-Lan, Ji He, and Meng Yao. A-Lan specializes in carrying and has a maximum stamina of four; Ji He specializes in reading maps and also has a maximum of four; Meng Yao specializes in balance and has a maximum of three. All three start at full stamina.

Each stage has two roles that must be filled simultaneously by two different teammates. A task in a character’s specialty costs two stamina points; any other task costs three. A character with exactly enough stamina can still complete the task, and reaching zero does not retroactively make them fail that stage. The teammate who does not participate recovers one point, up to their individual maximum.

Here, specialties determine costs; they do not permanently reserve a role for one person. If the work also has eligibility requirements that only certain characters meet, explain them in advance. Do not wait until the player has arranged a substitute to suddenly reveal, “Actually, he cannot participate.”

Put Stage Requirements Alongside Each Person’s Remaining Stamina

The three stages, in order, are “Carrying and Map Reading,” “Map Reading and Balance,” and “Carrying and Balance.” Before each stage, display the roles, individual stamina, and expected costs, then let the player assign teammates. Assignments can be changed before confirmation without spending stamina. Once confirmed, deduct both participants’ costs in a single calculation, then restore one point to the teammate who did not participate.

With the most obvious assignments, A-Lan handles carrying and Ji He reads the map in the first stage. Afterward, their stamina totals, in team order, are two, two, and three. In the second stage, Ji He reads the map and Meng Yao handles balance. Afterward, A-Lan recovers to three, Ji He reaches zero, and Meng Yao has one left.

The team now has four points in total, yet cannot complete the final stage. A-Lan can handle carrying, but Meng Yao has only one point and cannot handle balance, which requires two. Ji He cannot substitute with zero stamina either. The total of four is correct; the mistake is treating it as a shared balance that can be transferred freely.

At this point, the characters have begun to affect the rules. A-Lan saying “I can still go” does not also erase Meng Yao’s fatigue.

Give Rest a Cost and a Clear Effect

Add one option to this small example, disclosed at the start: the team may take a break between stages once during the entire competition, restoring one point to each person without exceeding their maximum. Each completed stage earns three points, and taking a break deducts one point from the final total. Ordinary intervals between stages do not automatically restore stamina to the whole team. The teammate who does not participate still recovers one point under the original rule.

On the route just described, taking a break after the second stage brings their stamina to four, one, and two. Assigning A-Lan to carrying and Meng Yao to balance then allows the team to complete all three stages. The three stages earn nine points; subtracting one for the break gives a final score of eight.

This break is neither presented as free nor portrayed as weakness. It creates the conditions for two people to participate together. Before confirming the break, the player can see the resulting stamina and the point deduction, then decide. If the player does not take a break and has no valid lineup, this example allows the team to withdraw, retaining six points for the two completed stages without forcing teammates to overexert themselves.

This is just one fully worked, calculable route, not a stamina table that every team competition must adopt. You can change the roles or costs, but after doing so, work through the assignments again. Do not merely change the numbers without checking whether completion is possible.

Make Disagreements Affect Who Does the Task, and Allow Refusal

You can add character opinions alongside the numbers. Meng Yao is willing to participate but wants to take a break first. Ji He feels it would be a shame to lose a point, yet saying “I support continuing” cannot replenish their stamina. Dialogue should respond to the immediate conditions instead of interpreting fatigue for the player as a lack of willpower.

If characters can refuse an assignment, let the player know before they confirm the lineup. After a refusal, the player can reassign roles, take a break, or withdraw. Do not deduct resources first and then tell the player that a teammate never agreed. For situations involving a group vote, continue with How to Preserve Minority Opinions After a Team Vote to carry the competition decision and individual attitudes forward separately.

End with a Results Sheet Readers Can Understand

How many stages were completed, whether the break was used, and how much stamina each person has left are enough to support a concrete ending. A team that finishes with eight points can regret missing out on one point while also appreciating that stopping allowed them to complete the exchange successfully. There is no need to use a single “team spirit score” to speak for everyone.

For the first version, use the text game creation page to write three teammates, the requirements for three stages, and one route through the calculations. Then change the lineup and try taking the break earlier, or letting someone’s stamina reach exactly zero. Only when the lineup, costs, and results all align does the team truly become part of the gameplay.

Explore product capabilities Play interactive stories
Explore this topicCharacter and worldbuildingDesigning text games
PLAY / DISCOVER

Related works and experiences

Browse the works index
Text game

Memory Black Market

Run an illegal memory clinic and decide whose life to preserve while clients, hunters, and conscience close in.

Text game

The Last Radio Show

Budget power, answer unknown call signs, and decide who is worth risking a rescue through the storm.

Text game

Pirate Survival: Sequence Legend

Manage supplies, recruit a crew, explore ruins, and ascend a mysterious sequence. Every choice redraws your route.

Text game

Seventh Code of Autumn Recruitment

A graduating senior receives a seventh-code offer from a company that doesn't exist. Each onboarding test accepted makes one classmate vanish from the campus recruitment list. Investigate node cards and a classmate relationship web; freely type company names or clue keywords to trigger verification. Phone notifications and campus surveillance dual interface; choosing who to verify first changes the order of disappearance; offer credibility shifts in real time. A 20-minute text loop with three endings.

Continue reading

Browse more articles
After a Team Vote, How Can Minority Views Still Shape the Story? — original editorial cover illustration
Relationships and Groups2026.10.07 · 18 min

After a Team Vote, How Can Minority Views Still Shape the Story?

After a three-to-two vote to change routes, let the decision take effect while preserving objections as concerns that can be checked, clearly assigned responsibilities, and conditions for further discussion. A fill-in meeting record can connect the losing vote to what happens next.

Who Can Take the Last Rope? Turning Team Inventory into Negotiable Authorization Rules — original editorial cover…
Resources and Constraints2026.10.07 · 18 min

Who Can Take the Last Rope? Turning Team Inventory into Negotiable Authorization Rules

Shared does not mean free to take. An authorization agreement card distinguishes ownership, temporary use, emergency exceptions, and retrospective approval. Taking the last rope requires explicit consent from both the custodian and the affected task lead; shortening the loan does not remove that requirement.

A creator turns material samples, lighting, and set models into executable style conditions.
Product workflow2026.09.26 · 16 min

After Choosing a Style, How to Write It for the Team: Turn References into Stable Text Constraints

After choosing a style, what you show the team is not the name of a reference work, but a text specification that can be checked item by item. The method is: first use one sentence to lock down the overall judgment of the style, then break down color tone, materials, light sources, and detail density into observable descriptions, and finally use a "can keep / can change" table to draw the boundaries of expression. Below, we walk through the fictional teaching example "Rainy Port Retro Style"; all names, numbers, and dialogue are fictional and do not correspond to any real project.

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.