Where to find Prickly Pear in ARC Raiders: extraction routes, spawn logic, and crafting value

Where to find Prickly Pear in ARC Raiders

Players looking for where to find Prickly Pear in ARC Raiders are usually after one of three things: the raw location of the plant, the conditions that make it actually appear during a run, and the recipe that justifies the trip. Prickly Pear is a natural flora resource in the extraction shooter ARC Raiders, published by Embark Studios, and it feeds a small number of mid-tier healing and field-crafting recipes. It is not the rarest material in the game, but its spawn pattern punishes players who run a fixed route, because each map reseeds flora on its own cycle rather than on a shared global timer.

This guide breaks the problem into the layers a player actually needs: the biomes where Prickly Pear appears, the specific landmarks that consistently hold it, the way ARC patrols and weather interact with those landmarks, the extraction path that keeps a haul alive, and the crafting recipes that justify picking it up instead of a faster, more obvious healing item. The advice here is based on the build of ARC Raiders available through the open and closed playtests, and on the published design intent of the developers as covered in early previews of the game.

What Prickly Pear is in ARC Raiders and why the question is harder than it looks

Prickly Pear is a flora-type gathering node, the in-fiction cactus fruit that ARC Raiders uses to feed its natural-resource crafting chain. The reason so many players ask about it is that the game does not treat natural resources the way many other survival-extraction games do. Flora does not respawn in fixed positions, and it does not have a single global cooldown. Each map region maintains its own internal pool of nodes, and that pool regenerates on a delay tied to player traffic, server population, and the time elapsed since the region was last cleared of a high enough density of players.

The other reason the question is harder than it looks is that the ARC Raiders map is layered. The overworld has named regions with distinct biomes, but many named regions also contain interior sub-areas, ruins, and underground ARC facilities. Flora nodes are not distributed evenly across that whole area. They are weighted toward the open biomes, the edges of ruins, and the parts of the map that the ARC patrols do not actively sweep. Walking straight to a Prickly Pear cluster on a route video will often produce an empty patch of sand because a different squad just took that spawn, or because the ARC behavior script suppressed it for the round.

How Prickly Pear differs from berries, fungus, and salvage

The game splits its gatherable resources into four practical categories, and Prickly Pear sits in a specific one. Understanding the category prevents the most common error, which is to treat a flora node like a salvage pile.

• Flora: plant-based nodes such as Prickly Pear, sunberries, and sky fungus. They grow in fixed biomes, regenerate on a per-region timer, and are gathered by hand without a tool.
• Salvage: mechanical and industrial loot found on ARC hulls, in containers, and inside facilities. Tools or weapons speed up gathering.
• Organic compounds: the byproducts of ARC kills and raider corpses. They are gathered from the remains after a fight, not from the environment.
• Cached supplies: pre-packaged loot in player-deployable caches and abandoned drop pods, not tied to a specific node.

Prickly Pear belongs to the flora group, which means the rules that govern salvage and the rules that govern ARC kills do not apply to it. It is gathered by walking up and holding the interact prompt. It is not a contested drop, and you do not need to kill an ARC to loot one. The challenge is entirely about reaching the right biome, at the right time in the respawn window, without being killed by something else on the way there.

The biomes where Prickly Pear actually grows

Across the playtest versions of the ARC Raiders map, Prickly Pear has been tied to three biome types: arid plateaus, dry canyon floors, and the scrubland borders that sit between human ruins and ARC territory. The plants appear in small clusters, usually two to four nodes per cluster, and the clusters are spaced far enough apart that a single run rarely gathers more than one full cluster unless the player is specifically routing between two or three known landmarks.

Arid plateau biomes

