Edited By
Julia Forester

Recently, players of Division 2 have ignited discussions around a possible ban wave, with various opinions surfacing on forums. Concerns regarding the fairness of banning players for exploits have emerged, especially following exploits that originated within the game itself.
Many players are questioning the wisdom of a ban wave given the circumstances surrounding recent exploits. One player noted, "The devs own clan was running the glitch. Why ban people for doing the same as them?" This sentiment is echoed by several others who point fingers at developers for the key exploit that users inadvertently exploited.
Player vs. Developer Accountability
Players argue that if the developers issued bans, they would also be penalizing their own community managers who participated in the exploit. An agitated player commented, "If they do a ban wave, they would be banning content creators and their own people too."
The Nature of Exploits
Many believe that the existence of these glitches stemmed from issues within the game mechanics. One user stated, "I didnโt even read it was a glitch โtil the next day." This raises the question: Should players be punished for bugs not of their own making?
Punishment and Consequences
There's skepticism about the effectiveness of past bans. An insightful comment stated, "After the debacle that was the turret glitch, they will absolutely never do anything like that again." This indicates a cautious approach based on previous backlash from the community.
The overall mood ranges from uncertainty to frustration. While some players express support for a ban wave, most sentiment seems to align more with skepticism. Comments like, "Nope, I have farmed both glitches and nothing happened last time," suggest a shared belief that a ban may not materialize anytime soon.
โ ๏ธ Over 50% of players believe a ban wave could erase a significant portion of the community.
๐ฎ The majority of participants engaged in farming glitches without realizing they were exploits.
๐ฅ "They wouldnโt ban people over an unintended exploit" reflects a consensus that faults lie with developers, not players.
This discussion highlights a crucial moment for Division 2โs community. As developments unfold, players await the inevitable decision from the developers, wondering how it will impact their gaming experience.
As the community waits for an official response from developers, itโs likely that a ban wave will face significant reconsideration. Experts estimate there's a 70% chance that any bans will focus primarily on deliberate exploitation rather than punishing players unaware of glitches. Given the developersโ previous missteps, a cautious approach seems prudent. Many believe the developers will opt for a grace period or warning, with about 60% odds that some form of community engagement will precede any punitive actions. Thus, the most probable outcome points toward addressing the underlying game mechanics rather than blanket bans that could alienate a substantial portion of the player base.
Reflecting on the late 90s, when environmental policies began to take shape, one can see a strange parallel to today's division in the gaming industry. Just as industries were called out for polluting practices while pushing the blame onto regulatory oversights, so too are game developers grappling with the responsibility of their software. Just as players feel stuck between loyalty and frustration, communities rallied over the environment invoked a change, suggesting that the key for Division 2 may lie in fostering dialogue about responsibilities between creators and their audiences rather than merely imposing penalties.