The November 17–23 rotation gives us two things to plan around: a fresh set of weekly objectives and a Cold Snap schedule that deserves a closer check before we commit a loadout. The supplied weekly report highlights container searches, ARC thruster destruction, heavy-ammo damage, ground ARC eliminations, and weapon caches. Our approach is to separate those objectives into manageable runs rather than chase everything in one overloaded raid.
Before sorting our ARC Raiders Items, we would check the active Trials screen, read each objective's exact wording, and confirm the condition attached to our intended map. That preparation matters here because the report mixes straightforward task advice with uncertain scoring details and a personal account of rotation information not matching the game.
We are treating November 17–23 as the reporting window, not as evidence that every listed activity remains available throughout the entire week. The practical question is simple: what can we work toward in the next raid, and what should we verify before spending ammunition, keys, or valuable equipment?
What This Week's Rotation Actually Changes
The weekly report describes five objectives with very different demands. One sends us toward a particular location. Others encourage targeted combat or deliberate looting. That gives us a useful planning framework, but it does not establish exact scoring values, spawn guarantees, or the best route for every squad.
| Objective described | Our recommended approach | Detail to verify in-game |
|---|---|---|
| Open containers at Cielo Sereno Observatory | Plan a focused location run | Eligible containers and required interaction |
| Destroy ARC thrusters | Prioritize visible components over general damage | Which enemies and components award progress |
| Deal damage using heavy-ammo weapons | Combine with suitable combat objectives | Exact weapon or ammunition requirement |
| Destroy ground ARC | Choose fights with a manageable resource cost | Eligible targets and scoring differences |
| Search weapon caches | Follow a compact, familiar loot route | Cache eligibility and any access requirements |

Our preference would be to organize the week around three types of runs: observatory searches, controlled ARC combat, and cache hunting. These are planning categories, not game restrictions. We would combine objectives whenever the route makes sense, but we would avoid forcing unrelated tasks into the same deployment.
There is a difference between refreshing weekly objectives and changing the underlying rotation system. Updated tasks and returning conditions, but it does not demonstrate a complete scheduling overhaul. We would therefore read "rotation update" as a change in the week's available activities, not proof that matchmaking, event timing, or map availability has been rebuilt.
That distinction keeps expectations sensible. A different task list gives us new priorities. It does not, by itself, resolve the schedule mismatch described later.
Observatory Containers: Keep the Run Focused
The location-specific objective is the easiest one to overcomplicate. We would plan to reach Cielo Sereno Observatory, identify eligible containers, perform the required interaction, and leave with a clear understanding of what was registered.
Already-open containers may still be useful. We would not build a route around that assumption without checking. "Open," "search," and "loot" can describe different requirements, and a translated transcript is not a reliable substitute for the wording on the active objective.
Confirm the interaction before repeating the route
For our opening attempt, we would use a loadout we can comfortably replace. The purpose is to establish the route and verify the task, not bring our most expensive equipment into an uncertain interaction.
We would approach the observatory with a primary entrance, a fallback route, and an exit in mind. Inside, we would interact with a clearly eligible container and check for any available progress feedback. If the game only resolves the relevant information later, we would review it before repeating the same actions across another raid.
A previously searched room should not automatically become the foundation of our plan. If open containers count, that is useful information. If they do not, repeatedly visiting depleted rooms wastes time.
Our route recommendation is deliberately conservative: prioritize the objective area, take worthwhile loot that is already on the path, and avoid turning a targeted search into a tour of every nearby building. A short route we can repeat is more useful than a sprawling route whose success relies on several uncertain stops.
For squads, we would also keep communication specific. Calling out "this room is searched" helps more than "there is nothing here." One describes the state of the route; the other may simply mean a teammate did not find anything they wanted.

ARC Thrusters: Aim for the Component
The thruster objective deserves more attention. It asks us to think about what we destroy, not merely how much damage we deal.
Our recommended method is to choose a flying target whose propulsion components we can clearly identify, take a stable firing position, and concentrate controlled shots on one component. We would avoid assuming that every airborne enemy has the same layout or that every apparent engine counts.
That uncertainty is especially relevant when working from a transcript containing inconsistent enemy names. The active task and visible progress should settle eligibility, not a loose list of flying machines.
Assign targets before the squad opens fire
For a coordinated group, we would designate one player to work on the component while the others handle nearby threats and watch the approach routes. If everyone immediately fires into the body, the target may be destroyed before we establish whether the intended component awarded progress.
This is a recommendation for cleaner execution, not a claim about shared credit. We would verify how progress is assigned before deciding who needs to land each hit.
Our preferred firing position would have three features:
- A clear view of the component.
- Nearby cover for disengaging.
- Enough visibility to notice another threat entering the fight.
An open area is not automatically a good shooting position. We would rather have a narrower angle with reliable cover than an uninterrupted view that leaves us exposed from several directions.
After an apparent component destruction, we would reassess instead of continuing to fire by habit. Did the relevant progress register? Is another component still available? Is the target now moving in a way that makes the next shot unsafe?
Those pauses should be brief, but deliberate. Precision objectives become expensive when we treat them like ordinary damage checks.