Arid plateaus are the most reliable biome for Prickly Pear. They are the open, sun-baked regions on the higher elevations of the map, usually reached through one of the central ridgelines. The advantage of running a plateau route is line of sight: a player on a plateau can see ARC patrols approaching from two or three directions, which matters for any flora run, because gathering requires a few seconds of standing still. The disadvantage is that plateaus are also where players who have already lost a fight tend to retreat, because the higher ground is a strong defensive position. That overlap means flora nodes on plateaus are sometimes contested by a third-party squad finishing off a runner.

Dry canyon floors

Canyon floors hold Prickly Pear less consistently than plateaus, but in greater density when the spawn fires. The nodes tend to be tucked against the base of a cliff wall, often under a small overhang. The trade-off is exposure: a player gathering from a canyon floor is in a kill box. If a patrol walks in, the only way out is forward. Canyon runs work best when the player has a planned extraction line along the canyon itself, rather than back to a plateau.

Scrubland borders near ruins

Scrubland borders sit between human-built ruins and ARC-controlled ground. They are the visual transitional zones in ARC Raiders, where cracked concrete fades into red dirt. Prickly Pear clusters here tend to be smaller, often a single node, but they regenerate quickly because the bordering ruins pull most of the player traffic. For a solo player, a scrubland route is often the safest, because the high-traffic ruins act as a noise buffer that draws squads away from the flora line.

Specific landmarks to anchor a Prickly Pear route

Players asking where to find Prickly Pear in ARC Raiders usually want coordinates, not biome theory. The map does not have coordinates in the conventional sense, but the playtest versions of the game have a small number of named landmarks that consistently hold the plant. The list below reflects the regions that have been present across multiple playtests, and that have a documented flora bias. Minor landmark names can shift between patches, so treat these as anchor points and confirm the exact name on the in-game map at the start of a run.

Landmark type	Why Prickly Pear grows there	Risk profile
Plateau ridgeline with a broken ARC sensor tower	Open sun, dry soil, ARC patrols routed around the tower rather than through the flora	Medium. ARC patrols are predictable here but third-party squads use the tower as a sniper perch
Canyon wall with a collapsed overpass	Shaded microclimate, dense cluster size when the spawn fires	High. Kill-box terrain, limited extraction angles
Scrubland edge of an abandoned mining camp	Border biome between ruins and open ground, fast regen due to nearby player traffic	Low to medium. PvP risk is lower, but ARC density is higher near the camp
Dry riverbed crossing beneath a derelict pipeline	Stable biome, predictable flora cluster, near a known extraction corridor	Medium. Extraction chokepoint, easy ambush by squad waiting on the pipeline
Open mesa south of a ruins perimeter wall	Sun-exposed flat ground, large cluster when present, good sightlines	Low flora risk, high sniper risk from the perimeter wall

The table is a starting point, not a final answer. A player who learns the five landmark types above can build a route through any region that shares one of those shapes, because the biome is what governs the spawn, not the landmark’s specific name.

Reading the in-game flora indicator

The current build of ARC Raiders shows a faint visual cue when a player is near a flora node: a small, low-contrast shimmer over the plant. The shimmer is intentionally subtle, because Embark has discussed the design goal of not turning gathering into a waypoint hunt. Players who rely on it should treat the shimmer as a confirmation, not a discovery tool. The biome knowledge above is the discovery tool, and the shimmer simply tells you whether the spawn has fired on this region this cycle.

How ARC patrols affect a Prickly Pear route

ARC behavior is the single largest variable in any flora run, because the ARC is not a passive mob. The patrolling units follow a script that responds to player presence, gunfire, and the density of corpses in an area. A Prickly Pear cluster that was clear thirty seconds earlier can be inside an ARC patrol route the moment a fight breaks out nearby. Players running for flora have to choose between two strategies: avoid ARC entirely, which means taking a longer path through less efficient biomes, or use ARC noise to mask their gathering, which is faster but more dangerous.

Why ARC noise can actually help

