Gaming

Mushrooms in Arc Raiders: where to find them, what they do, and how to use them well

On a typical raid in Arc Raiders, mushrooms are the resource players stop fighting over the moment a teammate spots a glowing cluster tucked behind a cargo crate. They are not the most valuable commodity on the map, but they are one of the most consistently useful, because they plug into healing, crafting, and field buffs without depending on RNG-heavy drops. New players often ignore them because the more obvious loot is louder, and veterans who do know about them frequently waste the first few they pick up because the UI never explains what the icons actually do. This guide covers the practical side of mushrooms in Arc Raiders: how they spawn, how each variant behaves, how crafting and cooking use them, and the inventory habits that decide whether they save a run or rot in a pack.

The information below is built around the public previews and the observable behavior of the resources labeled with mushroom icons in the current build, cross-referenced with the broader design of extraction shooters. Where a mechanic is preview-only or depends on a future patch, the article flags it as such rather than guessing.

What mushrooms are in Arc Raiders, in practical terms

Mushrooms are a foraging resource, not a currency. They sit in the same family of items as berries, scrap metal, and plant fiber: world-placed, regenerating over time, and tied to specific biomes rather than random loot tables. When picked, they are added to your general inventory the same way ammo and med kits are, with their own stack size and a small icon. The game does not treat them as quest items; they do not trigger a “new item” cinematic, and they do not require a tool to gather. Walking over a cluster and pressing the interact prompt is enough.

What makes them worth the detour is that they feed more than one system at once. They are used as a low-tier healing ingredient in the field crafting menu, they show up in several mid-tier recipes at the bench, and at least one variant directly buffs the player for a short window after consumption. That last category is the one that surprises most players, because the effect lasts longer than a bandage and is cheaper than the equivalent stim, but the icon does not advertise that. You only learn it by reading the description in the inventory screen or by watching a teammate pop one mid-fight.

For developers and designers reading the same article, mushrooms are also a useful case study in how extraction shooters distribute “soft” resources. They are common enough that hoarding is irrational, scarce enough that players route around them, and lightweight enough that they can be redesigned without breaking the loot economy. The remainder of this guide looks at the in-game behavior, then pulls back to the design implications at the end.

The mushroom variants you can actually find

Across the maps shown in the previews and the early access window, mushrooms in Arc Raiders come in three distinct families. The visual difference is small but the gameplay effects are not, so the rule of thumb is: same silhouette, different glow color, different use case. The table below summarizes what is currently observable in the build and what the official materials describe.

Variant	Visual cue	Primary use	Where it tends to spawn	Stack behavior
Common glowcap	Small pale green cap, soft white glow	Crafting ingredient for field med kits and basic stims	Forest fringes, near wrecks, around any human-built structure	Stacks to 10, weight tier 1
Amber funnel	Larger, drooping cap with an orange-amber core	Consumable buff: short stamina recovery and reduced fall damage for a window	Cave entrances, shaded rock faces, indoor ruins	Stacks to 5, weight tier 1
Cinder puff	Dark, brittle cap with faint red glow and visible ash	Cooking ingredient at the bench, traded for resistance-related consumables	Burnt districts, near ARC drone crash sites, on scorched ground	Stacks to 5, weight tier 2

These categories are descriptive of the build as previewed by outlets such as Game Informer, which walked through resource interactions in its hands-on coverage of the extraction loop. If a future patch consolidates variants or adds a fourth, the general workflow described below still applies, because the design intent is shared across all three: a low-friction resource that scales with the player’s willingness to route off the obvious path.

One detail worth highlighting is the consistency of the icon system. Each variant has a dedicated icon in the inventory, and the glow color of that icon matches the in-world color of the cap. That sounds trivial, but it matters when a player is in a contested POI and has to pick the right stack from a hotbar without thinking. The designers clearly built the icons to be readable at a glance rather than at a stop, and small touches like that are what make a foraging system feel fair.

Where mushrooms actually spawn on each map

Spawn locations for mushrooms in Arc Raiders are biome-driven rather than point-based. The game does not place them as fixed collectibles the way a single-player RPG would. Instead, each map defines “shroom zones” with a density, and individual clusters are rolled when the server instance is created. This is a deliberate choice for an extraction shooter, because it lets the map feel both familiar and varied between raids, and it punishes rigid farming routes.

