The appeal of a PvE lobby in ARC Raiders is straightforward: fight the machines, take on dangerous bosses, collect valuable loot, and make it to extraction without worrying about another Raider shooting you down. The Queen can still tear through an unprepared squad, and a failed extraction can still cost you a backpack full of hard-earned ARC Raiders items for sale. But other players are not supposed to be able to damage you in the new PvE test. Recent Reddit reports have raised questions about how that promise holds up in practice. One player claims that he and his teammate were knocked down by other Raiders after defeating the Queen, despite believing they were in a PvE-only lobby. In a separate incident, another player says a stranger used the promise of a blueprint to lure him into a room, then blocked the exit until the match timer ran out. These are two different problems, but both strike at the same concern: what happens when the risks of a raid come from other players in a mode designed to limit that kind of interaction? The reports do not prove that ARC Raiders has a widespread PvP damage exploit, nor do they establish that every PvE lobby is unsafe. However, they raise legitimate questions about the game's damage restrictions, physical interactions, and the risks players face when carrying valuable equipment. The Queen Fight That Allegedly Ended in a PvP Kill Reddit user u/Difficult_Offer3942 described an encounter that reportedly took place shortly after a group of Raiders defeated the Queen. According to the post, two players suddenly opened fire and managed to down both the poster and his teammate. The problem was not simply that another squad had turned hostile. The poster believed he was in a PvE-only lobby, where player-to-player damage was supposed to be disabled. One detail makes the account particularly puzzling. Earlier in the same match, the poster's teammate had accidentally shot another squad while fighting the Queen. Those shots reportedly caused no damage, suggesting that the PvE protection was working as expected at that point. Yet the later encounter appeared to produce a completely different result. If the events happened as described, why did the earlier shots fail to hurt other Raiders while the later attack allegedly knocked down two players? The consequences were substantial. The poster said he lost a fully equipped loadout and two reactors. For Raiders who spend time preparing for a difficult boss encounter, valuable equipment can represent a significant investment. Losing it after a fight they had already won would be frustrating under any circumstances. Losing it to an attack that should not have been possible makes the situation even harder to accept. Was It a Bug, Cheating, or Something Else? The available account does not establish what caused the incident. The player questioned whether cheating or a bug in the new PvE mode was responsible, but neither explanation has been confirmed. A matchmaking mistake, an unexpected technical issue, or another factor would need to be investigated before anyone could identify the cause. It would also be premature to claim that players have discovered a repeatable way to bypass PvE damage restrictions. For now, this remains a player-reported incident rather than a confirmed exploit. Still, the distinction matters to anyone entering a raid with expensive gear. If a player selects PvE because the mode disables damage from other Raiders, they should be able to rely on that rule. An unexplained death can turn an otherwise successful Queen run into a costly loss and leave players questioning whether the mode is behaving as intended. The Blueprint Trap: When Another Raider Becomes the Obstacle The reported Queen encounter concerns damage. A second Reddit post highlights a different way a PvE raid can go wrong. In that account, a player said another Raider lured him into a room by claiming to have a blueprint. The poster followed the stranger inside, apparently expecting a chance to obtain a valuable item. Once inside, however, the other player allegedly blocked the exit. The poster said he could not get out before the match timer expired, and both players ultimately died. He later asked the community whether there was a mine or another item he could throw to knock the blocking player out of the way. The appeal of a blueprint is easy to understand. Crafting unlocks and progression items can be valuable finds, and an offer from another Raider might seem worth investigating. But a confined room with only one exit creates an obvious disadvantage if the encounter turns hostile. The alleged trap did not require the other player to shoot anyone. Instead, the obstruction itself became the problem. That distinction is particularly important in ARC Raiders. Disabling PvP damage does not automatically mean players can no longer interfere with each other's movement. Depending on the environment and available equipment, a blocked doorway can prevent someone from leaving even when direct attacks are ineffective. The result can still be a failed extraction and the loss of whatever items the trapped player was carrying. The poster acknowledged that accepting the offer was a mistake. Even so, the incident raises a fair question: should a player be able to turn a friendly-looking interaction into an unavoidable trap simply by occupying the only exit? Door Blocking and PvP Damage Are Two Different Problems Embark Studios' PvE test rules help explain why these incidents should not be treated as identical. The studio stated that player-to-player damage would be disabled during the limited test. It also explained that certain physical interactions, including barricades and ziplines, would remain unaffected. That means the PvE mode was not intended to remove every form of interaction between Raiders. Some environmental and physical mechanics remain part of the experience. The distinction creates two separate issues. Unexpected PvP damage: If a player is correctly matched into the PvE mode and another Raider can genuinely damage them with ordinary attacks, that would conflict with the stated rules and warrant investigation. Physical obstruction: If another player blocks a doorway or uses an allowed physical interaction to prevent someone from leaving, the situation may not violate the literal no-damage rule. It can still be disruptive and may justify changes to how collision or griefing is handled. This difference matters because the solutions may be different, too. A damage anomaly requires an explanation of what happened to the damage restrictions. A door-blocking problem may require changes to player collision, environmental interactions, or the ability to escape an obstruction. The two Reddit reports do not prove that either problem is widespread. They do, however, show why players need a clear understanding of what PvE protects them from and what risks remain. Why Losing Items in PvE Feels Different ARC Raiders is built around risk and reward. Players collect weapons, materials, crafting resources, ARC Riders blueprints, and other valuable items while trying to survive long enough to extract. A failed run is part of that loop. A powerful ARC enemy can overwhelm a squad, a boss fight can consume more resources than expected, and an unsuccessful extraction can mean losing equipment. But players make decisions based on the rules of the mode they choose. Someone entering a conventional PvPvE raid knows that another Raider may be a threat. Someone selecting a PvE lobby expects a different balance of risk, with the main challenge coming from ARC machines and the environment. That expectation is why the Queen report has attracted attention. The poster claims that the squad had already defeated a major enemy before another group allegedly knocked them down. The loss of two reactors and a fully equipped loadout made the outcome more painful, but the underlying concern is whether the selected mode behaved as expected. The door-blocking report raises a related issue. Even when direct player damage is disabled, a Raider can still lose valuable items if another player prevents them from reaching extraction. For solo players and squads looking for a more cooperative experience, those situations can undermine the appeal of PvE. The point is not to eliminate danger from ARC Raiders. It is to ensure that the dangers players face match the rules they signed up for. How to Protect Your Loadout in ARC Raiders PvE Lobbies Until the circumstances behind these reports become clearer, players can take a few practical precautions. 1. Be cautious about blueprint offers from strangers. A player offering a blueprint may be acting in good faith, but there is no need to follow someone into a confined room to investigate. Ask them to meet in a more open area where you have space to move and more than one possible escape route. 2. Check the exits before entering a confined space. A narrow doorway can become a serious disadvantage if another player blocks it. Look for alternative routes before committing to an enclosed area, particularly when carrying valuable items. 3. Do not assume a mine or grenade will solve a body-blocking problem. The player who reported being trapped specifically asked whether an item could move the obstructing Raider. However, the available account does not establish a reliable solution. Do not assume that equipment designed to damage or disrupt ARC enemies will necessarily push another player out of the way in a PvE lobby. 4. Consider your loadout when testing unfamiliar situations. If you are experimenting with the mode or exploring areas where you may encounter unpredictable player behavior, bringing equipment you can afford to lose can limit the consequences of a failed run. This is a precaution, not a substitute for reliable game rules. 5. Record suspected damage anomalies. If another Raider appears to damage you in a PvE-only lobby, capture the encounter if possible. Evidence showing the selected mode, the attack, and the resulting damage can help clarify what happened. Repeated reports with clear footage are more useful for investigating a potential issue than speculation about its cause. None of these measures guarantees a successful extraction. They simply reduce the chance of being caught unprepared while the community tries to understand these reports. Will Embark Change the PvE Rules? The incidents leave two questions for Embark Studios. The first is whether the reported Queen-fight deaths can be explained by a matchmaking mistake, a technical issue, cheating, or another cause. The available evidence does not establish the answer, and the report should not be treated as proof of a confirmed PvP damage exploit. The second is whether the current physical interaction rules provide enough protection against deliberate door blocking. One possible approach would be to prevent sustained player obstruction from completely sealing a narrow exit. Another would be to provide a reliable way to escape when another Raider deliberately blocks the only available route. These are potential design solutions, not announced changes. Ultimately, the two issues need to be evaluated separately. If the damage restrictions are not functioning correctly, players need a clear explanation and a dependable fix. If physical obstruction is an unintended consequence of the current rules, Embark may need to decide how much interference should be possible in a mode intended to support cooperative play. For now, neither Reddit report establishes how widespread these situations are. But both highlight the importance of making the PvE experience predictable and fair. Players are not choosing PvE because they expect every raid to be easy. They are choosing it because they want to face the dangers of ARC Raiders without the same threat of direct player combat. If an unexplained attack can cost a squad its equipment after a Queen fight, or a promise of a blueprint can end with a player trapped until the timer runs out, that expectation becomes harder to maintain. Have you encountered unexpected PvP damage in an ARC Raiders PvE lobby, or been trapped by another Raider blocking a doorway? Share your experience and any method that helped you escape. Specific reports may help the community determine whether these are isolated incidents or problems that deserve a broader fix.