ARC units in ARC Raiders are tuned to converge on gunfire and movement, but they do not all converge at the same speed. A heavy unit, for example, takes longer to reposition than a light scout. A solo player can use that asymmetry by firing a single low-noise weapon at a distant ARC, drawing the heavy away from a flora node while the light scout rotates into a different pattern. The window of safety is short, often less than a minute, but it is enough to gather a cluster if the player has already scouted the spot.

Why ARC noise can wreck the same plan

The same mechanic cuts the other way. A player who fires a noisy weapon to bait an ARC can attract a second squad. The extraction shooter format of the game means that any loud action has a PvP consequence as well as a PvE consequence. The general rule is to bait only with the quietest weapon in the loadout, and to bait only when the nearest player on the map is far enough away that the sound will fade before it reaches them. In practice, most experienced players will not bait at all for a Prickly Pear run, because the resource is not rare enough to justify a noisy approach.

Extraction routes that keep a Prickly Pear haul alive

The longest section of any flora run is not the gathering, it is the walk back. A Prickly Pear cluster in ARC Raiders is not worth carrying if the player dies on the return, because natural resources are kept in the personal inventory and are lost on death unless a teammate recovers the bag. That makes the choice of extraction route at least as important as the choice of gathering spot.

Extraction approach	When it fits a flora run	Main failure mode
Direct call at the closest exfil pad	Solo run with no other player seen on the map, low ARC density	Exfil pad chokepoint, easy ambush during the call timer
Two-stage exfil through a near pad and a far pad	Squad run with one player carrying the flora, one player screening	Requires a team that stays together, slow if the first pad is contested
Walking exfil to a friendly perimeter	Run started near a friendly ruins edge with a clear path out	Long exposure time, ARC can intercept on the open ground
Stash-and-return with a hidden cache	Long route with multiple gather points and no safe exfil nearby	Cache can be found and emptied by another player
Drone exfil using a deployable beacon	Late-round run when most squads have already left the area	Beacon is a loud, visible signal that draws every remaining squad

The trade-off that the table exposes is a constant in ARC Raiders: the faster an extraction is, the louder it is. Prickly Pear is a small enough resource that the loudest extractions are usually wasted on it. The most efficient plan in a typical round is to gather the cluster, walk a short distance to a peripheral exfil pad, and call a standard extraction. A peripheral pad, rather than a central one, gives a few extra seconds of safety during the call timer because squads tend to watch the obvious hubs.

Solo runs versus squad runs

Solo players have the worst odds on any extraction, but they also have the best stealth options for a flora run. A solo Prickly Pear route should minimize the time spent near other players, which means the scrubland edge biomes rather than the contested plateaus. Squad runs have the opposite problem: a four-player team gathering a single cluster is overkill, and the squad is far better served by splitting into two pairs, with one pair gathering and the other pair screening from a defensible position. The resource itself does not change between solo and squad play, but the optimal route does.

What Prickly Pear is used for in crafting and field medicine

The reason a player takes the trouble to learn a Prickly Pear route is the recipe. The playtest versions of ARC Raiders route the resource into a small number of mid-tier healing items and one field utility recipe. None of the recipes require Prickly Pear as a single input, so a player who wants the outputs has to bring back at least two or three units per run to be efficient.

Healing recipes that take Prickly Pear

The exact recipe names shift between patches, and Embark has stated that the crafting balance is still being tuned, so the descriptions below are written to capture the function of each recipe rather than the precise label. Players who want the current label should check the in-game crafter at the start of a session.

• Field dressing, advanced tier: a healing consumable that restores a moderate amount of health and clears one minor status effect, such as a minor bleed. Takes Prickly Pear as the flora input, plus a small amount of salvage.
• Stim-shot, natural variant: a short-duration buff to stamina regeneration, useful for extended extraction fights. Prickly Pear is combined with a processed flora item and a small organic compound.
• Antidote field mix: a consumable that mitigates a single instance of toxic damage from ARC gas. Takes Prickly Pear plus a processed organic compound, and is the recipe that pushes Prickly Pear from optional to important in any biome that contains ARC gas units.

