At a glance
- Category
- Side Op
- Credit scope
- Unknown
- Progress persistence
- Unknown
Conditions, conflicts and limits 1
- Prerequisites
- Unknown
Rewards, unlocks and progression 1
- Rewards
- Not established
Uses and connected references 1
- Related Mission
More reference details 3
- Notes
- Use the current Side Op marker. Exact spawn geometry, repeat availability and reward quantities remain unknown.
- Only safes with the active Side Op marker count toward this Side Op. Hold the red-panel interaction; the reported action does not require a key or code.
- Opening the marked safe can also advance the Robbery Order. Its completion banner does not itself extract carried loot.
- Objective Completeness
- Source Described
- Objectives
Image not available for Crack Safe. Use the written reference below.
Saved automatically in this browser only. No account sync.
Crack Safe
These are your notes. Objective checks do not confirm in-game credit, extraction or rewards, and do not complete planner prerequisites.
Clear the entire local mission log, including archived entries? Download an export first if you want a backup. Your atlas and preparation checklist are separate.
Plan the details
Mission context
- Combine with Robbery
The side-op safe can also satisfy Robbery’s safe-opening objective.
Practical route notes
- Open the lock panel Planning tip
Hold the interact control on the safe’s red lock panel until its progress ring finishes. The described interaction needs neither a key nor a code.
Sources and conditions
Where to look
- Where Source description
Only some safes initiate this side op. The tracker cites an All Things How example in a room east of the Haneul Nuclear Reactor dome, marked CRACK SAFE on the Tac-Map. Ordinary safes do not automatically count as this activity.
dmztracker.gg
Open the marked safe with its interact prompt.
- Required order
- Follow the active tracker; conditional route stages can differ.
- Targets
- Not established
Not yet established: who receives credit; extraction required for credit; progress kept between deployments; quantity; must be completed in one deployment.
Back to page sections ↑Connected systems and progression
Read the applicable conditions, reward context and source differences before counting an outcome.