The following warnings occurred:
Warning [2] A non-numeric value encountered - Line: 499 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 499 errorHandler->error
/global.php 459 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 499 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 499 errorHandler->error
/global.php 460 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 394 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 394 errorHandler->error
/global.php 466 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 395 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 395 errorHandler->error
/global.php 466 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 396 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 396 errorHandler->error
/global.php 466 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 474 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 474 errorHandler->error
/global.php 466 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 499 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 499 errorHandler->error
/global.php 818 my_date
/showthread.php 24 require_once
Warning [2] A non-numeric value encountered - Line: 394 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 394 errorHandler->error
/inc/functions_post.php 163 my_date
/showthread.php 1063 build_postbit
Warning [2] A non-numeric value encountered - Line: 395 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 395 errorHandler->error
/inc/functions_post.php 163 my_date
/showthread.php 1063 build_postbit
Warning [2] A non-numeric value encountered - Line: 396 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 396 errorHandler->error
/inc/functions_post.php 163 my_date
/showthread.php 1063 build_postbit
Warning [2] A non-numeric value encountered - Line: 474 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 474 errorHandler->error
/inc/functions_post.php 163 my_date
/showthread.php 1063 build_postbit
Warning [2] A non-numeric value encountered - Line: 499 - File: inc/functions.php PHP 7.4.33 (Linux)
File Line Function
/inc/functions.php 499 errorHandler->error
/inc/functions_post.php 365 my_date
/showthread.php 1063 build_postbit



Hello There, Guest!
View New Posts   View Today's Posts
RSVSR Tips for Spotting Comets and Securing Igniters ARC Raiders

  • 0 Vote(s) - 0 Average


02-26-2026, 08:33 AM #1
Hartmann846
Junior Member
**
Posts: 4 Threads:4 Joined: Feb 2026 Reputation: 0 Stance Fencesitter

RSVSR Tips for Spotting Comets and Securing Igniters ARC Raiders
Hunting down a Comet Igniter in ARC Raiders sounds simple on paper, right up until you've watched a Comet roll in, panic, and leave with nothing but junk. I started treating it like a tiny mission with a timer, not "loot I might bump into." If you're still figuring out what you even need and why, I kept a checklist open from ARC Raiders Items so I didn't waste runs chasing the wrong parts.

 The big issue isn't finding a Comet. It's finishing it properly. Comets have that nasty habit of blowing themselves up if they get too close or if you drag the fight out. When that happens, the loot you actually care about is gone. So don't play it like a normal brawl. Keep space, keep line of sight, and commit to damage. People talk about high-impact options like the Hullcracker or the Anvil for a reason. You're trying to crack armor fast, get to the core, and end it before the "I'm about to explode" moment even has time to happen.

 You'll save yourself a lot of frustration by sticking to open areas where a Comet can drop in and roll around. I've had consistent spawns around Dam Battlegrounds, especially near the Control Tower, and Buried City can work too if you sweep the wide plaza north of Plaza Rosa. On Blue Gate, I'd loop the Warehouse Complex and nearby open lanes. Stella Montis is a trap for this—too vertical, not enough open sky, and you'll spend the whole session hoping. One thing that helps: don't just look, listen. There's usually a heavy roar and a sky streak before impact, and if you catch the landing early you can set up instead of sprinting after it.

 Once you drop it the right way, the loot comes in pieces. The outer ring tends to be the boring stuff, while the central core is what you're really here for. That's where the Igniter shows up. If you've heard complaints about looting being finicky, yeah, it happens. Sometimes the prompt feels awkward or you've got to move a step left and try again. Still, if you beat the self-destruct and didn't get wiped by the blast, you should be able to pull it. And it's worth it, since Igniters feed into bigger goals like the Weather Monitoring System project and crafting the Deadline explosive weapon.

 I treat Comet runs like quick, repeatable loops: rotate open zones, listen for the drop, kill fast, loot core, extract before another squad shows up. If you're short on time or you're trying to finish a project without burning a whole weekend, it can also help to gear up efficiently through trading or item services; I've seen players use RSVSR to pick up game currency or items so they can stay focused on the Comet fight instead of rebuilding after every bad run.







Users browsing this thread: 1 Guest(s)