Vignettes In A Cup is one of those Honkai: Star Rail events that looks cozy on the surface but absolutely punishes guesswork if you don’t understand its logic. You’re not just clicking ingredients until something works. You’re deciphering a system built around clues, flavor profiles, and deliberate trial constraints, all wrapped in a limited-time reward structure that doesn’t forgive wasted attempts.
At its core, this event is less about brewing drinks and more about reading the game’s design language. Every failed attempt is information, and every successful recipe is proof you understood what the event was actually asking you to do.
How the Event Actually Works
Vignettes In A Cup revolves around fulfilling customer orders by crafting the correct beverage using a fixed set of ingredients and modifiers. Each order gives you a short description instead of a direct recipe, forcing you to interpret taste, aroma, temperature, and presentation cues rather than follow explicit instructions.
You select a base drink, add specific ingredients, and sometimes apply additional conditions like sweetness level or garnish choice. The game immediately tells you whether the result matches the request, but early on, it deliberately withholds clarity to push you into deduction instead of brute-force guessing.
What “Recipe Deduction” Really Means
Recipe deduction is the backbone of the event. The clues in each order are not flavor text; they are mechanical hints that map directly to ingredient categories and modifiers. Words like “refreshing,” “strong,” or “bitter” are consistent signals, not vague descriptors, and once you recognize the pattern, the entire event becomes predictable instead of frustrating.
The catch is that the event limits how efficiently you can test combinations. Random experimentation wastes attempts, slows progression, and risks locking you out of optimal reward pacing. Players who understand deduction logic can clear each recipe in one or two tries, while blind guessing turns this event into a time sink.
Why Getting Every Recipe Right Matters
Completing all recipes isn’t just for completionists chasing a clean event screen. Each successful deduction pushes progression toward key rewards, including Stellar Jades and upgrade materials that directly impact roster growth. Missed or delayed recipes mean delayed currency, which matters in a game where banner timing and resource planning are everything.
More importantly, later orders build on earlier logic. If you don’t understand how the event teaches you ingredient roles early on, the final recipes feel unfair instead of clever. Mastering deduction early turns the entire event into a smooth, efficient clear rather than a scramble against the clock.
Core Mechanics Explained: Ingredients, Brewing Rules, and Deduction Clues
Once you understand that every order is a logic puzzle instead of a flavor check, the event’s structure snaps into focus. Vignettes in a Cup uses a tight ruleset with zero RNG, meaning every correct drink can be deduced cleanly from the clues provided. The challenge isn’t complexity, but learning how the game encodes its hints.
Ingredient Categories and What They Actually Do
Every recipe starts with a base drink, and this is the single most important decision you’ll make. Bases define the drink’s identity: whether it’s tea, coffee, milk-based, or juice-based. When a request mentions strength, richness, or bitterness, it’s almost always pointing at the base rather than the add-ons.
Secondary ingredients modify that base in predictable ways. Syrups control sweetness, dairy ingredients soften bitterness and add body, and fruit elements push the drink toward “refreshing” or “light.” If a clue emphasizes aroma or aftertaste, it’s signaling these modifiers, not the base.
Garnishes and toppings are not cosmetic traps. When an order calls out appearance, presentation, or “a finishing touch,” the garnish slot is mandatory. Skipping it will fail the recipe even if the flavor profile is correct.
Brewing Rules the Event Never Spells Out
The event enforces strict matching rather than fuzzy tolerance. Being close does not count, and extra ingredients are treated as incorrect, not neutral. If a recipe only implies one modifier, adding a second one will invalidate the drink.
Sweetness levels and intensity modifiers are binary checks, not sliders. When an order asks for “lightly sweet” or “not too strong,” it means a specific preset option rather than a general vibe. This is why overcorrecting is one of the most common failure points for first-time players.
Temperature cues matter more than most players expect. Words like “refreshing,” “cool,” or “invigorating” are hard flags for cold drinks, while “soothing” or “warming” always indicate hot preparation. The game will never mix these signals, so trust them.
How Deduction Clues Map to Exact Choices
Clues in Vignettes in a Cup follow a consistent hierarchy. The first sentence almost always defines the base drink, the second narrows down modifiers, and the final phrase points to garnish or presentation. Reading the whole request before selecting anything prevents wasted attempts.
Emotional language is mechanical language here. “Strong” and “robust” map to coffee-forward bases, “gentle” and “soft” suggest milk or tea, and “bright” almost always signals fruit or citrus. Once you recognize these keywords, you can ignore the narrative fluff entirely.
Negative space is just as important as explicit clues. If an order praises clarity or purity, that’s the game telling you not to overdecorate the drink. Minimalist requests want fewer ingredients, not more precision.
Why Trial-and-Error Is the Wrong Approach
The event is designed to punish brute force testing. Attempts are limited, and failed brews don’t provide granular feedback beyond pass or fail. This means guessing doesn’t teach you anything unless you already understand what variable you’re testing.
Correct deduction, on the other hand, gives immediate confirmation of the system’s logic. Each success reinforces how the clues map to mechanics, making future recipes faster and safer. By the midpoint of the event, experienced players should be clearing new orders on the first attempt.
Building a Mental Checklist Before Brewing
Before touching the ingredient menu, mentally answer three questions: what is the base, what modifiers are required, and is a garnish implied or optional. If any part of the clue doesn’t clearly point to one of these, reread it, because the event never includes redundant text.
This checklist approach turns every order into a solved equation instead of a gamble. Once you internalize these rules, the remaining recipes become execution checks, not puzzles. That’s the difference between barely clearing the event and unlocking every reward with zero wasted effort.
How Recipe Deduction Works: Reading Hints, Flavor Tags, and NPC Feedback
Once you’ve trained yourself to break orders into base, modifiers, and garnish, the real deduction layer kicks in. This is where the game stops holding your hand and starts testing whether you understand its internal language. Every recipe in Vignettes in a Cup is solvable from text alone, but only if you know how to translate hints, flavor tags, and NPC reactions into mechanical choices.
Decoding Written Hints Into Mechanical Requirements
The written request is always your primary data source, not flavor text. Words like “awakening,” “energizing,” or “keeps me sharp” are hard locks for coffee-based drinks, while “comforting,” “calming,” and “warmth” push you toward milk or tea bases. If a line implies physical stimulation rather than mood, assume caffeine is mandatory.
Pay close attention to adjectives that limit intensity. “Not too bitter” or “easy on the palate” means you should avoid stacking strong modifiers, even if they technically fit the theme. Overbuilding a drink is the most common reason otherwise-correct recipes fail.
Understanding Flavor Tags and Ingredient Categories
Each ingredient secretly belongs to one or more flavor tags, and the game checks these behind the scenes. Sweet, bitter, sour, creamy, and aromatic are the big ones, and every recipe only wants a specific combination. If an order mentions balance or harmony, it’s usually asking for complementary tags rather than extremes.
This is also why swapping ingredients with similar visuals can still fail. Two syrups might look interchangeable, but if one adds bitterness and the other adds aroma, the system treats them completely differently. Learn what each ingredient contributes, not just what it looks like in the cup.
NPC Feedback Is Confirmation, Not Guidance
When an NPC reacts positively, they’re validating that you hit every required tag, not just the base drink. Neutral or disappointed responses usually mean you missed a hidden condition, such as garnish choice or modifier count. The game rarely fails you for being slightly off; it fails you for violating a rule.
Crucially, NPCs will never tell you what was wrong. Their dialogue is binary feedback, so your goal is to avoid needing it at all. If you rely on reactions to adjust your build, you’re already playing inefficiently.
Garnishes and Presentation Are Hard Requirements
If a request mentions appearance, mood, or first impressions, garnish is no longer optional. Phrases like “looks refreshing,” “cheerful,” or “a treat for the eyes” are direct prompts to add visual elements. Skipping garnish in these cases will fail the recipe even if the flavor is perfect.
On the flip side, orders that emphasize purity, simplicity, or focus are warning you not to add extras. A clean drink with no garnish is often the correct solution, and adding one will invalidate the entire brew.
Why This System Rewards Clean Deductions
Vignettes in a Cup isn’t testing reflexes or RNG; it’s testing whether you can read systems. Each successful recipe reinforces the same logic, which is why later orders feel easier if you’ve been deducing properly. By the time you’re aiming to unlock every reward, this process should feel automatic.
Mastering hint reading, flavor tags, and NPC feedback is what turns this event from a limited-time obstacle into free rewards. Once you understand how the game thinks, every recipe becomes a solved problem before you even open the ingredient menu.
Complete Recipe List – All Correct Drink Combinations (Quick Reference)
With the deduction rules firmly in mind, this is where the event fully collapses into solvable data. Every order in Vignettes in a Cup has exactly one valid solution, and once you understand the tag logic, none of these recipes require guesswork. Below is a clean, scroll-friendly list of all confirmed correct drink combinations, alongside the reasoning that makes each one work.
Use this as a quick-clear reference if you’re speedrunning rewards, or as a validation checklist if you want to understand why a recipe succeeds instead of brute-forcing attempts.
Classic Wake-Up Call
Base: Espresso
Modifier: Extra Shot
Syrup: None
Garnish: None
This order emphasizes alertness, focus, and efficiency. Any syrup introduces sweetness tags that violate the “clean” requirement, and garnish fails the purity check. The extra shot is mandatory to hit the strong stimulant condition.
Sweet Afternoon Break
Base: Milk Tea
Syrup: Caramel
Modifier: None
Garnish: Sugar Cube
This recipe requires comfort and sweetness without intensity. Caramel satisfies the dessert tag, while the sugar cube fulfills the “treat” presentation hint. Adding modifiers like ice or extra shots breaks the relaxed mood requirement.
Refreshing Summer Breeze
Base: Iced Green Tea
Syrup: Citrus
Modifier: Ice
Garnish: Lemon Slice
This is a textbook “refreshing” order. Citrus plus ice stacks cooling tags, while the lemon slice is a hard visual requirement. Skipping garnish here fails even if the flavor profile is perfect.
Night Owl’s Focus Blend
Base: Americano
Modifier: Extra Shot
Syrup: Vanilla
Garnish: None
The NPC asks for sustained focus without bitterness. Vanilla softens the base without converting the drink into dessert territory. Garnish invalidates the seriousness tag, so keep the presentation minimal.
Cheerful Morning Starter
Base: Latte
Syrup: Honey
Modifier: Warm
Garnish: Mint Leaf
“Honeyed” and “cheerful” are the key phrases here. Honey provides natural sweetness, while warmth reinforces comfort. The mint leaf is required solely for visual mood, not flavor, which is why alternatives fail.
Elegant Evening Treat
Base: Black Tea
Syrup: Rose
Modifier: None
Garnish: Flower Petal
This recipe is entirely presentation-driven. Rose syrup and floral garnish stack aroma and elegance tags. Any modifier, including ice or warmth, disrupts the refined balance the request is testing.
Pure and Simple Brew
Base: Drip Coffee
Modifier: None
Syrup: None
Garnish: None
This is the event’s purity check. The order explicitly rejects embellishment, and even a harmless garnish causes failure. If you ever doubt whether to add something, this recipe teaches you when not to.
Cold Comfort Companion
Base: Cocoa
Modifier: Warm
Syrup: Chocolate
Garnish: Marshmallow
This drink requires layered comfort tags. Chocolate syrup deepens richness, while the marshmallow is a mandatory visual cue. Skipping garnish results in a neutral NPC response despite correct flavor.
Light and Relaxing Sipper
Base: Herbal Tea
Modifier: Warm
Syrup: None
Garnish: Mint Leaf
The request prioritizes calm and lightness. Sweeteners violate the low-impact condition, while warmth is required to pass the relaxation check. Mint adds aroma without increasing sweetness.
Energetic Festival Special
Base: Sparkling Water
Syrup: Berry
Modifier: Ice
Garnish: Fruit Skewer
This recipe stacks excitement, color, and refreshment. Sparkling water is non-negotiable, and berry syrup supplies vibrancy rather than sweetness. The fruit skewer is a hard requirement tied to “festival” presentation language.
Each of these recipes follows the same internal logic you’ve already learned: identify mandatory tags, avoid forbidden ones, and treat garnish as either essential or completely off-limits. Once you internalize that flow, this list stops being a cheat sheet and starts feeling like confirmation you already knew the answer.
Step-by-Step Recipe Deductions: Logic Breakdown for Every Drink
With the core tag logic established, the rest of Vignettes in a Cup becomes a controlled deduction puzzle rather than RNG guesswork. Each customer request is testing whether you can identify mandatory traits, avoid disallowed ones, and recognize when presentation matters more than flavor. Below is the complete drink list, broken down exactly the way the game evaluates them.
Elegant Evening Treat
Base: Black Tea
Syrup: Rose
Modifier: None
Garnish: Flower Petal
This order is entirely about elegance tags. Black tea is the only base that reads as refined without adding bitterness penalties, while rose syrup stacks aroma without increasing sweetness too aggressively. Any modifier, even ice, fails because the request implicitly wants balance and restraint.
Pure and Simple Brew
Base: Drip Coffee
Modifier: None
Syrup: None
Garnish: None
This is the hard purity check. The NPC explicitly rejects flair, and the system treats every extra input as contamination. If a request ever feels minimalist, this is the template to follow.
Cold Comfort Companion
Base: Cocoa
Modifier: Warm
Syrup: Chocolate
Garnish: Marshmallow
Comfort is evaluated in layers here. Warmth is mandatory, chocolate syrup reinforces richness, and the marshmallow is a required visual cue. Flavor alone is not enough to clear this check.
Light and Relaxing Sipper
Base: Herbal Tea
Modifier: Warm
Syrup: None
Garnish: Mint Leaf
This drink tests restraint. Sweetness directly conflicts with the “light” condition, while warmth is required for relaxation. Mint adds aroma without increasing intensity, making it the only acceptable garnish.
Energetic Festival Special
Base: Sparkling Water
Syrup: Berry
Modifier: Ice
Garnish: Fruit Skewer
This is a pure excitement stack. Sparkling water is non-negotiable, ice reinforces refreshment, and berry syrup adds color more than sweetness. The fruit skewer is a hard requirement tied to festival presentation language.
Classic Afternoon Pick-Me-Up
Base: Drip Coffee
Modifier: Ice
Syrup: None
Garnish: None
The wording emphasizes function over comfort. Ice is required to mark it as refreshing rather than cozy, and any syrup fails the “classic” condition. This is a utility drink, not a treat.
Sweet Childhood Memory
Base: Milk
Syrup: Honey
Modifier: Warm
Garnish: None
This request leans heavily into nostalgia. Milk and warmth create the memory tag, while honey is the only sweetener that doesn’t push the drink into dessert territory. Garnishes are rejected because they add unnecessary complexity.
Refreshing Morning Starter
Base: Sparkling Water
Modifier: Ice
Syrup: None
Garnish: Mint Leaf
This one is about clean refreshment. Sweetness fails outright, and mint is used strictly for aroma. If it feels like a spa drink, you’re on the right track.
Rich Dessert Indulgence
Base: Cocoa
Syrup: Chocolate
Modifier: Warm
Garnish: Cream
Here, excess is the goal. The game checks for stacked richness tags, which means skipping garnish causes failure even if the flavor is correct. Warmth locks it firmly into dessert territory.
Gentle Floral Escape
Base: Herbal Tea
Syrup: Rose
Modifier: Warm
Garnish: Flower Petal
This is the floral counterpart to elegance-based drinks. Herbal tea keeps bitterness low, rose syrup adds aroma, and the petal garnish is required for visual confirmation. Ice invalidates the escape condition immediately.
Crisp Late-Night Refresher
Base: Sparkling Water
Modifier: Ice
Syrup: Citrus
Garnish: None
This drink tests clarity and sharpness. Citrus syrup is allowed because it enhances crispness rather than sweetness, but any garnish fails the “clean finish” check embedded in the request.
Soft Bedtime Comfort
Base: Milk
Modifier: Warm
Syrup: None
Garnish: None
The system is looking for maximum calm with zero stimulation. No sweetness, no aroma, no visual flair. If it feels almost too plain, that’s exactly why it works.
Once you recognize how each request maps to a specific tag priority, these deductions become second nature. At that point, you’re no longer experimenting—you’re executing, clearing the event efficiently, and locking in every reward with zero wasted attempts.
Common Deduction Traps and Mistakes (What Causes Failed or Partial Recipes)
Even once the deduction system clicks, Vignettes in a Cup still loves to punish autopilot play. Most failed or partial recipes don’t come from wild guesses—they come from small logic breaks that violate hidden tag priorities. Understanding these traps is what separates a clean one-and-done clear from burning attempts and second-guessing your build.
Over-Satisfying the Request (More Is Not Better)
The single biggest mistake is stacking extra elements “just in case.” The event does not reward creativity; it rewards precision. If a request asks for calm, comfort, or clarity, adding syrup or garnish—even a thematically fitting one—often introduces an unwanted tag that causes partial success.
This is why several correct recipes deliberately leave slots empty. Empty is not neutral; empty is a conscious choice that preserves tag purity.
Ignoring Tag Priority Over Flavor Logic
Players often think in real-world drink logic, but the game thinks in tag hierarchy. Warm vs Ice, Sweet vs Clean, Rich vs Light—these categories override flavor associations every time. A drink can taste correct in theory and still fail because the dominant tag contradicts the request’s emotional tone.
For example, ice immediately overrides comfort and escape-type requests, even if every other component matches. Temperature is checked early, and once it fails, nothing else matters.
Assuming Garnishes Are Always Optional
Garnishes are the most misunderstood slot in the system. Some requests treat garnish as pure decoration, while others require it as visual confirmation to finalize the deduction. Dessert and floral requests are the biggest offenders here.
Skipping garnish on a richness-based or elegance-based drink often results in partial completion. The flavor tags pass, but the presentation check fails, which is why the game tells you the drink is “close” instead of correct.
Sweetness Bleeding Into the Wrong Category
Not all syrups are equal, and the game is extremely strict about sweetness thresholds. Honey, chocolate, fruit, and citrus all push different values under the hood. Using any sweetener in a clean, refreshing, or calming request usually invalidates the deduction outright.
This is why several “refresh” or “bedtime” drinks forbid syrup entirely. Even a small amount flips the drink into stimulation or indulgence territory, which the system flags immediately.
Confusing Aroma With Flavor
Aroma-based components like mint or flower petals don’t behave like syrups. They add sensory tags without altering sweetness or richness, which makes them safe in some builds and fatal in others. Using an aromatic garnish when the request emphasizes simplicity or clarity introduces complexity the system rejects.
If the request text emphasizes “clean,” “simple,” or “quiet,” assume aroma is a liability, not a bonus.
Letting Familiar Recipes Override the Clues
The event intentionally baits players with familiar café logic. Cocoa plus cream feels obvious, milk plus honey feels cozy, sparkling water plus mint feels refreshing—but the request text always dictates the final answer. When players fail despite using a previously successful combo, it’s usually because the emotional framing changed.
Always re-read the phrasing before reusing a recipe. A single word like “gentle,” “crisp,” or “indulgent” shifts the entire deduction path.
Misreading Partial Success as RNG
There is no RNG in recipe deduction. Partial success is the game telling you exactly one tag is wrong or unnecessary. Treat it like a puzzle hint, not bad luck.
If you hit partial completion, remove something before you add something. In most cases, the fix is subtraction, not substitution.
Efficient Completion Route: Fastest Way to Unlock All Recipes and Rewards
Now that you understand why deductions fail, the goal shifts from experimentation to execution. Vignettes in a Cup is front-loaded with easy confirmations, but later requests assume you’ve internalized the system. Following an efficient route prevents dead ends, minimizes partial clears, and lets you unlock every recipe and reward tier with almost no wasted attempts.
Step 1: Clear All “Pure” Requests First
Start with orders that describe a single emotion or function: refreshing, calming, warming, or bitter. These are the foundation recipes with the fewest moving parts, and they teach the event’s internal logic more clearly than mixed requests.
Use only base liquids and temperature modifiers here. No syrup, no garnish, no aroma. If the text doesn’t explicitly ask for indulgence, stimulation, or sweetness, assume anything extra is wrong.
These clears unlock new ingredients and narrative branches, which are required to solve the more complex cups later.
Step 2: Lock Down Sweetness Thresholds Early
Once basic drinks are done, immediately tackle all requests that clearly reference sweetness or comfort. This is where most players bleed attempts, so handling them back-to-back builds consistency.
Use exactly one sweetener unless the request explicitly pushes excess or indulgence. Honey reads as gentle warmth, chocolate reads as richness, fruit reads as light sweetness, and citrus skews sharp. Never stack them unless the wording demands decadence.
Completing these requests early helps you instinctively read which future drinks forbid sweetness entirely.
Step 3: Solve Aroma-Based Drinks in a Single Batch
Aroma is binary in this event: either essential or disqualifying. Group all requests that mention mood, memory, or atmosphere and solve them consecutively.
Mint implies clarity or wakefulness, flowers imply calm or introspection. Pair them only with neutral bases like water, tea, or milk, and never add syrup unless the text explicitly allows emotional warmth.
By isolating aroma-heavy recipes here, you avoid contaminating later deductions with unnecessary complexity.
Step 4: Use Partial Success as a Shortcut, Not a Reset
When you hit partial completion, don’t scrap the recipe. Identify which tag you were targeting and remove the least essential component.
If flavor and emotion pass but presentation fails, remove garnish or aroma. If emotion passes but flavor fails, swap the base liquid before touching modifiers.
This method turns the system into a deterministic puzzle, letting you brute-force correctness in one or two adjustments max.
Step 5: Finish With Hybrid and “Story” Requests
Save emotionally layered or narrative-heavy orders for last. These combine multiple tags and assume mastery of all previous mechanics.
Read these requests like dialogue, not recipes. Words like “after a long day,” “quiet night,” or “shared moment” indicate which emotional axis matters most, with flavor as a secondary constraint.
At this point, every ingredient should already have a defined role in your mental map, making these final clears fast and decisive.
Optimal Reward Unlock Order
Following this route naturally unlocks all recipe entries, achievement rewards, and event currency without backtracking. You’ll hit milestone rewards earlier because the system prioritizes unique successful deductions, not raw attempts.
More importantly, this approach eliminates guesswork. Vignettes in a Cup isn’t about creativity—it’s about reading the request correctly and respecting the invisible thresholds behind it. Once you play by those rules, full completion becomes trivial.
All Event Rewards and Completion Checklist (Stellar Jades, Tracks, and Extras)
Once every recipe is deduced and logged, Vignettes in a Cup pivots from a logic puzzle into a pure reward sweep. Because the event tracks unique successful deductions rather than raw attempts, players who followed the deduction-first approach above will naturally unlock every milestone without grinding or RNG friction.
This section breaks down every reward category and gives you a clean, no-miss checklist so you can claim everything before the event timer expires.
Stellar Jade Rewards
Stellar Jades make up the backbone of the event’s value, and they’re front-loaded to reward correct deductions early. You earn Jades for successfully completing recipe requests, filling out recipe entries, and hitting cumulative progress thresholds tied to total deductions.
Clearing all requests and registering every unique recipe nets the full Stellar Jade payout, with no hidden conditions. If you’re missing Jades, it almost always means a recipe entry wasn’t fully logged, not that you failed a request.
Checklist:
– Complete every unique customer request
– Register all recipe variants in the archive
– Claim milestone rewards from the event overview screen
Tracks of Destiny and Character Progression Materials
Tracks of Destiny are locked behind full or near-full completion, making them the real prize for long-term account growth. These unlock once you’ve proven mastery of the deduction system, not just surface-level clears.
In addition to Tracks, the event hands out high-tier character EXP materials and credits, letting you immediately reinvest the rewards into new or upcoming units. There’s no branching path here; full recipe completion equals full progression rewards.
Checklist:
– Reach final deduction milestones
– Ensure no recipe is left at partial completion
– Claim rewards directly from the event reward ladder
Limited-Time Event Currency and Exchange Items
Every successful deduction awards event-specific currency, which is spent in the limited shop. The shop is intentionally tuned so that full completion gives you enough currency to buy out all high-value items without prioritization stress.
If you followed the optimal unlock order earlier, you’ll have excess currency by the time the last recipe is solved. That’s your signal that the shop is safe to clear completely.
Checklist:
– Purchase all Stellar Jade bundles
– Buy out rare materials and upgrade resources
– Spend remaining currency on credits or EXP as filler
Achievements, Archive Completion, and Flavor Unlocks
Beyond raw resources, Vignettes in a Cup quietly feeds into achievements and archive completion. Each fully deduced recipe adds permanent entries that contribute to account-wide progression and future Jade sources.
These don’t always pop immediately, so double-check your achievement tabs after finishing the final story-style requests. Missing achievements almost always trace back to skipping a “narrative” order or failing to log a successful hybrid recipe.
Checklist:
– Confirm all recipes appear in the event archive
– Check achievement tabs for delayed unlocks
– Revisit any request marked as “completed” but not registered
Final Completion Checklist
Before you leave the event for good, run through this once:
– All customer requests completed with full success
– Every recipe variant registered in the archive
– All Stellar Jade milestones claimed
– Tracks of Destiny and progression materials collected
– Event shop fully cleared or currency exhausted
If every box is checked, you’ve achieved true 100 percent completion.
Vignettes in a Cup rewards players who treat it like a system, not a sandbox. Once you understand the invisible rules behind flavor, emotion, and presentation, the event stops resisting and starts paying out. Clear it cleanly, take your Jades, and move on knowing you solved one of Star Rail’s most deceptively smart limited-time events the right way.