Skip to content
FOBplans

Patch 0.11

How we verify

Menu screenshot, placed blueprint, console stock before and after, HP via C4 count, patch build: the five steps behind every verified value.

  1. 01

    Menu screenshot

    The price in the radial menu is the menu cost. It is charged when you place the blueprint.

  2. 02

    Placed blueprint

    We place the piece on free ground inside the build zone and note the console stock.

  3. 03

    Stock before and after

    At 100% we read the stock again. The difference is the real full-build cost; the factor comes from there.

  4. 04

    HP via C4

    We measure durability with C4 charges until destruction, backed by the planners’ buildable response tables.

  5. 05

    Patch build

    Every value carries the patch number from the main menu. After each patch we re-check the top values within 72 hours.

Cost conventions

We always show the menu cost and, next to it, a full-build estimate: menu cost × 1.333. Planner databases measure this factor consistently (4/3) because supplies also drain per hammer swing. Once we have measured the factor ourselves, the estimate is replaced.

Scale

One grid cell equals one HESCO block, currently 1.5 m (measured footprints). One planner models 1.2 m; the value is disputed and will be re-measured. The isometric preview draws heights in real metres.

Status levels

Draft
Numbers unverified, page not indexed.
Data only
Values consolidated from public sources, conflicts marked with ‡.
Verified in game
Rebuilt, measured and documented with a screenshot by us.

Preview status

Every preview is generated from data. "Checked against screenshot" means the render and an in-game photo sit side by side at the same angle. "Verified in game" means the build was fully rebuilt.

Disputed values

Where sources disagree we show the value we use with ‡ and every alternative in brackets. Cost cards turn that into a range. Nothing is decided silently.

Corrections

Found a mistake? Send us a screenshot through the submit page or via contact. Every correction lands in the changelog with date and source. Changelog · Sources