Have you ever found a loophole in a game that seemed too good to be true? For one Wardogs streamer, it was—and it led to a permanent ban.
Wardogs is a first-person shooter where you play as a mercenary, doing everything from frontline combat to logistics and building forward-operating bases (FOBs). Every action earns you in-game cash, which you can spend on gear or convert to gold—the premium currency for cosmetics—at the end of the season. But streamer KatieRouu and their squad found a way to game the system.
According to the developer, KatieRouu and friends would place dozens of sniper lookout towers around a FOB, then deliberately let the enemy team capture it. Once the base switched control, they'd sit in another FOB stocked with ammo and fire mortars at the captured base. This generated massive amounts of money from destroying enemy structures, plus assist cash from supplying the ammo—all without actually helping their team win. Even a squadmate warned KatieRouu that the tactic wasn't allowed, but she dismissed the concern.
After the ban, KatieRouu challenged the CEO on social media, asking, "So tell me what the exploit was." Joe Brammer, CEO of developer Bulkhead, responded directly: "You know it, I know it… you were taking advantage of an exploit. It's obviously not an intended part of the game." He noted that many players involved quickly converted their exploit earnings into gold bars and skins, calling it "purely a cash loop" with "no gameplay there, nothing organic."
Brammer also revealed that the exploit has been fixed for Season 2 and that data tracking has been added to catch similar behavior. While some players defended KatieRouu, arguing she used legitimate mechanics, Bulkhead stood firm. "We made it clear that known cash & xp exploit abuse will no longer be tolerated," the official account tweeted. "These punishments will stand. This decision is final."
So, what do you think? Was the ban fair, or should KatieRouu have gotten a second chance? Let us know in the comments!
Comments (0)
Log in to join the discussion
Log InNo comments yet