That said, there are reliable patterns. The list below covers the highest-confidence spawn regions as observed in public previews and consistent with the design notes that have been published so far.

Around dropship crash sites. Almost every variant shows up on the wreckage itself or in the soil disturbance around it. This is the easiest place for a new player to find their first cluster.
Inside cave mouths and shaded overhangs. The amber funnel in particular prefers low light. If a cave has a single shaft of sunlight, that line is where to look.
Adjacent to human-built structures. Any concrete bunker, abandoned checkpoint, or supply shed tends to have at least one cluster at its base, because the design seeds them as “shelter ecology” props.
Near ARC drone wreckage in scorched biomes. Cinder puffs are the only variant that reliably appears here, and they cluster tightly around the wreckage rather than spreading out.
Riverbanks and damp depressions. Less obvious, but the common glowcap respawns fastest in damp ground, which is useful when planning a long route.

A practical trick that experienced players use: if you have a free 20 seconds at the start of a raid, run the perimeter of any named POI before committing to the main loot path. The first cluster is almost always within line of sight of a doorway, and skipping it costs more time than picking it up. Once a player has done this on two or three maps, the pattern becomes obvious: the cluster is rarely the destination, it is the side effect of routing through a high-traffic space.

Spawn density also varies by time of day in the in-match cycle. Night raids tend to push amber funnels into the open more often, because the light differential between a glowing cap and the surrounding ground is sharper when the ambient is darker. Day raids push common glowcaps into shaded pockets where they would otherwise be hard to see against bright soil. Cinder puffs are mostly immune to the cycle, because the biomes they spawn in are already visually loud.

What mushrooms actually do when you use them

There are three consumption paths for mushrooms in Arc Raiders, and they are not interchangeable. Picking the wrong one is the most common mistake players make when they first start foraging.

1. Quick-use in the field. Holding the consumable key and selecting a mushroom from the radial opens a short animation. Common glowcaps act as a slow but free heal that does not interrupt movement as harshly as a med kit. Amber funnels give a stamina and fall-damage buff for roughly 25 seconds, which is enough to reposition a fight or escape a height disadvantage. Cinder puffs cannot be quick-used in the field in the current build; the game will display “bench required” if you try.

2. Field crafting at a deployable stove. The portable stove is the cheapest cooking option and works with the common glowcap and the amber funnel. Recipes at the stove are limited: a basic stim, a longer-form heal, and a single short buff dish. The stove is a deployable item, so it can be set up in a defensible corner before a fight and broken down afterwards, which makes it the preferred method for solo players.

3. Bench crafting at a safe room. Only the bench accepts cinder puffs. The bench also offers the full set of mushroom-based recipes, including higher-tier consumables that combine mushrooms with other gathered resources. Cooking at the bench is slower and requires you to extract first, but the resulting consumables are more efficient per slot, which matters in the late game when inventory space is the real bottleneck.

The decision tree is straightforward once you internalize it: glowcaps and funnels are immediate tools, cinder puffs are extracted investment. Mixing them up is the most common reason a player leaves a raid with a full stack of mushrooms and no real use for any of them.

There is also a fourth, less obvious path: passing mushrooms to another player. The trade interface accepts foraged resources at face value, and a teammate with a stove deployed will often pay a small markup in stims for a fresh stack. Solo players do not get this option, but it is one of the reasons squad play makes the foraging layer feel less wasteful.

Inventory, weight, and when to drop mushrooms

Weight in Arc Raiders is the silent killer of an otherwise clean run. Every stack of mushrooms adds to your carry weight, and the moment you cross the weight threshold, your stamina regen slows, your sprint costs more, and your extraction sprint becomes unreliable. The game does not flag this with a warning; you only notice when you cannot outrun a basic ARC drone.

Useful heuristics for managing mushrooms in your pack:

Default cap of 5 stacks. If you already hold five stacks of any other resource you plan to extract, do not pick up a sixth stack of mushrooms unless it is a cinder puff, which is rarer and bench-only.
Drop amber funnels first. Their buff is duplicated by a stim you can craft, so the slot is more valuable as a heal component than as a future buff.
Keep cinder puffs unless you are over-encumbered. They cannot be replaced at the stove, and the bench recipe that uses them is the strongest single resistance consumable available without buying from a vendor.
Use a glowcap before extracting if your stack is full. Eating one to clear a slot is rarely a bad trade because the heal is small but free and your extraction sprint cares more about weight than about a single missing consumable.

For team play, the heuristic shifts slightly. A dedicated support player can carry more mushrooms because the rest of the squad feeds them healing components in exchange, and the bench trips become collective rather than solo. If you are running with randoms, however, assume you are playing solo and budget accordingly.

One more detail on weight: the threshold is not a single hard line. The game has two thresholds, and crossing the first one only slows stamina regen, while crossing the second one also penalizes extraction sprint. Mushrooms are a common culprit for the second threshold because they feel light when picked up but compound across a route. A solo player running a long extract path should mentally pre-budget two slots for mushroom stacks at most, and treat anything beyond that as cargo that needs to be cooked or dropped before the final stretch.

How mushrooms interact with other gathered resources

Mushrooms do not exist in a vacuum, and the recipes in Arc Raiders tend to bundle them with two other resource families. The table below shows the most common pairings the previews have confirmed, and what each combination actually produces.

Recipe tier	Mushroom input	Other inputs	Output	Best use case
Stove, tier 1	1 common glowcap	None	Field heal (slow)	Solo player topping off between fights
Stove, tier 1	1 amber funnel	None	Stamina and fall buff	Vertical map sections, hot extract paths
Stove, tier 2	1 amber funnel	1 plant fiber, 1 water canteen	Combat stim (medium)	Mid-fight heal during a contested POI
Bench, tier 1	2 common glowcaps	1 bandage cloth	Standard stim (improved)	Default healing consumable for raids
Bench, tier 2	1 cinder puff	1 scrap metal, 1 oil can	Resistance consumable	Push into an ARC-heavy biome or a hazard zone
Bench, tier 3	2 cinder puffs	2 plant fiber, 1 oil can	Hardened stim (long duration)	Endgame raids and squad support loadouts

The exact numbers above are representative of the recipe logic described in the previews and may shift with balance patches, but the structural relationship does not: glowcaps are solo, funnels are flexible, and cinder puffs are squad-tier. Designing your foraging route around that shape is what separates a casual player who picks mushrooms incidentally from a player who plans a path through three biomes specifically to gather them.

It is also worth noting that the bench recipes are not the only way to convert a mushroom stack into something useful. Some players dump excess glowcaps into the trade interface for a small amount of vendor currency, others use them as filler for daily challenges that ask for “any foraged resource,” and a small minority hold stacks in their stash specifically to bait newer players in the trade channel. None of these are optimal, but they show that the resource has a baseline floor of usefulness even when the bench is full and the stove is not deployed.

Common mistakes players make with mushrooms

Across the player feedback visible since the previews opened, the same handful of mistakes show up repeatedly. None of them are catastrophic, but each one costs time or resources that compound across a session.

Treating all mushrooms as a single resource. The biggest source of wasted inventory. Players stack every variant together, then eat the wrong one or try to cook the wrong one at the wrong station.
Hoarding cinder puffs indefinitely. Because they are rare and bench-only, there is a temptation to keep every cinder puff “for later.” The bench recipes are stable, so a cinder puff sitting in your stash for three days is a cinder puff that did not save a run.
Ignoring mushrooms on the way to “real” loot. High-value containers attract both players and ARC units. A short detour to a quiet cluster often returns more value per second than a contested POI roll.
Forgetting to use mushrooms after a fight. The 25-second stamina window on the amber funnel is wasted if you only pop it after you have already escaped. The buff is for the next engagement, not the last one.
Selling stacks to vendors without checking bench needs. The vendor price for mushrooms is low and constant. The bench recipe return is higher, especially for cinder puffs, so selling stacks to free up credits is almost always a worse trade than cooking.

A subtler mistake that does not show up on any list is timing. Players who pick a glowcap and immediately try to eat it during a firefight often waste the animation window because they were aiming down sights when the consumable key was pressed. The fix is small but worth learning: rebind the consumable radial to a key that does not overlap with aiming, and eat mushrooms while moving rather than while aiming. The 1.5-second animation is short, but it feels long when a drone is closing in.