The three recipes together make Prickly Pear a useful bridge between the early-game berry-based healing and the late-game compound-based healing. A player who ignores the resource in the first hour of a wipe will usually start looking for it in the second hour, because the antidote mix is what unlocks safer farming of the ARC units that drop the heavier compounds.

Why Prickly Pear is not a top-priority resource

It is worth being honest about the resource’s tier. Prickly Pear is a mid-tier flora, and it is not the bottleneck in any current crafting chain. A player who treats it as a top-priority grind will spend more time on routes than the recipes will save. The right mental model is that Prickly Pear is an opportunistic pickup: a player who passes a known cluster on the way to a higher-value objective should grab it, but no run should be planned around the resource alone. The recipes that need it can be batched, and a stockpile of four to six units is enough to ride out a short wipe without re-running the route every session.

A practical Prickly Pear route plan

Bringing the previous sections together, a reliable Prickly Pear route in the current build of ARC Raiders looks like this. The plan assumes a solo player, a quiet server, and a target of two units per run. The map-specific landmark names are deliberately left as variables, because the playtest map has been rebuilt several times, but the route shape is stable.

1. Spawn at a peripheral drop point rather than the central hub, to avoid the first-minute PvP traffic.
2. Move immediately toward the nearest scrubland border biome, prioritizing a route that stays within cover for the first ninety seconds.
3. Cross from scrubland into a dry canyon floor, and follow the canyon wall rather than the canyon center, because the wall edges are where the flora clusters tend to be.
4. Reach the nearest landmark that matches the broken-ARC-sensor-tower or collapsed-overpass shape, and check the biome shimmer. If the cluster is present, gather it. If not, hold position for thirty to sixty seconds and check again, because the regional regen can fire during a stay.
5. Do not bait ARC units. If a patrol path crosses the cluster, reposition to a different cluster along the same biome rather than fighting.
6. After gathering, walk to a peripheral exfil pad rather than the nearest pad, and call a standard extraction only after confirming no other player has rotated onto the pad during the previous two minutes.
7. If a second squad is already on the chosen pad, fall back to the stash-and-return plan, hide the cluster in a covered cache, and either continue gathering another cluster or run a wider loop to a quieter pad.

The plan takes longer than a direct farming route, but it produces a much higher survival rate per unit, which is the metric that actually matters for a resource this size. The trade-off is between time and yield, and ARC Raiders rewards yield-per-life over yield-per-minute in the mid game.

How the spawn logic actually works

Players who want to optimize a Prickly Pear run benefit from understanding the spawn logic, because the system is more forgiving than it first appears. The relevant rules, as observed across playtest builds and as described in Embark’s design commentary, are these.

• Each map region has a flora budget, which is the maximum number of flora nodes that can be present in that region at any one time.
• When a flora node is gathered, it is removed from the budget immediately. The next node does not appear at the same spot, it appears at the next eligible position in the same biome.
• The region’s budget refills on a timer that is influenced by player traffic, but the timer has a minimum value, so even a quiet region will not refill faster than the minimum.
• If a region is heavily trafficked, the budget refills at the maximum rate. If a region is empty, the budget refills at the minimum rate. A solo player is therefore best served by staying near a moderately trafficked area, because the regen is faster but the contested risk is lower than in a hot zone.
• ARC units can suppress flora regen in their immediate vicinity. A region with a heavy ARC presence will have a lower effective flora budget, even if the underlying biome is correct.

The practical consequence of the rules is that a Prickly Pear run is best done near, not inside, a high-traffic area. The player borrows the faster regen of the traffic without paying the cost of fighting the players who are causing the traffic. The scrubland border biomes are the cleanest expression of this principle, because they sit at exactly the right distance from a ruin to pick up the regen benefit while staying out of the direct line of sight of the players inside the ruin.

Weather and time-of-day interactions

