Two Lighthouses, Only One Can Be Repaired First: Turning Scarcity into Trade-offs, Not Guesswork

When only one of two lighthouses can be repaired first, frame the choice as “Which need do we meet first, and how do we look after the other side?” Before players act, explain who needs each lighthouse, what waiting will cost them, when that loss will occur, and what limited alternative assistance is available. Players should be able to explain their priorities without guessing which answer the author approves of.

The following “Cape Bay Twin Lighthouses” scenario is entirely fictional and intended for teaching. It is not a real user case, a tested result, or a representation of DramaFork’s product features. The lighthouse and sailing rules serve narrative design purposes only and are not real-world navigation advice. The timeline, delivery deadline, and exhibition stall arrangements are all premises of this example.

The east lighthouse serves workshop cargo ships; the west lighthouse serves inter-island passenger ferries. Today, there is only one intact lamp wick and one repair crew. Repairing either lighthouse will use up the crew’s working hours for the day; the second wick will not arrive until noon tomorrow. The lighthouses have identical structures, and the wick cannot be divided. Under the announced sailing suspension rules, if a route’s lighthouse is unlit, that route will not operate tonight and will resume during daylight tomorrow.

If the cargo ship arrives tonight, materials can be ready before work begins tomorrow morning. If it arrives tomorrow morning, unloading, transfer, and preparation will take until noon, leaving the workshop idle for half a day. Once work resumes at noon, the afternoon provides enough time to finish this batch, so delivery can still be made by the agreed deadline tomorrow evening without borrowing materials. Borrowing only allows one process to start early, reducing some idle time; it cannot get the entire workshop started on schedule.

One night route will definitely be unavailable this round. Players must decide whether to preserve the workshop’s full production period tomorrow morning or the residents’ chance to attend tonight’s festival opening. Both needs are valid; they do not need to be converted into the same kind of score.

Identify the affected parties in the column headings, then compare them row by row across six required dimensions: immediate need, loss from waiting, loss timing and deadlines, alternative assistance, cost of assistance, and limits of assistance. The parties themselves do not count toward the six dimensions. The limits must state what the assistance still cannot resolve. Use the same dimensions for both sides so that one is not represented by specific people while the other is reduced to abstract numbers.

If residents arrive tonight, they can confirm the stall and take down their exhibit themselves, without the player handling either task. This example also includes a messenger who can deliver only one request before its submission window closes tonight. Both requests for assistance must be delivered by him, and the recipients have already agreed to the conditions in the table. Players can request help for the side that must wait, or leave the messenger unused, preserve tomorrow’s action, and accept the listed consequences of declining help.

Be specific about what “can wait”: repairs can be postponed, but some losses cannot be recovered. Repairing the other lighthouse tomorrow will not give residents another chance to join the chorus or reclaim a released stall. Being able to deliver on time does not mean the workshop has lost no production time.

After displaying the briefing, first ask players to choose the repair order, then whether to arrange assistance. Keeping these as separate steps distinguishes their priorities from the obligations they are willing to take on for those who must wait.

You can use the following text directly before the choice:

Only one lighthouse can be lit tonight. Repair the east lighthouse, and the workshop starts on schedule tomorrow morning. Residents arrive tomorrow morning and miss the opening; unless you request a hold on their stall, they cannot exhibit tomorrow either, though they can still join other activities. Repair the west lighthouse, and residents reach the opening and confirm their own stall. The workshop’s materials reach port tomorrow morning and are ready at noon. Without borrowing, the workshop is idle for half a day, but afternoon processing still leaves enough time for delivery tomorrow evening. The messenger can request borrowed materials or a stall hold for the side that must wait. Borrowing only starts one process early; holding the stall only preserves tomorrow’s exhibit. Only if you request assistance must you spend one action tomorrow returning an equal quantity of materials or taking down the exhibit on the residents’ behalf. Decline assistance, and you keep that action.

The parallel options are “Repair the east lighthouse first so work starts on schedule tomorrow morning” and “Repair the west lighthouse first so residents attend tonight’s opening.” Do not label one “Help the residents” and the other “Care only about business,” using wording to impose a moral ranking on the player.

Consider the west lighthouse route: the player wants residents to attend the one-time opening and also sends the messenger to borrow materials. Tonight, the west lighthouse is lit and residents board the ferry. Tomorrow morning, the workshop uses surplus materials to begin one process; the others begin once materials are ready at noon, and the batch is finished in the afternoon. Borrowing reduces the number of idle processes without getting the whole workshop started on schedule. On-time delivery is not a benefit obtained only through borrowing, either.

“Return borrowed materials” appears among tomorrow’s tasks and uses the one action already disclosed. After the second wick arrives at noon, the player can arrange repairs to the east lighthouse. Without borrowing, the workshop remains idle for half a day, resumes work at noon, and still delivers as agreed, while the player keeps tomorrow’s action. This route also needs to be written in full.

The opposite choice is to repair the east lighthouse first and ask the venue to hold the stall. Materials arrive tonight, and the workshop starts on schedule tomorrow morning. Residents arrive tomorrow morning and can still set up their exhibit, but the opening chorus has ended. The player takes down the exhibit on their behalf tomorrow. Residents may express gratitude for the stall hold, or regret about what they missed. If no hold is requested, the stall is released tonight. Residents cannot exhibit tomorrow but can still participate in other activities; the player does not have to take down the exhibit and keeps tomorrow’s action.

Players concerned with preserving the full production period can explain why they repaired the east lighthouse first. Players who value a shared event that cannot be repeated can explain why they chose the west lighthouse. Both justifications come from the briefing shown before the choice, without waiting for the ending to reveal a secret.

If one route performs better against every stated objective, review the premises. For example, if borrowing completely eliminates lost working time and carries no burden, repairing the west lighthouse would almost satisfy both sides at once. You can honestly present that as a straightforward scheduling problem. If you want to retain the dilemma, specify in advance which processes borrowed materials can support, rather than secretly punishing players who choose the west lighthouse.

Players may also propose dividing the wick. The previously stated requirement to install it intact is enough to explain why this will not work. If other solutions are allowed, establish their resource costs and the needs they can meet before players commit to acting. Do not add restrictions on the fly after they try.

A common failure is an ending that suddenly declares, “The lighthouse you left unrepaired actually served a more important purpose,” and uses that revelation to declare that the player has failed. If a hidden purpose would change priorities, provide discoverable clues and opportunities to investigate beforehand. Otherwise, an information gap cannot fairly be written as an error of judgment.

Another failure is making everyone on the side not prioritized turn against the player. Disappointment should correspond to known losses: the workshop can ask about material preparation, and residents can regret missing the chorus. If a breakdown in cooperation is introduced, relevant promises or relationship conditions should be established beforehand; it should not be added as an automatic punishment.

Before submitting the draft, hide the lighthouse names and check three things: Can you explain reasons for prioritizing either side? Can you state what those waiting lose and when? Can you identify what assistance still cannot solve, what happens without it, and whether the action is preserved? If not, add information rather than more emotional dialogue.

This briefing suits scenes with conflicting needs, insufficient resources, and further actions still available. If the story is about finding the only viable solution, provide clues for identifying it. If it emphasizes unexpected unknowns, make clear where those unknowns lie. Do not package either kind of problem as a value trade-off and then require players to guess the one correct ending.