So I've been messing around with ARC Raiders since the playtest, and honestly the extraction shooter formula with this weird retro-future aesthetic got me thinking about how I'd actually structure a proper guide site for it. Not just another wiki clone — something that actually helps players make decisions mid-raid.
The core problem with extraction shooters is information density. You need gear stats, map rotations, faction behavior, extract point timings, and loot tables — all at a glance. Most sites just dump everything into long scrollable pages and call it a day. That's useless when you're trying to figure out if the ARC-7 rifle can penetrate Sentinel armor before the patrol swings back around.
I've been sketching out what a companion tool would need:
- Weapon comparison that actually matters — not just damage numbers, but time-to-kill against specific enemy types with different armor zones. The Sentinel tanks have that exposed coolant line on the back, so shot placement completely changes the math
- Dynamic extract maps — elevation matters way more than most people realize. Some extract points are suicide if the ARC machine patrols are in their northern rotation phase
- Crafting chains visualized — the material dependencies get ridiculous once you're pushing for blue-tier gear. A node graph beats a table every time
The game's still in early testing but Embark's doing that thing where they're tight-lipped about exact mechanics. Players are already datamining and frame-counting to reverse-engineer things like the drone aggro radius and resource respawn timers on supply crates.
Actually built a basic stat calculator to test some weapon spread patterns against the training dummy, and the recoil curves are way more nuanced than the in-game bars suggest. The burst-fire ARs have this weird first-shot multiplier that resets differently depending on stance.
Anyway, curious if anyone else has been tracking the machine patrol patterns? I've got partial data for the Crossroads map but the northern sector rotation seems inconsistent during weather events. Wondering if that's a bug or an intended variable.
Top comments (0)