Some playtest builds of ARC Raiders include a day-night and weather system that changes the behavior of flora and ARC units. Prickly Pear has not been documented as weather-sensitive in the same way that some fungus-type resources are, but the indirect effects matter. Dust storms reduce sightlines, which helps a stealthy gatherer but also makes ARC detection less predictable. Night cycles reduce overall player traffic, which slows regional regen. A player building a regular Prickly Pear route should run it during a weather window that favors the player, which in the current balance means a light overcast or early evening rather than a clear midday, because the former two have slightly more cover and slightly less traffic.

Common mistakes when chasing Prickly Pear

For additional context, Five mistakes account for most of the failed Prickly Pear runs in ARC Raiders. A new player usually makes at least two of them per session, and an experienced player will make at least one. Naming them up front is the fastest way to avoid them.

1. Treating the map as static. The flora respawns per region, not per map, so a route that worked yesterday will produce empty clusters today if the region is still on its cooldown.
2. Routing through the center of the map. The center is the PvP axis of the map, and a flora run through the center is a fight, not a gather.
3. Fighting the ARC that wanders into the cluster. The ARC will move on within a few seconds, and a fight wakes up every squad on the map. The Prickly Pear is not worth the noise.
4. Calling extraction at the nearest pad. The nearest pad is also the most watched pad. A flora run deserves a peripheral pad.
5. Forgetting the craft. Carrying Prickly Pear back to the crafter only to realize that the recipe also needs a salvage item the player did not bring is a common late-wipe problem. A quick check of the recipe before leaving the safe zone saves a return trip.

None of these mistakes are unique to Prickly Pear, and the same list applies to most flora resources in the game. The reason Prickly Pear is a useful case study is that it is just valuable enough to be worth routing for, and just common enough to be worth optimizing, so the mistakes have a measurable cost.

How Prickly Pear fits into a wider resource economy

The place of Prickly Pear in the economy of ARC Raiders is best understood by looking at what it replaces, what it feeds, and what it cannot do. A player who knows those three boundaries can decide quickly whether a Prickly Pear run is the right use of a given match.

• Replaces: low-tier berry healing and a small amount of early-game stamina support. A Prickly Pear route is an upgrade over berry farming in any biome that supports both.
• Feeds: the field dressing, stim-shot, and antidote recipes listed earlier. None of these recipes are top-tier, but they are the recipes most likely to be used in a typical mid-wipe session.
• Cannot do: Prickly Pear cannot replace the heavy organic compounds dropped by ARC kills, the salvage from ruins, or the cached supplies from player caches. A run that tries to do all four at once will usually fail at three of the four.

A clean mental model is to treat Prickly Pear as a step in a longer chain. A player who picks up a cluster on the way back from an ARC farm has turned a quiet walk into a productive one. A player who drops into the map specifically to farm Prickly Pear, with no other objective, has usually chosen the wrong resource for the session. The game is built around combined-objective runs, and the resource economy is tuned to reward that pattern.

What the developers have said about flora and extraction design

Embark Studios has been unusually open about the design intent of ARC Raiders, and a few of those design notes matter for any player planning a Prickly Pear route. In a published preview of the game, the developers described flora as a deliberately low-priority resource layer, intended to give players a reason to slow down and read the map rather than rushing from objective to objective. The developers also discussed the per-region regen system in the same preview, framing it as a way to keep resources meaningful in a live, populated map without forcing a global wipe timer that would punish solo and small-squad play.

That framing is useful because it explains why Prickly Pear behaves the way it does. The per-region regen is not a bug, and it is not a placeholder for a future system. It is the system, and it is built to keep flora routes valuable for a player who learns the regional cycle. Players who expect a single global cooldown will be frustrated, and players who learn the regional cycle will be rewarded. The Prickly Pear is one of the easier resources on which to learn the cycle, because its mid-tier status means that a player can experiment without losing much when a route fails.

Adapting the route to squad play, solo play, and different wipes

