Killer • Common • Information
Vigo's Blueprint
Hatch-routing twin to Annotated Blueprint, but biased toward main landmark building.
Verdict: Utility and economy tech. Strong in the right session, dead in the wrong one.
Stacking
Special
Uses custom conflict/priority rules. Check exact effect details below.
Risk profile
High-variance
Can spike hard, but can also underperform depending on lobby/map state.
Last verified
2026-02-16
What it does
Increases Hatch spawn likelihood near the map main landmark building.
Exact effect
Increases Hatch spawn likelihood by +100% near the map main landmark building, if available.
When to use
- Your build is explicitly built around basement conversion.
When not to use
- Your killer has weak basement pathing and carry tools.
Do this now
- Use ward/legacy offerings when inventory management is the true objective.
- Treat utility offerings as tools for defined scenarios, not defaults.
- Maintain stock tracking so rare utility offerings are used intentionally.
- Confirm patch-relevant behavior for Vigo's Blueprint before treating it as solved meta.
Avoid this now
- Do not burn rare utility offerings without clear return.
- Do not mistake inventory protection for in-match pressure.
- Do not autopilot Vigo's Blueprint because of one good memory.
Best pairings
- carry control perks
- territory-denial powers
Counterplay
- Punish low-pressure utility selections with faster tempo play.
- Force high-decision states where utility picks cannot stabilize macro.
Common fail cases
- Running protection offerings in matches where item/add-on value is low.
- Ignoring tactical offerings when match winrate is the priority.
Common misconceptions
- Even favorable basement spawn can be unplayable if map side control fails.
Patch history
8.6.0
No verified gameplay change.
FAQ
Do ward offerings help winrate directly?
Usually no. They protect inventory value; match win impact is indirect.
When are utility offerings best?
When your session goal is inventory management, challenge completion, or controlled testing.