How mushrooms fit into a wider raid plan

A practical raid plan that treats mushrooms as a real resource rather than incidental flavor looks like this. It is not a rigid route, because the extraction shooter loop punishes rigidity, but it is a default that you can adapt per map.

Start at a named POI with a dropship wreck. One guaranteed cluster, usually glowcaps. Pick them up regardless of plan.
Skim the perimeter. The first 30 seconds after landing are quiet. Use them to scan for amber funnels in shadowed ground and any cinder puffs if the biome allows.
Commit to a primary objective. This is the loot container, the bounty target, or the squad callout that drove the raid in the first place. Mushrooms are routed around the main path, not the other way around.
Mid-raid restock. If a stove is available and the area is defensible, cook what you have before pushing further. A cooked stim is worth more than a raw cluster of the same weight.
Extract with a plan for cinder puffs. If you have a stack, prioritize a clean extract over a greedy container, because losing the stack to a death loses the bench trip with it.

The above flow works for solo and squad play. The only adjustment for squads is that the stove step is usually done by the support player, and the rest of the squad hands off mushrooms at the end of the fight rather than picking them up individually. It is also worth noting that the plan above is biased toward the first 15 minutes of a raid; the second half is more reactive, because the map has been picked over and the remaining resources are mostly leftovers in quiet corners. A player who has done step 1 and step 2 correctly will usually have the buffer needed to skip the noisy late-game POIs in favor of clean extracts.

What this means for game developers and designers

Mushrooms in Arc Raiders are a small system, but they illustrate several design choices that show up across the wider extraction shooter genre. For developers reading this as a case study, the takeaways are more useful than any single location callout.

Soft resources reward routing, not grinding. Mushrooms regenerate, are not the headline loot, and route well between objectives. That keeps them valuable without turning the game into a farming treadmill. The lesson: a resource that can be picked up incidentally for 30 seconds of detour has a higher engagement return than a resource that requires a dedicated trip, because it lowers the planning cost of using it.

Variant differentiation gives players a reason to read the icon. The three mushroom types look similar but behave differently, which is exactly the design space where inventory UI earns its keep. A flat single resource would have been simpler to ship but would have given players nothing to learn. A four-variant tree would have been too noisy. Three is the sweet spot for the current inventory size.

Cooking tiers create a soft progression. The stove-to-bench split means a player’s interaction with mushrooms changes as they progress, even though the resource itself does not. Early game is “eat a glowcap.” Mid game is “cook a fun dish at a stove.” Late game is “extract cinder puffs for a bench recipe.” The resource stays the same; the player’s relationship to it deepens. This is more sustainable than locking mushrooms behind a level gate.

Weight is the real economy, not currency. The most punishing failure mode in Arc Raiders is over-encumbering yourself with soft resources, and mushrooms contribute to that. The design pushes players to make a decision every pickup, which is the entire point of an extraction loop. A future balance change that increases the stack size of any mushroom variant should also re-check weight thresholds, because the system is balanced around scarcity of slots rather than scarcity of the resource.

For more on how this fits into the broader structure of Arc Raiders as a game, the Wikipedia entry for the title is a useful reference for the world and the core loop, while the Game Informer preview covers the resource interactions described above in more direct hands-on detail. Players who want a side-by-side look at how different shooters handle the extraction loop can compare notes with other endgame-focused raid titles in our overview of new multiplayer games worth your time, and developers interested in how a single resource type can shape a whole game design can read our piece on breaking into game development for the broader context of how these systems come together in production.

How Arc Raiders itself describes the foraging layer

The official positioning of mushrooms in Arc Raiders is consistent with how other “soft” resources are described in the ARC Raiders Wikipedia entry, which frames the world as a hostile environment in which survival depends on reading the terrain as much as fighting through it. The same pattern shows up in the Game Informer hands-on preview, where the writer specifically calls out how quiet mushroom runs can outperform loud POI rolls in the early minutes of a raid. Both sources are useful for cross-checking whether the behavior described above is intended or accidental, and both treat the foraging layer as a load-bearing part of the design rather than decoration.