Most of the advice above is written for a solo player in a normal-wipe session. Three situations need a different approach, and they are worth covering because they are the situations where a player will actually feel the limits of the standard route.

Squad play with a dedicated gatherer

A four-player squad can put one player on a Prickly Pear gather while the other three run a higher-value objective. The gatherer should take the scrubland border route, because the other three will draw attention away from the border. The gatherer should not call extraction on the squad’s main exfil pad, because that exposes the squad’s location. The cleanest plan is for the gatherer to use a peripheral pad, extract alone, and rejoin the squad at the next drop point. The split is a small loss of time, but it preserves the squad’s tactical position.

Solo play in a high-traffic server

Solo play on a busy server is the hardest case, because every peripheral pad is also being watched. The right plan is to skip Prickly Pear entirely for the session and focus on resources that drop from kills and caches, where the higher player density actually helps. A solo player on a busy server who insists on a flora run is gambling the session’s survival on a mid-tier resource, which is the wrong trade.

Late-wipe play after the population has thinned

Late-wipe play, when most players have already extracted or died, is the easiest case for a Prickly Pear run. The regen is slow because the map is empty, but the contested risk is also low. A player who has been holding back on a flora route for the right window will find that the late-wipe window is when Prickly Pear is least contested and least noisy. The trade-off is the standard late-wipe risk: fewer surviving players means a longer wait for any rescue if the run goes wrong.

Troubleshooting a run that produced no Prickly Pear

A player who reaches a known cluster and finds no Prickly Pear should run through a short diagnostic before assuming the spawn is broken. The diagnostic takes about a minute and resolves most failed runs.

1. Confirm the biome is correct. A landmark that looks right from a distance can sit on the wrong biome when the player reaches it. A quick look at the ground texture and the surrounding flora will tell.
2. Confirm the regional cooldown. If the player has been in the region for less than a minute and the cluster is missing, the cooldown is the most likely cause. Wait for thirty to sixty seconds and recheck.
3. Confirm the ARC suppression. If a heavy ARC unit is on top of the cluster’s position, the cluster has been suppressed. Repositioning to a different landmark in the same biome usually solves this.
4. Confirm the player’s server is the same map version. The playtest has run multiple map revisions, and a player who has loaded an older client will see the old landmark layout. Restarting the client is the fix.
5. Confirm the resource is actually missing and not just hidden. The flora shimmer is subtle, and a node can be present but invisible from the wrong angle. Walking a small loop around the landmark almost always reveals it.

If the diagnostic does not produce a node, the right move is to cut the run and rotate to a different biome rather than continuing to search. Time spent searching an empty biome is time that a second squad is using to position on the player.

How Prickly Pear compares with similar resources in other extraction shooters

Players coming from other extraction shooters will recognize the pattern of Prickly Pear, even if the specific plant is new. The comparison is useful for setting expectations, because the resource behaves a little differently from the similar plants in other games.

Resource	Game	Role	Respawn model
Prickly Pear	ARC Raiders	Mid-tier flora, feeds healing and antidote recipes	Per-region timer, influenced by traffic and ARC presence
Hemp	Escape from Tarkov	Early-game healing and barter input	Static spawns, long fixed cooldown per map
Honey	Hunter: Call of the Wild	Low-tier consumable, mainly flavor	Persistent on the map, no cooldown
Shrooms	Cycle: Frontier	Mid-tier healing and craft input	Per-biome respawn with a global minimum
Sample	Returnal	High-tier progression resource	One-time per run, not a respawning flora node

The closest mechanical cousin is the Cycle: Frontier shroom system, which also uses a per-biome timer with a traffic influence. Players who have run shrooms in that game will adapt quickly. Players coming from the static-spawn model of Tarkov will need to unlearn the assumption that an empty landmark is permanently empty, and will need to learn the regional cooldown instead.

A short checklist before leaving the safe zone