As the official 1.0 release of Path of Exile 2 approaches, it is clear that, beyond the already announced new content, the development team is poised to implement significant, unprecedented changes to the endgame. Following several leagues of refinement during the early access phase, Path of Exile 2 endgame is steadily maturing. However, Atlas of Worlds, the cornerstone of this experience, while offering immense freedom, also reveals several flaws that demand attention. In this analysis, we examine the current state of Atlas system, covering exploration mechanics, questline design, and the passive skill tree, to explore how the development team might enhance the experience for 1.0 launch. Optimizing Atlas exploration experience While Atlas system in the original game relied primarily on a traditional, menu-based map selection interface, Path of Exile 2 Atlas embraces a more expansive, infinite design, presenting Atlas and its landscapes as a vast, explorable space. Specifically, players can venture in any direction, pushing into Fog of War to uncover new regions, unique maps, and specialized zones containing powerful, rare modifiers. If fully realized, this mechanic could grant Path of Exile 2 an unparalleled level of immersion. Currently, however, Atlas exploration experience feels somewhat thin, lacking sufficient feedback and moments of genuine surprise. Another area for improvement lies in the tower mechanic and the potential for long-range exploration. As a key component of Atlas system, these towers initially served to shroud surrounding areas in fog. Now, however, exploration has become the core purpose of these zones; completing a Tower map reveals a significant portion of the surrounding territory. We believe there is ample opportunity to enrich these maps, for instance, by allowing players to actively choose and unveil deeper, fog-shrouded regions. This would not only increase the utility of various Tower maps within Atlas system but also provide a stronger incentive for exploration, after all, completing more maps translates to the potential for earning more PoE 2 currency. In short, exploration should be a core pillar of Path of Exile 2 Atlas. If the act of exploration itself isn't engaging, then the very concept of Atlas, a vast, infinite world of maps, loses its purpose. Potential improvements for endgame questlines Initially, Path of Exile 2 endgame felt somewhat aimless; it lacked a clear sense of direction, which could make the experience quite confusing for players. Fortunately, the introduction of questlines in Patch 0.5.0 went a long way toward addressing this. Especially during the early stages of a new league, these questlines help players plan their Atlas Tree more effectively while providing a compelling role-playing experience. However, as of Patch 0.5.5, these endgame questlines have begun to reveal some underlying issues, such as visual clutter caused by an overcrowded UI, and the fatigue that sets in from repetitive gameplay. Perhaps the most challenging issue is spatial limitation. Currently, Path of Exile 2 Atlas uses a fixed layout. As more core league mechanics are added leading up to the 1.0 launch, there may simply not be enough room on the map to accommodate everything. This would not only lead to a disorganized and chaotic Atlas, but it could also cause other problems, for instance, forcing certain mechanics to spawn extremely far from the starting point, which would significantly detract from the player experience. What are the flaws in Atlas Tree? While a well-configured Atlas Tree can greatly enhance your endgame mapping experience, some of its current mechanics, such as how passive points are earned and how the tree is structured, have clear shortcomings. For starters, the acquisition of Atlas passive points is currently tied strictly to Fortresses. You must complete maps within these Fortresses, or even rush directly to them to finish specific questlines, just to earn points; otherwise, you cannot access the bonuses provided by Atlas Tree. We believe Path of Exile 2 development team should allow players to earn passive points by engaging with any content within Atlas. Tying point acquisition to specific mechanics like Fortresses severely limits player freedom and forces everyone into a narrow, singular strategy for progression. Furthermore, the current Atlas Tree is far too expansive and cluttered with a multitude of low-value nodes. Pruning some of these and consolidating the remaining nodes more efficiently would make every passive point investment feel significantly more meaningful. Streamlining tablets and biomes Planning a specific mapping strategy in Path of Exile 2 currently involves a tedious amount of upfront preparation, whether it's the previous reliance on Towers to boost map returns or the current focus on city biomes. At present, the disparity in rewards between city-themed zones and other areas is too vast. This effectively forces players to prioritize city zones, severely limiting the diversity of viable choices. Moreover, the design choice to grant specific biomes exclusive drop bonuses via Atlas Tree tends to funnel players toward a single optimal path. This traps players in an endless, exhausting search for the best biome, wasting both time and energy. As for Tablets, the complexity is compounded by the sheer variety of types available, combined with a random re-rolling mechanic for affixes. Many of these affixes are entirely useless, while others are so powerful that they dictate the upper limit of your mapping potential. Given this, we believe a system similar to Scarab fragments from Path of Exile 1, a plug-and-play approach, would be a better alternative. This would drastically reduce the burden of preparation, allowing players to consume more time actually engaging with the game's core content. Ultimately, as a vital component of Path of Exile 2, Atlas system requires further refinement. To ensure it remains consistently rewarding, and to avoid disappointing players, the development team will need to implement additional changes as we approach the 1.0 launch and beyond!