Chef is one of Risk of Rain 2’s most unusual survivors, blending absurd presentation with deceptively deep mechanics. On the surface, he’s a walking kitchen appliance lobbing ingredients at monsters, but under the hood he’s a high-skill, cooldown-driven DPS survivor built around positioning, timing, and smart ability sequencing. Unlocking him isn’t just a checklist task either, and the game expects you to understand its systems before it hands him over.
What makes Chef special is how different he feels from the base roster. His kit emphasizes sustained damage over burst, wide hitboxes over precision shots, and careful cooldown management instead of raw mobility. If you enjoy survivors like MUL-T or Acrid who reward planning and spatial awareness, Chef fits squarely into that niche.
Why Chef Is Locked Behind Seekers of the Storm
Chef is exclusive to the Seekers of the Storm DLC, and there’s no workaround or base-game method to unlock him. The DLC introduces a new progression path, new environments, and specific event triggers that simply do not exist in vanilla Risk of Rain 2. Without the expansion installed and active, the unlock condition for Chef never spawns, even if you meet every other requirement.
Seekers of the Storm also adds several mechanics that directly tie into how Chef is unlocked. These include DLC-specific stages, interactables, and enemy behaviors that the unlock sequence relies on. This is similar to how Survivors of the Void gated Railgunner and Void Fiend behind Void Locus progression, ensuring players engage with the DLC’s content instead of brute-forcing an unlock in early runs.
What the Game Expects Before You Attempt the Unlock
Before going for Chef, you should already be comfortable clearing mid-to-late loop content consistently. The unlock process is not friendly to fresh accounts, and it assumes you understand aggro control, enemy scaling, and how to survive extended encounters without relying on lucky item RNG. Having multiple survivors unlocked is strongly recommended, as some kits handle the unlock condition far more safely than others.
You’ll also want to be playing on at least Drizzle or Rainstorm with intentional item routing. Mobility items, reliable AoE, and defensive staples like Tougher Times or Repulsion Armor Plates dramatically reduce the risk of failing the unlock due to a single mistake. This isn’t a speedrun challenge, but sloppy play will absolutely cost you the run.
How the Unlock Ties Into Chef’s Theme and Playstyle
Chef’s unlock condition is deliberately designed to teach you how he plays before you ever select him on the character screen. The game forces you into a scenario where spacing, patience, and sustained damage matter more than raw burst DPS. If you try to rush it or face-tank like you’re playing Loader, you’ll fail fast.
This design philosophy mirrors some of Risk of Rain 2’s best survivor unlocks, where the challenge acts as a tutorial in disguise. By the time you unlock Chef, you’re already thinking the way his kit demands, which makes the first run with him feel natural instead of overwhelming.
All Prerequisites Before Attempting the Chef Unlock (DLC, Game Mode, Difficulty)
Before you even think about triggering Chef’s unlock sequence, you need to make sure your run is eligible on a systems level. Risk of Rain 2 is extremely strict with DLC flags and progression checks, and missing a single prerequisite will quietly invalidate the attempt without any on-screen warning.
This section breaks down exactly what the game checks behind the scenes before the Chef unlock can occur, so you don’t waste a 40-minute run chasing something that will never spawn.
Seekers of the Storm DLC Is Non-Negotiable
First and foremost, you must own and have the Seekers of the Storm DLC enabled. Chef is a DLC-locked survivor, and the unlock trigger is hard-tied to Seekers of the Storm-specific content. If the DLC is disabled, the required stage variant, interactable, or event simply does not exist in the run’s seed.
This is similar to how Void Locus and Planetarium were completely inaccessible without Survivors of the Void. Even if you meet every gameplay condition perfectly, the unlock will not appear unless the DLC flag is active at run start.
Classic Game Mode Only (No Simulacrum, No Eclipse)
Chef’s unlock can only be completed in standard Classic runs. Simulacrum is fully incompatible, and Eclipse modifiers can interfere with key survival checks during the unlock sequence. The game does not explicitly tell you this, but the event logic is disabled outside Classic mode.
If you’re farming Eclipse clears or Endless Simulacrum waves, switch back to Classic before attempting this. A surprising number of failed unlock attempts come from players forgetting they were still queued into the wrong mode.
Difficulty Requirements and What Actually Matters
Chef can be unlocked on Drizzle, Rainstorm, or Monsoon. There is no hidden difficulty lock forcing Monsoon, which is a relief given how punishing the unlock sequence can be. That said, Drizzle does not trivialize the process as much as players expect.
Enemy behavior and spawn density still scale aggressively once the unlock event begins. Drizzle gives you more room for mistakes, but it will not save you from poor positioning, bad item routing, or ignoring telegraphed attacks.
Progression and Account State Checks
Your account must have access to Seekers of the Storm stages in the normal stage pool. This means you need to have progressed far enough that the DLC’s content is fully integrated into your runs, not just installed.
If you’re on a fresh or partially progressed account, the unlock condition may never roll simply because the required stage variant hasn’t been added to your rotation yet. This is why the unlock feels inconsistent for newer players and far more reliable for veteran accounts.
Recommended Survivors and Loadout Readiness
While the game does not restrict which survivor you can use, some kits are dramatically better suited for the unlock’s pacing and safety requirements. Survivors with consistent ranged DPS, built-in mobility, and defensive utility perform far more reliably than melee-heavy or burst-dependent characters.
Huntress, MUL-T, Railgunner, and Engineer are standout choices due to their ability to control space and manage prolonged encounters without overcommitting. You don’t need god-tier RNG, but you do need a survivor that can deal damage while repositioning, because standing still during the unlock sequence is how most runs end.
Why These Prerequisites Exist
Chef’s unlock is designed to filter out unprepared runs before the challenge even begins. The game expects you to understand DLC routing, stage variance, and how difficulty scaling interacts with prolonged encounters.
Once all of these prerequisites are met, the unlock becomes a test of execution rather than luck. With the right setup, the game finally allows the Chef unlock sequence to appear, setting the stage for the exact in-game actions you’ll need to perform next.
Step-by-Step Chef Survivor Unlock Process: Exact In-Game Actions Explained
With the prerequisites handled, the Chef unlock finally becomes deterministic rather than RNG-dependent. The game will now allow the correct stage variant and event trigger to appear naturally during a Seekers of the Storm run, provided you know exactly what to look for and when to act.
This is not a passive unlock. Every step requires deliberate positioning, threat management, and understanding how Risk of Rain 2 handles event-based scaling.
Step 1: Reach the Seekers of the Storm Stage Variant
Begin a standard run with Seekers of the Storm enabled and progress normally through the early stages. The Chef unlock can only trigger on a specific Seekers of the Storm stage variant, not during Simulacrum or alternate game modes.
You do not need to rush the teleporter, but you also cannot stall endlessly. Aim to leave each stage around the 4–6 minute mark to stay ahead of enemy scaling without starving yourself of items.
When the correct stage rolls, you’ll notice a distinct environmental structure tied to food preparation and industrial equipment. If you don’t see it, the unlock cannot occur on that run.
Step 2: Locate the Hidden Interaction Point
Once on the correct stage, ignore the teleporter initially. The Chef unlock is tied to a hidden interaction object, usually positioned off the main traversal path or elevated on environmental geometry that rewards exploration.
Listen carefully for unique ambient audio cues and watch for interact prompts that do not resemble standard chests or shrines. This interaction does not announce itself and is easy to miss if you beeline objectives.
Interacting with this object will immediately lock you into the unlock sequence. Make sure you are ready before activating it.
Step 3: Survive the Cooking Trial Encounter
Activating the interaction begins a multi-phase combat event that functions similarly to a holdout zone. Enemy spawns are dense, aggressive, and escalate faster than a normal teleporter fight.
You must remain within the defined area while managing elite spawns, aerial threats, and sudden aggro swaps. Leaving the zone for too long will either pause progress or fail the attempt outright, depending on difficulty.
This is where mobility and sustained DPS matter more than burst. Abuse terrain, break line of sight when shields drop, and prioritize enemies with ranged pressure to avoid chip damage spiraling out of control.
Step 4: Defeat the Final Elite Wave
After surviving the initial waves, the game spawns a final elite-heavy group that acts as the unlock’s execution check. These enemies hit harder, soak more damage, and punish poor target prioritization.
Do not tunnel vision the largest enemy on screen. Clear adds first, manage crowd control, and only commit to elites when the arena is stable.
Once the final wave is defeated, the event ends immediately. There is no extra interaction required.
Step 5: Complete the Stage to Secure the Unlock
After the event ends, Chef is technically unlocked, but the game only registers it once the run properly progresses. Activate and complete the teleporter as normal.
You do not need to finish the run or defeat a final boss. As long as you transition to the next stage without dying, Chef will be permanently added to your survivor roster.
If you die after completing the event but before leaving the stage, the unlock will not count. This is one of the most common failure points.
Recommended Survivors and Item Priorities During the Unlock
Huntress excels here due to auto-aimed DPS and constant repositioning. MUL-T’s sustain and Engineer’s zone control trivialize the holdout aspect if built correctly.
Prioritize movement speed, on-hit effects, and defensive layers like Tougher Times or Repulsion Armor Plate. Raw damage matters, but survivability is what actually completes the unlock.
Avoid glass-cannon builds or lunar items that reduce HP. The event punishes greed far more than low DPS.
Common Mistakes That Cause Failed Unlock Attempts
The most frequent mistake is triggering the interaction too early with a weak build. If your items can’t handle sustained pressure, the event will overwhelm you regardless of difficulty.
Another common error is leaving the event zone to chase enemies, which resets or stalls progress and exposes you to ranged fire. Let enemies come to you and control space instead.
Finally, players often forget to finish the stage after succeeding. Treat the post-event section as lethal, because one sloppy death erases the entire attempt.
Best Survivors, Loadouts, and Items to Use for a Smooth Unlock Attempt
Now that you understand how fragile the unlock conditions actually are, the goal shifts from raw power to consistency. You want a survivor and build that can survive sustained pressure, control space during the event, and safely finish the stage afterward without gambling on RNG.
This section breaks down the most reliable survivor picks, the loadouts that minimize risk, and the item types that quietly carry successful Chef unlocks.
Top Survivors for Consistent Event Control
Huntress remains the safest overall pick for this unlock. Her auto-targeting removes aim pressure during chaotic waves, and Blink gives instant repositioning to escape bad spawns or elite overlap. Even with mediocre items, she can maintain DPS while constantly moving, which is exactly what the event demands.
Engineer trivializes the event if you are patient. Stationary turrets draw aggro, apply constant damage, and let you focus entirely on survival and add control. Bubble Shield or Thermal Harpoons both work, but shield offers more forgiveness if elites stack up.
MUL-T is another high-floor option thanks to built-in sustain and flexible weapon loadouts. Double Nailgun or Nailgun plus Scrap Launcher gives strong close-range control, while Transport Mode lets you disengage safely if things spiral.
Survivors That Can Work but Require Cleaner Play
Loader can brute-force the event with proper cooldown management, but a single mistimed grapple can leave you exposed without I-frames. If you use Loader, prioritize defensive items early and do not overcommit to aerial play during elite waves.
Bandit and Railgunner are viable but risky. Their burst damage deletes priority targets, yet both suffer heavily when surrounded. If you choose them, crowd control items are non-negotiable, and positioning becomes far more important than DPS.
Avoid survivors that rely on long setup windows or fragile summons. Anything that needs ramp time or precise execution increases failure odds during the final waves.
Recommended Loadouts That Reduce Failure Points
Default loadouts are often safer than experimental ones for this unlock. Huntress’s Blink over Phase Blink gives more frequent repositioning, while Engineer’s stationary turrets outperform mobile ones due to consistent aggro control.
For MUL-T, prioritize weapons with reliable on-hit application rather than burst reload gimmicks. Sustained damage smooths out bad enemy RNG and synergizes better with common defensive items.
If a loadout sacrifices mobility or defensive utility for damage, it is usually the wrong choice here. The event tests endurance, not speedrunning potential.
Item Priorities That Actually Win the Unlock
Movement speed is the single most important stat. Energy Drink, Goat Hoof, and Wax Quail let you kite elites without abandoning the event zone. Being fast enough to dodge is more valuable than killing faster.
On-hit effects like Ukulele, ATG Missile, and Tri-Tip Dagger scale incredibly well during dense waves. These items clear adds passively while you focus on survival and positioning.
Defensive layers win runs. Tougher Times, Repulsion Armor Plate, and Personal Shield Generator dramatically reduce chip damage, which is what usually kills players after the event ends. One or two defensive items often matter more than an extra damage pickup.
Items and Choices to Avoid During the Attempt
Glass-cannon items and risky lunars are a trap here. Shaped Glass, Brittle Crown, and anything that lowers max HP or removes healing will turn a stable run into a coin flip.
Avoid equipment that demands precise timing or stationary use. The event frequently spawns enemies behind you, and tunnel vision on equipment usage is a common cause of deaths after success.
If an item makes the run faster but less controllable, skip it. The Chef unlock rewards patience, not speed.
With the right survivor, a defensive-minded loadout, and smart item priorities, the unlock becomes a controlled challenge instead of a panic test. Build for survival first, and the event will fall into place naturally.
Common Failure Points and Hidden Mechanics That Can Break the Unlock
Even with the right build and survivor, this unlock fails more often due to system quirks than raw difficulty. Risk of Rain 2 is full of edge cases, and the Chef unlock is especially unforgiving if you don’t understand what the game is tracking behind the scenes.
This is where most “I definitely did everything right” attempts quietly break without the player realizing it.
Leaving the Event Zone for Even a Moment
The unlock condition tracks continuous participation, not just completion. Stepping outside the event radius, even briefly due to knockback, vertical movement, or panic dodging, can invalidate the attempt.
This includes getting launched by elite attacks or using movement abilities that overshoot the boundary. If you Blink, dash, or rocket jump, make sure you are angling horizontally, not vertically, to avoid clipping the edge.
Always fight near the center of the zone once the event starts. Kiting wide may feel safer, but it is the fastest way to fail without feedback.
Teleporter Completion Conflicts with the Unlock Flag
A major hidden failure point is interacting with the teleporter too early. If the teleporter finishes charging or is activated before the event fully resolves, the game can drop the Chef unlock flag.
This is especially common in co-op or high-DPS builds where enemies melt instantly. Even if the UI suggests the event is complete, wait a few extra seconds before touching anything.
Solo players should avoid stacking too much teleporter charge speed. The unlock prioritizes the event state over stage progression, and rushing the teleporter can override it.
Damage-Over-Time Kills Breaking Enemy Tracking
Certain DoT-heavy builds can accidentally sabotage the unlock. Enemies killed far outside the event zone by lingering effects like Gasoline chains, Ukulele lightning, or high-range bleed procs may not count properly.
This becomes a problem when enemies spawn inside the zone, get tagged once, then die well outside the radius. The game may register that as a failed containment condition.
If you are running heavy on-hit or AoE effects, focus your positioning so enemies die inside the circle. Let them come to you rather than chasing spawns.
Post-Event Deaths Still Count as Failure
One of the most brutal mechanics is that the game does not immediately lock in success when the event ends. There is a short grace window where dying will still fail the unlock.
This usually happens when players relax too early and get clipped by a lingering elite attack or a delayed projectile. Shields dropping and chip damage are the usual culprits.
After the event completes, keep moving and stay defensive until the unlock notification appears. Treat the event as active until the game explicitly confirms success.
Difficulty and Run Modifiers Quietly Invalidating Attempts
The Chef unlock requires a standard run environment. Certain modifiers, artifacts, or non-standard difficulties can invalidate progress without warning.
Artifacts that drastically alter enemy behavior or spawn rules are the biggest offenders. Even if the game allows the event to start, the backend conditions may not register properly.
To be safe, run on a clean ruleset with no artifacts enabled. If you are attempting this on higher difficulties, understand that the margin for error shrinks dramatically, especially with elite density and projectile spam.
Co-op Desync and Player Positioning Issues
In multiplayer, the unlock condition tracks all players. If even one teammate leaves the zone, the entire attempt can fail.
This is compounded by latency, where a player appears inside the zone on their screen but is technically outside server-side. Vertical movement and uneven terrain make this worse.
If attempting this in co-op, communicate constantly and designate one player to call movement decisions. Solo runs are significantly more reliable for this reason alone.
Why “Almost Successful” Attempts Don’t Count
The game does not provide partial credit or warning states. If any condition breaks, even briefly, the attempt is invalidated with no UI feedback.
This leads many players to believe the unlock is bugged when it is actually extremely strict. The Chef unlock is binary: perfect execution or nothing.
Understanding these hidden mechanics turns the unlock from frustrating to consistent. Once you respect the boundaries, timing windows, and tracking rules, success becomes repeatable rather than RNG-dependent.
Efficiency Tips: Speedrunning the Unlock vs. Playing It Safe
Once you understand how unforgiving the Chef unlock is, the real decision becomes philosophical: rush it and reset aggressively, or slow the run down and guarantee consistency. Both approaches work, but they reward very different mindsets and survivor choices.
What matters most is aligning your strategy with how comfortable you are managing aggro, spacing, and damage control under pressure.
The Speedrun Method: Fast Resets, Minimal Commitment
Speedrunning the Chef unlock is about reaching the required event as quickly as possible, attempting it with minimal gear, and resetting the moment something goes wrong. This approach assumes failure is acceptable and time efficiency matters more than win rate.
Pick survivors with immediate mobility and front-loaded damage. Loader, Mercenary, and Huntress excel here due to fast stage clears, reliable I-frames, and the ability to disengage instantly if positioning breaks.
Rush Teleporters, skip chests unless they are directly on your path, and prioritize movement speed over DPS. Goat Hooves, Energy Drinks, and Wax Quail do more for success here than raw damage because repositioning cleanly is what keeps attempts valid.
If you take any chip damage during the event or lose zone control for even a split second, pause and reset. Speedrunners treat failed attempts as data, not losses.
The Safe Method: Controlled Scaling and Over-Preparation
Playing it safe flips the philosophy entirely. Instead of rushing the unlock, you build a stable run first, then execute the event when you are statistically unlikely to fail.
Tankier survivors like MUL-T, Acrid, or Engineer shine here. Their sustained damage, zone control, and defensive tools reduce the risk of accidental condition breaks during the unlock window.
Clear stages thoroughly, stack defensive items like Tougher Times, Repulsion Armor Plates, and Topaz Brooch, and only trigger the unlock once you can comfortably survive multiple elite spawns without panic movement.
This method takes longer but dramatically increases first-attempt success, especially on higher difficulties where stray projectiles and elite modifiers end runs instantly.
Recommended Loadouts That Minimize Failure States
Regardless of approach, certain loadout choices reduce hidden risks. Abilities with forced movement, recoil, or self-displacement are dangerous because they can pull you out of the valid zone unintentionally.
Avoid skills that lock you into long animations unless they provide I-frames. Short cooldown dashes, instant bursts, and deployables that draw aggro all make the event easier to control.
Equipment like Royal Capacitor, Disposable Missile Launcher, or The Crowdfunder helps clear elites quickly without forcing you to reposition. Avoid equipment with delayed effects or screen clutter that can obscure incoming damage.
Common Efficiency Traps That Waste Attempts
The biggest time loss comes from trying to hybridize both strategies. Rushing with underpowered gear but refusing to reset leads to long, doomed attempts that feel close but never count.
Another mistake is over-scaling damage while neglecting defense. Killing enemies faster does not matter if one elite tick invalidates the unlock at the final second.
Finally, never assume the game will be lenient. Treat every frame as monitored, every pixel of movement as deliberate, and every sound cue as a warning. Efficiency comes from respecting how strict the system is, not trying to brute force it.
Troubleshooting: What to Do If Chef Does Not Unlock Properly
Even when everything feels perfect, Chef can fail to unlock due to hidden checks, version conflicts, or minor execution errors. Before assuming the run was wasted, walk through the following troubleshooting steps in order. Most failed unlocks trace back to one overlooked condition rather than a full reset-worthy mistake.
Double-Check the Core Unlock Requirements
First, confirm you were on a valid difficulty and game mode. Chef’s unlock in Seekers of the Storm only registers in standard runs; alternate modes, seeded runs, or certain mutators can silently invalidate progress.
Next, verify that the entire unlock sequence was completed in a single run. Stage transitions, character swaps, or ending the run early can all prevent the unlock flag from triggering, even if the event itself appeared successful.
Confirm You Never Broke the Hidden Failure Conditions
This is where most players get caught. The unlock tracks more than just completion; it monitors positioning, damage intake, and event integrity frame by frame.
Common silent failures include being nudged out of the valid zone by knockback, taking a single elite tick at the final second, or using an ability with forced movement that briefly exits the monitored area. Even if you immediately recover, the game does not forgive these micro-errors.
Watch for Co-Op and Multiplayer Desync Issues
If you attempted the unlock in multiplayer, desync is a real risk. Client-side success does not always match host-side validation, especially during high enemy density or elite spawns.
To eliminate this variable, attempt the unlock in solo or ensure you are the lobby host. Several players report the unlock only registering once repeated under host-controlled conditions.
Disable Mods and Verify DLC Installation
Mods are a frequent culprit, even cosmetic or UI-only ones. Any mod that alters enemy behavior, hitboxes, timers, or event logic can block the unlock trigger without throwing an error.
Before retrying, disable all mods, restart the game, and confirm Seekers of the Storm is properly installed and enabled. On PC, verifying game files can resolve cases where the unlock event completes but never saves.
Force a Clean Save State and Retry Efficiently
If you are confident the run was valid but Chef still did not unlock, fully exit the game rather than starting a new run immediately. This forces the game to re-sync progression data and prevents cached errors from persisting.
When retrying, replicate your successful conditions as closely as possible. Use the same survivor, similar loadout, and the same cautious pacing. Treat the second attempt as a controlled confirmation run, not a rushed re-clear.
When to Reset Versus When to Push Through
If you notice a clear violation mid-attempt, reset immediately. Continuing only wastes time and increases frustration, especially on higher difficulties where scaling punishes hesitation.
However, if everything feels clean and controlled, finish the run. Some unlocks fail to pop instantly and only register once the run concludes. Ending the run properly ensures the game has every opportunity to validate the unlock.
Troubleshooting Chef’s unlock is less about grinding and more about precision. Once you remove external variables and respect how unforgiving the checks are, the unlock becomes consistent rather than mysterious.
Chef Unlocked: What You Gain and How Chef Plays Compared to Other Survivors
Once Chef finally unlocks, the reward immediately feels earned. This survivor is not a gimmick character or a novelty add-on from Seekers of the Storm. Chef is a high-execution, high-payoff hybrid that rewards mechanical precision, spacing awareness, and smart cooldown management in a way few Risk of Rain 2 survivors do.
If your unlock attempt was clean and intentional, Chef will feel instantly familiar yet radically different. That’s by design.
Immediate Rewards for Unlocking Chef
Unlocking Chef grants permanent access to a survivor built around controlled aggression and positional dominance. Chef excels at mid-range pressure while retaining strong close-quarters burst, making them adaptable across early and late-game scaling.
Chef’s kit emphasizes chaining abilities efficiently rather than spamming cooldowns. You gain access to tools that punish clumped enemies, shred priority targets, and create safe zones in chaotic fights. This makes Chef especially valuable on higher difficulties where enemy density and elite modifiers demand precision.
Chef’s Core Playstyle: Precision Over Panic
Chef plays slower and more deliberately than survivors like Commando or Huntress. You are rewarded for reading enemy movement, timing engagements, and committing only when your kit is ready. Panic dodging or overextending gets punished hard.
Unlike Loader or Mercenary, Chef lacks consistent I-frames. Survival comes from positioning, spacing, and killing threats before they overwhelm you. This places Chef closer to survivors like Bandit or Railgunner, where mastery comes from decision-making rather than raw mobility.
How Chef Compares to Other Survivors
Compared to MUL-T or Engineer, Chef is far more hands-on. There are no passive turrets or brute-force builds to lean on. Every fight requires active input and awareness, especially against flying enemies and fast elites.
Chef also scales differently than most survivors. Instead of relying purely on attack speed or proc chains, Chef benefits disproportionately from cooldown reduction, on-hit effects, and items that reward precise hits. This makes item prioritization more nuanced than usual, especially for completionists pushing Eclipse or looping runs.
Why the Unlock Process Prepares You for Chef
The strict unlock conditions are not arbitrary. They teach the exact discipline Chef demands in actual gameplay. Clean execution, controlled pacing, and respecting game rules are the same skills needed to survive with Chef past the midgame.
If you brute-forced the unlock or relied on RNG, Chef will feel punishing. If you approached the unlock methodically, Chef feels powerful from the first stage. The survivor is effectively a skill check, both in unlocking and in long-term mastery.
Final Tip for New Chef Players
Treat your first few runs as practice, not progression. Learn enemy breakpoints, experiment with spacing, and resist the urge to over-loop early. Chef rewards patience more than almost any other survivor in Risk of Rain 2.
Seekers of the Storm doesn’t just add content, it adds expectation. Chef stands as proof that Risk of Rain 2 is still willing to challenge veteran players, not just test their builds, but their fundamentals.