Crime Simulator Co-op Heist Planning: From Setup to Extraction
Heist Planning Checklist
Before leaving the hideout, confirm:
- [ ] Target selected from job board or free-roam
- [ ] Security level assessed (locks, NPCs, alarms)
- [ ] Required tools confirmed for each team member
- [ ] Entry point identified (front, back, roof, window)
- [ ] Extraction point agreed (vehicle, alley, rooftop)
- [ ] Role assignments confirmed
- [ ] Hard abort condition set (e.g., 2 police alerts = retreat)
Target Selection
Not all houses are equal. Evaluate each target based on:
Risk Factors
- Electronic locks -- require hacking tool, slow down entry
- NPC occupancy -- more NPCs = higher alert risk
- Neighbor proximity -- tight spacing = noise carries
- Security cameras -- must be disabled or avoided
- Police response time -- varies by map zone
Reward Factors
- Known high-value locations -- safes, jewelry boxes, electronics
- Item request matches -- premium payout if requested items are inside
- Gold bar potential -- high-security targets (Update 1.3)
- Tool upgrade materials -- special loot boxes
Decision Matrix
| Target Type | Risk | Reward | Recommended Team Size |
|---|---|---|---|
| Low-security house | Low | Low | 1-2 (solo farmable) |
| Medium-security house | Medium | Medium | 2-3 |
| High-security residence | High | High | 3-4 |
| Commercial property | High | High | 3-4 |
| Heist location | Very High | Very High | 4 (all roles) |
Entry Route Planning
Every heist should have two entry plans:
Plan A: Primary Entry
- Quietest available route
- Lockpick the back door or side window
- Crawl through basement access
- Stun and bypass NPCs
Plan B: Emergency Entry
- Smash a ground-floor window (loud but fast)
- Use blowtorch on a side wall (very loud)
- Rooftop access via fire escape
Plan B is for when Plan A fails (broken lockpick, unexpected alarm, NPC wandering to your entry point). Switch to Plan B quickly to avoid wasted time.
Inside the Heist
Once inside, follow the team's defined path:
- Clear ground floor -- Lookout confirms no NPCs
- Lockpick internal doors -- Lockpick opens the path
- Secure NPCs -- Sleeping gas + cable ties if occupied
- Loot sweep -- Hauler takes high-value items in priority order
- Safe cracking -- Blowtorch or drill on safes
- Final sweep -- Quick check for missed items
- Extraction -- Regroup at extraction point
Extraction Protocols
Clean Exit
- All players exit through the planned route
- No police alert
- Walk to extraction point (no sprinting -- attracts attention)
- Get in vehicle and drive to next target or hideout
Hot Exit
- Police have been alerted
- Doors are being watched
- Exit through Plan B route immediately
- No further looting
- Each player escapes independently
- Regroup at a secondary hideout location
- If caught, minimize loot loss by dropping low-value items
Evacuation Routes
Know at least two exits from every major room:
| Room | Primary Exit | Emergency Exit |
|---|---|---|
| Ground floor | Front/back door | Window |
| Upper floor | Stairs | Balcony drop (injures but escapes) |
| Basement | Stairs up | Ventilation shaft (if available) |
| Garage | Vehicle bay | Pedestrian door |
Post-Heist: Share and Plan
After extraction:
- Stash deposit -- All loot goes into the shared hideout stash
- Item request check -- Pull requested items for delivery
- Repair session -- Everyone repairs broken tools
- Skill review -- Check if anyone found new skill leaflets
- Next target -- Repeat the planning cycle
The post-heist sync at the hideout is where good teams become great. Share info about police patterns, NPC routes, and hidden loot spots you noticed. This collective knowledge makes every subsequent heist smoother.
Dealing with Failure
Even the best plans fail. When things go wrong:
- One player arrested: Remaining team should abort and start over. Loot from a failed run can still be sold.
- Multiple arrests: Reset at hideout. Take smaller targets to rebuild momentum.
- Tool failure mid-heist: The Driver should have backups. Switch tools and continue, or abort if the backup also fails.
Community Verification & Resources
Data values may shift with patches. Cross-check against community resources before building your strategy.