Most failed Prickly Pear runs fail because the player skipped one of three checks. A pre-run checklist is the cheapest way to prevent that.

• Confirm the current map version and the landmark names in the in-game map, because playtest patches have renamed several regions.
• Confirm the crafter recipes that take Prickly Pear, and bring any other inputs the recipe needs, so the haul can be turned into a useful item without a second run.
• Confirm the loadout. A flora run wants a quiet weapon, a healing item that does not require Prickly Pear, and a deployable that can serve as a backup extraction if the planned pad is contested.

Each item on the checklist takes less than a minute, and together they prevent the most common reasons a Prickly Pear run ends as wasted time. The list also doubles as a useful mental reset between runs, which is the moment when most players forget the small details.

Frequently asked questions

Is Prickly Pear a rare resource in ARC Raiders?

Prickly Pear is a mid-tier flora resource, not a rare one. The reason it feels scarce is that the regional cooldown is long enough that a single map run will not refill the same cluster, and the spawn weights lean toward a few specific biomes. A player who knows the biome map can gather several units per session, which is enough for the mid-tier recipes that need it. A player who chases the resource across the wrong biomes will perceive it as rare even when it is not.

Can Prickly Pear be traded with other players?

The current build of ARC Raiders does not expose a direct trade interface for gathered resources. The intended flow is to use the resource through the personal crafter or to share the finished craft with a squadmate who is in the same session. Trading through the in-game economy is a feature Embark has discussed for the long term, but the playtest builds do not include it. A player who wants to give Prickly Pear to another player should expect to give the crafted item, not the raw resource.

Do I need a specific tool to gather Prickly Pear?

No. Prickly Pear is gathered by walking up to the node and holding the interact prompt, the same as any flora node. The game does not currently attach a tool requirement to the gather action, and adding one would conflict with the design intent of keeping flora as a low-friction resource layer. A tool that speeds up gathering is a reasonable future addition, but it has not been part of any playtest build to date.

Does Prickly Pear respawn during a single match?

It can, but only across different regions of the map. The regional cooldown is short enough that a player who moves to a different region and back may see a fresh cluster in the original region. The same cluster inside the same region, however, will not refill within a single match in any playtest build. Planning around regional rotation is the right way to use this mechanic.

What is the best crafting recipe that uses Prickly Pear?

The antidote field mix is the most valuable recipe in the current build, because it is the only one that mitigates toxic ARC damage. Toxic damage is rare in some biomes and common in others, and a player who plans to farm ARC units in a toxic-dense region will get more value from the antidote mix than from the healing recipes. For a player who does not intend to fight the toxic ARC units, the advanced field dressing is the better use of the resource.

Is Prickly Pear worth farming in a solo run?

It depends on the server population. On a quiet server, a solo Prickly Pear run is a productive use of a session, because the contested risk is low and the regen is fast enough to support a second cluster. On a busy server, a solo flora run is a poor use of a session, because the contested risk is high and the regen is offset by the other players drawing the ARC attention. The decision is server-state-dependent rather than resource-dependent.

Does weather affect Prickly Pear spawns?

Direct weather effects on Prickly Pear have not been documented in any playtest build. The indirect effects, including reduced sightlines during a dust storm and reduced player traffic during a storm cycle, do change the value of a Prickly Pear run. A player who wants to farm the resource during a storm should expect quieter maps and slower ARC patrols, which is a useful trade in either direction depending on playstyle.

Will the spawn rules change after the game leaves playtest?

Almost certainly. Embark has stated that the flora balance, including the per-region cooldown and the ARC suppression behavior, is still being tuned. The biome map and the basic rules are likely to remain stable, but the specific timers and the exact weight of the suppression mechanic are reasonable places to expect changes. A player who learns the biome map now will carry that knowledge into the live game, even if the timers shift.

Related reading

• Project XL Codes: The Pain of Grinding Low-Tier Mobs
• Subnautica 2 map: what players know about the world so far