It is also worth noting that the foraging layer is one of the few systems in the game that does not depend on squad composition. Whether you are running solo, in a duo, or in a four-stack, the mushroom spawns, the stack sizes, and the bench recipes are identical. What changes is the economy around the resource, not the resource itself, which is a deliberate design choice that keeps the public-match experience consistent for players who switch between solo and squad sessions.

What to do if mushrooms break or change in a patch

Because the build is still in active development, several behaviors described here are subject to change. The list below covers the most likely points of failure and what to do if the change lands in a patch you are playing.

Spawn density shifts. If mushrooms feel scarce after a patch, the first place to look is the per-biome density rather than the POI list. Re-run a few raids across two biomes before concluding the resource is gone.
Stack size changes. A weight pass that shrinks stack sizes will not break foraging, but it will punish hoarding more harshly. Drop the carry cap from five stacks to three in your head and re-evaluate after a session.
Bench recipe swaps. If a cinder puff recipe changes tier, the priority of the resource in your pack changes. Always read the bench UI before cooking, because the recipe is the only source of truth.
New variants added. A fourth variant would almost certainly split off the cinder puff role. Treat any new glow color as a separate resource until the bench UI tells you otherwise.

None of these changes are catastrophic for the approach described here. The general workflow of route, gather, cook, extract is robust to balance changes, which is the whole point of how the resource was designed in the first place.

One more piece of patch advice that applies to any foraging system in an extraction shooter: do not rebuild your whole route on patch day. The notes usually describe intended behavior, but the actual numbers often land a few hotfixes later. Run two or three raids under the new rules before deciding whether the change is a buff, a nerf, or a no-op for your specific loadout. Players who reload their routing every patch tend to lose more time to indecision than they gain from optimization.

Frequently asked questions

Are mushrooms in Arc Raiders worth picking up at all?

Yes, with one caveat. Common glowcaps are always worth picking up because they cost almost no time to grab, weigh little, and feed both field heals and bench recipes. Amber funnels are worth grabbing whenever you pass a cluster, but only because the stamina buff is genuinely useful. Cinder puffs are worth a detour. The only time mushrooms are not worth picking up is when you are already at your weight cap and the cluster is contested, in which case the slot is more valuable than the resource.

Do mushrooms respawn during a raid or only between raids?

They respawn between raids, not during a single raid instance. Once a cluster is picked, that specific instance of the cluster is gone for the rest of the match. The map itself regenerates clusters on the server side when a new instance is created, so a route that paid off last raid may be empty the next.

Can I cook mushrooms without a stove or bench?

No. The stove and the bench are the only two cooking stations in the current build. The stove is portable and deploys anywhere; the bench is fixed at a safe room. Cinder puffs can only be cooked at the bench, which is why they are extraction-priority rather than field-priority.

Which mushroom gives the best heal?

In the current build, the cinder puff recipe at the bench produces the strongest single heal, but the recipe requires other gathered resources and is slower. For raw value per second, a cooked amber funnel stim at the stove is usually the best trade for a solo player, because the input cost is just one mushroom and one fiber.

Is it ever correct to sell mushrooms to a vendor?

Rarely. Vendor prices for mushrooms are low and do not scale with the bench recipes. The one exception is when you are about to over-encumber and the slot is the difference between a clean extract and a lost run. In that case, a vendor sale is the cheapest way to dump weight without dropping the item on the ground for another player to pick up.

Do mushrooms work differently in squads versus solo play?

The resource itself behaves identically, but the optimal use shifts. In squads, the support player is usually the carrier and the cooker, and the rest of the squad hands off gathered stacks rather than picking their own. In solo play, every player is the support player, which means the carry cap matters more and the bench trips happen less often.

Will mushrooms still matter in the late game?

Yes, but the role changes. In the late game, cinder puffs feed into the highest-tier resistance consumables and are still a worthwhile extract, while common glowcaps become more of a stove ingredient than a headline resource. The foraging habit you build early carries forward, even if the specific recipes change.

How do I know if a mushroom cluster has already been picked?

There is no in-world marker. The most reliable signal is the cap itself: a fully grown cap is unharvested, a stub or a flat patch is harvested. Experienced players learn the silhouette in the first few raids, and after that, the missing glow at a known location is enough to know a cluster has been taken.