How to Design a Cooking Revenge Story Game: Let Recipes Provide Clues, Not Prove Guilt
Using an original cooking-class story, this article unpacks recipe versions, shopping lists, tasting memories, and letters between collaborators. Let cooking shape the opportunities for investigation, and let evidence and explicit permission to publish determine the endings. Avoid treating taste or anger as grounds for a guilty verdict.

Taste Can Bring Back Memories, but It Cannot Determine the Truth
Cooking and revenge make for an easy opening with a certain elegance: one spoonful of a familiar soup, and someone who has not been seen in years puts down their spoon. But if the story immediately declares, “Only the person who stole the recipe would know this taste,” the investigation skips its most important step. The same recipe could have come from instruction, family sharing, adaptation, or independent experimentation. Familiarity does not mean guilt.
The original story game The Seventh Dish takes place in a cooking school that is about to close. Teacher Xu Wenxia discovers that the signature dish in a commercial cookbook closely resembles her mother's handwritten menu, while the only public credit goes to her mother's former business partner. Players help her organize the school and decide which materials to investigate, whom to invite for a tasting, and under what conditions to make their findings public.
The story can include anger and the urge for revenge, but it does not make poisoning, concealing allergens, or harming diners part of the gameplay. What is at stake is the right to credit, explain, and speak publicly.
Let Each Dish Answer a Different Question
The seven dishes should not amount to seven rounds of “get it right to gain a clue.” Instead, the first might establish which recipe version is involved, the second connect it to a purchasing date, the third ask where someone learned it, the fourth reveal a menu revision, the fifth seek permission to consult private correspondence, the sixth cross-check the information, and the seventh decide how to present the findings.
| Material | What it can support | What still needs checking |
|---|---|---|
| Handwritten menu | Someone once recorded this version | When it was written and how it later circulated |
| Shopping list | A particular ingredient was bought on a particular date | Who actually developed or used the recipe |
| A taster's recollection | The person remembers a similar taste | Whether the memory is accurate or influenced by prompts |
| Letters between collaborators | What was discussed about credit | Whether a reply was received and whether there were later agreements |
These materials can complement one another, but they cannot stand in for one another. A shopping list should not suddenly prove who has the right to credit, and a taster's emotional reaction cannot replace a clear account of what they know.
Use Cooking Choices to Change the Opportunities for Investigation
Players can recreate the old menu or use substitute ingredients available now. The recreation route helps with recipe comparisons, but may use up the limited shopping budget. The substitute route lets more people participate, but offers less of a basis for comparing flavors. Both routes should still leave written materials to investigate; players who skip a dish should not lose every path to the truth.
Before a tasting, explain the ingredients and respect a refusal. Someone who does not want to eat is not necessarily hiding something; they may simply be unable to eat a particular food. Players can instead show them the recipe, ask about the process, or agree to talk later. In this way, cooking provides a setting for characters to meet, not a tool for extracting a confession.
Investigation steps should also provide clear feedback. For example, if players find a menu that predates the commercial cookbook, they can first mark “this version existed earlier” as confirmed, then ask who had the right to make it public. Upgrading “I saw similar content” directly to “plagiarism is proven” means later choices rest on a verdict the author made on the players' behalf.
Make the Scope of Publication a Meaningful Choice
After obtaining her mother's private letters, Xu Wenxia may be eager to present them in full at the cooking school's final exhibition. Players can suggest first getting the relevant people's consent, publishing only the excerpts necessary to support the credit claim, or keeping the materials private and holding no public exhibition.
Publishing more should not automatically lead to a better ending. Full disclosure might also expose family secrets unrelated to the dispute; a limited account might take longer, but protect people who do not want to be drawn into it. The story should make these consequences clear rather than package all privacy as a free reward for “revealing the truth.”
Three Endings, Each Pursuing a Different Goal
“Credit Restored” requires mutually supporting materials and explicit permission to publish. The ending presents the corrected account alongside what remains uncertain. “Keep the Originals” has Xu Wenxia refuse to trade private letters for a victory; she organizes the menus and continues the negotiations. “Empty-Plate Exhibition” follows when players publicly accuse someone despite insufficient evidence: the audience remembers the argument, while the materials that could really clarify matters lose their credibility.
Reconciliation should not happen automatically over a single dish, and revenge should not be written as inevitably clever. Trace each ending back to the materials and permissions involved, and you can check whether the story rewards careful inquiry or merely louder accusations.
The school, recipes, and characters in this article are original fictional examples and do not constitute a judgment on any real dispute. When making a similar work, first spell out what each item of material can establish, then decide how cooking will bring about encounters, memories, and choices. That gives the mystery a basis players can look back on.






