Choose whether this is build, route, mod or utility work.
Avoid: Read random pages without a save-state question.Cyberpunk 2077 · Mods
Cyberpunk 2077 Gameplay Mods: mod safety and dependency checks
Use this page when gameplay mods affects your current Cyberpunk 2077 route and you need a safe next action.
Primary sections
Start with your problem
Players need gameplay mods guidance that fits their save state, patch scope and build route instead of generic text.
The Gameplay Mods page connects the topic to route state, sources, risks and a next action so it can support real play.
Check original sources and version scope.
Avoid: Install or delete files first.Use only requirement rows until you need details.
Avoid: Open full story walkthroughs too early.Problem solver
Diagnose the gameplay mods blocker
Start from the state that can actually change your next action.
No clear next step
Gameplay Mods is being treated as a broad topic.
Choose whether this is build, route, mod or utility work.
Do not: Read random pages without a save-state question. Use the action map.Patch or mod uncertainty
The source may be stale or modded assumptions may apply.
Check original sources and version scope.
Do not: Install or delete files first. Use source chips.Spoiler risk
The page may reveal route outcomes.
Use only requirement rows until you need details.
Do not: Open full story walkthroughs too early. Use checklist.Playable tools
Use this while planning your route
These tools turn the guide into a quick decision surface for boss attempts, builds, quests and backups.
Decision tool
Gameplay Mods next-action selector
Pick the current blocker and get the safest next action.
Choose the current state to get the next action.
Checklist
Gameplay Mods verification checklist
Use this before changing a live save or route.
Video
Cyberpunk 2077 official Steam trailers and media
Open the official Steam store media section for current trailers, screenshots and publisher-provided video assets.
Open official Steam mediaStructured data
Real entries to check while playing
These tables turn the page into a working reference instead of a text-only article. Exact values should stay tied to the source trail and update date.
Database
First route and system facts
| Decision point | Source-backed fact | Player use | Risk | Next action | Verification | Sources |
|---|---|---|---|---|---|---|
| Character start | The lifepath choice is Nomad, Streetkid or Corpo. | Set roleplay expectation without treating it as a class system. | Restarting only because the opening flavor feels wrong wastes time. | Pick the lifepath for dialogue flavor, then plan attributes separately. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Lifepaths page |
| First attribute spend | Body, Reflexes, Technical Ability, Intelligence and Cool are the core attribute families. | Choose a combat direction before spreading points. | Even spread delays the tools your build actually needs. | Pair one combat attribute with one utility or cyberware attribute. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Attributes pageCyberpunk Wiki Body pageCyberpunk Wiki Reflexes pageCyberpunk Wiki Technical Ability pageCyberpunk Wiki Intelligence pageCyberpunk Wiki Cool page |
| Body route | Body is the attribute page tied to heavy physical combat direction. | Use it when survivability, blunt weapons or heavy weapon pressure is the goal. | It does not solve stealth, netrunning or precision by itself. | Commit only if your main combat loop wants close pressure. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Body pageCyberpunk Wiki Attributes page |
| Reflexes route | Reflexes is a core attribute page for mobility and fast weapon pressure. | Use it for blades, aggressive gunplay and movement-heavy routes. | Mobility does not replace cyberware capacity or hacking tools. | Pair with Technical Ability or Cool depending on weapon plan. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Reflexes pageCyberpunk Wiki Attributes page |
| Technical route | Technical Ability is a core attribute page connected to tech tools and cyberware planning. | Use it when the build depends on cyberware capacity, tech weapons or item utility. | Raw tech investment without a weapon plan feels slow early. | Choose whether tech supports a weapon build or a cyberware-heavy build. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Technical Ability pageCyberpunk Wiki Cyberware page |
| Netrunner route | Intelligence is the attribute page tied to quickhack and cyberdeck planning. | Use it when stealth hacking or RAM-based combat is the intended loop. | A netrunner plan needs cyberdeck and RAM support, not just attribute points. | Check quickhack and cyberware pages before spending broadly. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Intelligence pageCyberpunk Wiki Quickhacks pageCyberpunk Wiki Cyberware page |
| Stealth route | Cool is a core attribute page for stealth and precision-oriented planning. | Use it when pistols, precision pressure or stealth routing is the goal. | Cool cannot cover every loud fight if you ignore backup damage. | Keep one reliable combat option for forced encounters. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Cool pageCyberpunk Wiki Attributes page |
| Cyberware planning | Cyberware is its own system and should be planned alongside attributes. | Treat implants as build infrastructure, not random upgrades. | Installing whatever is affordable can waste capacity and money. | Pick cyberware that supports your main loop first. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Cyberware pageCyberpunk Wiki Technical Ability page |
| DLC awareness | The Relic perk tree is tied to Phantom Liberty route planning. | Do not compare Relic choices to base-game attribute points as if they are the same resource. | DLC-specific guidance can confuse base-game-only saves. | Mark whether the save includes Phantom Liberty before following Relic advice. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Relic pageCyberpunk 2077 Steam store |
| Ending safety | Nocturne OP55N1 is the endgame gateway players should treat as a route checkpoint. | Clean up side jobs, romance routes and iconic weapon pickups before pushing final choices. | Rushing the finale can hide ending and completion options. | Make a manual save and review ending requirements before entering. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Nocturne OP55N1 pageCyberpunk Wiki Endings page |
| Iconic weapon habit | Iconic weapons are tracked as a distinct weapon category by the Cyberpunk Wiki. | Check quest-linked weapons before leaving major missions. | Some iconic sources are easy to miss during one-time mission spaces. | Open the iconic weapon page before major story missions. | source-backed fact high confidence 2026-05-09 | Cyberpunk Wiki Iconic Weapons pageCyberpunk Wiki Dying Night pageCyberpunk Wiki Satori page |
| Mod boundary | CD Projekt RED provides an official REDmod support page for modding support. | Separate official mod tooling from random fix packs. | Unknown executables and outdated loaders can break the install or save. | Back up saves and use original mod pages only. | source-backed fact high confidence 2026-05-09 | Cyberpunk official REDmod support pageREDmod Steam tool pagePCGamingWiki Cyberpunk 2077 page |
Player problem
Players need gameplay mods guidance that fits their save state, patch scope and build route instead of generic text.
The Gameplay Mods page connects the topic to route state, sources, risks and a next action so it can support real play.
When gameplay mods matters
This page is for the moment when gameplay mods changes a build, route, mod state or save decision.
- Check whether gameplay mods is a build, route, mod or utility problem.
- Use the linked source rows before applying exact facts.
- Keep base game, Phantom Liberty and modded saves separate.
How to use gameplay mods safely
The page should answer the next action first, then send the player deeper only when needed.
- Protect saves before irreversible choices.
- Use original mod or official support sources for technical topics.
- Avoid spoiler-heavy sources until the route actually needs them.
What to ignore for now
Not every gameplay mods detail is useful on a live save.
- Ignore collector-only details unless completion is the goal.
- Do not change mods while debugging story route problems.
- Do not chase exact values without source dates.
Gameplay Mods action map
| Current need | Use this source layer | Next action |
|---|---|---|
| Gameplay Mods changes build planning | Attribute, cyberware or item source | Return to the build spine before spending. |
| Gameplay Mods changes route planning | Quest, ending or romance source | Make a manual save before advancing. |
| Gameplay Mods changes technical state | Official support, PCGamingWiki or original mod page | Change one variable and retest. |
Action checklist
Do this in order
- Open the Gameplay Mods source chips.
- Confirm base game, Phantom Liberty or modded scope.
- Make a manual save if route state can change.
- Pick one next action and retest.
FAQ
Common questions
Is Gameplay Mods mandatory?
Only when it affects the current build, route, mod or utility problem.
Why not give one universal answer?
Cyberpunk 2077 choices depend on save state, DLC scope, build direction and mod state.
Sources