Pair Heavy-Ammo Damage With Ground ARC Carefully
Heavy-ammo damage and ground ARC eliminations are the most obvious objectives to consider together. Our recommendation would be to identify a suitable ground target, use a weapon that satisfies the displayed ammunition requirement, and check whether both objectives advance.
Weapons include Bettina and Anvil, but names alone should not decide the loadout. We would confirm the active requirement and the weapon's current ammunition classification before spending a raid trying to satisfy the wrong condition.
The same caution applies to larger ground enemies. Bastions and Bombardiers, yet it does not supply a reliable scoring comparison. We would not promise that the largest available enemy offers the best return.
Compare the entire fight, not just the target
Our planning would account for ammunition, healing, exposure time, and the route afterward. A large enemy might suit a prepared squad. It might also consume the resources we need to finish the raid.
| Situation | Our preferred decision |
|---|---|
| Clear firing lane, nearby cover, healthy supplies | Consider committing to the fight |
| Target visible but several approaches are unguarded | Reposition before shooting |
| Ammunition already running low | Avoid starting a prolonged engagement |
| Another group interrupts the encounter | Break contact and reassess |
| Objective progress is secured, and equipment is strained | Favor extraction over an optional target |
We would give each squad member a clear responsibility before engaging: damage, nearby threat control, or observation. Those assignments can change during the fight, but they prevent everyone from concentrating on the same enemy while ignoring the route behind us.
For a solo attempt, we would be stricter about the stopping point. If the fight starts taking longer than expected or consumes our reserve ammunition, we would leave rather than defend an increasingly poor decision.
The aim is not to avoid difficult combat. It is to make sure the fight serves the objective we brought the equipment to complete.
Weapon Caches and Nomad Offers Need Separate Plans
Buried City for weapon-cache searches. We would use that as a route candidate rather than declare it the best option without a direct comparison.
A useful cache route needs compact travel, familiar entrances, and an exit that remains practical when a preferred stop is unavailable. We would build around a few understood locations before adding distant detours.
Keys should fit that route. Carrying several keys without knowing which rooms we intend to visit adds preparation without necessarily improving the run. We would check access requirements and bring only what supports the planned stops.
We would also distinguish weapon caches from ordinary loot containers. A room containing a weapon does not automatically prove that searching it satisfies a cache objective. That is another interaction worth checking before repeating a route.

Read Nomad's offer screen before valuing the trade
Deadline, a Lemons backpack charm, and Anvil II. Its translated offer descriptions, however, mix numbers, item categories, and acquisition terms too heavily to support an exact price guide.
We would not reproduce those figures as settled costs.
Before making a trade, our checklist would cover the reward, quantity, requested payment, purchase limit, and expiration time. Each field answers a different question. An attractive item can still be a poor immediate purchase if acquiring it removes materials we need for the rest of the week.
Our preference would be to keep cosmetic decisions separate from combat preparation. We can want a charm without pretending it improves a raid, and we can evaluate a weapon offer without assuming that buying it is necessary for the current Trials.
Cold Snap: Verify the Schedule Before Calling It Broken
Cold Snap is the strongest part of the original report because it raises a practical problem: the creator describes a mismatch between rotation information and what they could actually access.
That is a useful observation. It is not enough to identify the cause.
Embark's official Map Conditions page lists Cold Snap, includes a server-region selector, and separates active conditions from upcoming entries. Those distinctions give us a concrete starting point for checking a suspected mismatch.
We would compare the same map, server region, and time window across the game and any external schedule. An upcoming event should not be compared with a raid already underway. A screenshot captured earlier should not be treated as a live status display.
Record enough detail to reproduce the problem
Our suggested check is straightforward:
- Confirm the selected server region and the time shown.
- Distinguish the active listing from the upcoming schedule.
- Refresh the information before entering matchmaking.
- Record the selected map and displayed condition.
- Compare that selection with the actual raid.
- Save matching timestamps if the discrepancy persists.
If the information still disagrees, we would describe exactly what differs. "The schedule listed Cold Snap for this map, but our selected raid showed another condition" is actionable. "Cold Snap is broken" skips the evidence needed to understand the problem.
Our Plan for the November 17–23 Window
We would use the opening sessions to settle uncertainty cheaply. Check the objective wording, establish which interactions count, and confirm the selected map condition. Once those details are clear, repeat the routes that actually support the tasks rather than continually changing equipment.
For an observatory run, we would prioritize access and eligible containers. For combat, we would choose either controlled thruster destruction or a suitable ground engagement, combining objectives only when the requirements align. Cache searches would stay focused on a familiar circuit with a practical exit.
We would also keep searches for ARC Raiders Coins for sale separate from the weekly checklist. Our recommendations do not require an external purchase, and an uncertain rotation should not be a reason to spend before checking what the game currently offers.
Before deploying, our team would agree on the main objective, the equipment budget, and the condition that ends the run. That last decision matters: a completed task, depleted ammunition, or an unsafe return route can all be reasons to stop adding optional fights.
If Cold Snap is not available in the selected window, we would move to an objective the active screen allows us to complete. If the displayed schedule still disagrees with the raid, we would preserve the evidence and report that discrepancy without guessing at its cause.