When an Option Is Disabled, Explain Whether Its Conditions Can Change

When the option to borrow a boat for a voyage is disabled, explain three things together: what is blocking it, whether the player can change that, and whether the restriction affects this way of obtaining a boat or the entire voyage. For removable restrictions, give an action; for story-stage restrictions, give a point at which to return; for irreversible restrictions, define what has become unavailable. Simply saying “Requirements not met” leaves players guessing whether they should take action, wait, or abandon the route.

The following example, Letters from Fog Harbor, is a fictional teaching scenario. Its characters, conditions, and dialogue are original creations. It is not a real user case, does not present tested results, and does not represent DramaFork product features.

In the story, a messenger named A-Cheng needs to reach North Island. The option at the docks is “Borrow a boat from its owner and travel to North Island.” The owner requires a letter of guarantee, while harbor rules stipulate that voyage registration begins only after the council meeting ends. The player may also have previously handed this boat over to the rescue team, making it unavailable to borrow for the rest of this playthrough.

All three obstacles can gray out the button, but they require different judgments from the player. Without a letter of guarantee, the player can seek a guarantor. Before registration opens, finding more guarantors will not enable an early departure. Once the boat has been handed over, waiting longer will not bring it back. The copy must reflect the actual rules, rather than merely deliver a refusal in the character’s voice.

“Ask to borrow the boat” and “Set sail immediately” also need to be separated. If the owner allows the player to discuss borrowing first, the harbor’s closure should restrict departure without disabling that conversation. This article assumes the option completes both borrowing and departure in one step, so both conditions must be met before it becomes selectable. If your story divides these into two steps, explain the restrictions separately.

It is especially important to identify exactly what is permanently unavailable. “This boat cannot be borrowed during this playthrough” does not mean “You can never reach North Island.” Unless the other routes have also closed, do not prematurely describe the loss of one opportunity as the ending of the entire story.

To classify a restriction, first ask: does the current story state offer an action the player can take to meet the missing requirement? If so, describe it as removable. If it requires passing a specific story milestone, describe it as a story-stage restriction. Only call it irreversible when there is no way to restore the opportunity during this playthrough. Here, “this playthrough” means continuing from the current choices; it excludes loading a save and choosing differently.

“Removable” does not mean success is guaranteed. If the lighthouse keeper may refuse to act as guarantor because of earlier choices, do not write “Talk to him to unlock this option.” Retain conditional wording such as “request” and “if approved,” and check whether other guarantors exist. If the request has been refused and there is no alternative source, this restriction is no longer removable.

A story-stage restriction does not mean asking players to sit at the interface and wait for time to pass. In this example, registration opens when the council meeting storyline is complete, so state that milestone. Unless the story actually uses elapsed time as a condition, “Try again later” provides no useful direction.

For irreversible restrictions, avoid vague reassurance. “There may still be a chance” encourages players to keep searching for a solution that does not exist. A character may express regret, but the rule explanation should clearly state that the opportunity to borrow this boat has ended for this playthrough.

Authors can copy the following card for each disabled option. It places the basis for the decision alongside the promises readers will see, making it easier to check each item against the script.

When both conditions are unmet, do not write only “You can set sail once you obtain a letter of guarantee.” That presents one requirement as the complete set. A more complete message is: “You still need a letter of guarantee, and voyage registration has not opened. You can request a guarantee now; return to the docks after the council meeting ends.” If the prompt area cannot fit that explanation, use “Guarantee missing; registration not yet open,” then explain both actions in the adjacent description.

If the boat has already been handed over to the rescue team, lead with the reason for the permanent closure. Emphasizing the letter of guarantee at that point could make players think completing the paperwork would still help. The other conditions can remain on the author’s card. Readers only need to know that this boat can no longer be borrowed and which alternative routes remain possible.

The card should also specify when to reassess the copy: after obtaining the letter of guarantee, finishing the council meeting, and handing over the boat, check the corresponding message. This is a review task for the author and should not be described as a mechanism the platform performs automatically.

First, follow the branch in which the boat is retained. When A-Cheng first arrives at the docks, he has no letter of guarantee and the council meeting has not ended, so both restrictions appear. After he obtains a guarantee at the lighthouse and returns to the docks, the message should change to: “You have obtained a guarantee, but voyage registration has not opened. You can register after the council meeting ends.” The old “A letter of guarantee is missing” message must be removed.

After the council meeting ends, the option should become selectable if the script introduces no new obstacles. Do not suddenly require a travel permit that has never been mentioned. If a new conflict really does arise, explain the change through a new story event so players understand what happened to the rules, rather than suspecting their earlier efforts have been erased.

Next, follow the branch in which the boat is handed over. Even if A-Cheng later obtains a guarantee and completes the council meeting storyline, the boat-borrowing option remains disabled because the boat has been handed over. An alternative can read “Ask whether the merchant ship will take you aboard,” but not “Take the merchant ship and you will reach your destination,” unless the subsequent requirements have actually been met.

This walkthrough checks consistency between the copy and the story’s rules. It does not demonstrate that players actually understand the text or establish its effect on their experience. At each milestone, authors can hide their story notes, read only the text beside the option, and try to answer where to go next, what they are waiting for, and which efforts are no longer useful.

If players have already seen the opportunity to borrow the boat, or the story has explicitly encouraged them to do so, retaining the disabled option can explain why that opportunity disappeared. If the route has never been revealed and is irrelevant to the current decision, it can remain hidden for now. Hiding it, however, cannot substitute for explaining a change to a known route.

A permanently closed option does not have to occupy the action area indefinitely. It can become a record of the outcome: “You handed the boat over to the rescue team.” Display the routes players can still attempt in the choice area. This preserves the consequences of the earlier decision without requiring players to repeatedly read the same unavailable option.

When suspense is involved, the explanation can focus on the action required. For example, “You must first gain the boat owner’s approval” need not reveal the owner’s hidden identity, but it should still provide a known way to approach them. If the author deliberately designs unknown conditions, acknowledge that exploration is needed here rather than pretending to have already provided a clear way to remove the restriction.

Before submitting the script, remove unsupported uses of “all you need to do,” “later,” and “forever,” then consult the condition card to restore precise wording. Good disabled-option copy lets players distinguish what is worth doing now, when it is worth returning, and which choice has already left its consequences on the story in this playthrough.