Are the radius and the cell size from the game?
No. Both live in config/fob.ts. The dataset records them as null. The numbers in that config file are provisional estimates until someone measures them in-game.
Planner
FOB base planner
Place constructables on a top-down grid inside an FOB radius. The radius and the cell size are site settings, not figures from the game files.
Game build 25937608
Radius and cell size
| Source | Meters |
|---|---|
| Dataset placement radius | — Not in the game files |
| Dataset cell size | — Not in the game files |
| Config placement radius | 30 m |
| Config cell size | 1 m |
The planner is using a placement radius of 30 m and a cell size of 1 m from config/fob.ts. Both numbers are provisional estimates. They were not measured in-game and are not WARDOGS stats. The dataset rows above stay null.
Cell 0, 0. Center 0.5 m, 0.5 m from the anchor, using the configured cell size. That cell is the anchor FOB.
Arrow keys move the highlighted cell. Enter places or selects. Delete removes the selected piece. R swaps X and Y.
Swap X and Y exchanges the stored horizontal sizes on the grid. The files do not publish a rotation rule.
A piece smaller than one cell still occupies one cell. That snap is the configured cell size, not a game footprint.
Placement rules are the strings on the record. The grid does not turn those words into extra coordinates.
Selected piece
Choose a catalog row, then click a cell inside the circle.
Running totals
Total build cost
30
Costs are the stored numbers added together. The files do not name a unit. A null cost makes the total blank instead of zero.
The anchor row is the Forward Operating Base at the center. It is the radius origin, not a piece stamped from a click.
Nothing else is placed. The total still includes the anchor FOB when that record is present.
- Cells inside the radius
- 2,828
- Occupied cells
- 16
| Piece | Count | Cost | Max health | Cells |
|---|---|---|---|---|
| Forward Operating Base | 1 | 30 | 15,000 | 16 |
| Total | 1 | 30 | 15,000 | 16 |
Catalog
How this planner works
TODO: localization. This section explains the planner. It is not a base guide for a specific map.
The planner puts one FOB at the center when the record Id.Buildable.FOB is in the catalog. The circle is the placement radius from config/fob.ts. The cells are the grid snap from the same file. Neither number is in warpuppies/wardogs-data. The normalized file records both as null and points at the config. While either config value is null, or is not a positive length, this page shows that missing state and does not draw a circle or a grid.
Pieces come from the constructable catalog. A stamp uses the stored X and Y sizes. Z is height and is not a grid axis. Each horizontal axis is rounded up to a whole number of planner cells. That rounding is this page's snap, not a rule from the game files. A piece smaller than one cell still occupies one cell here. Swapping X and Y only changes which stored axis runs along which grid direction. The files do not publish a rotation rule.
The running cost and max health add the stored numbers, including the anchor FOB when that record is present. If any included cost or health is null, the total for that column is blank. A null is not counted as zero. Cells outside the circle cannot take a piece. Occupied cells, including the anchor footprint, cannot take another piece. Placement-rule strings are shown from the record. The grid does not invent coordinates for rules that are only words.
Korean and English carry this explanation. Other languages fall back to English. This planner is not affiliated with Bulkhead or Team17. Catalog numbers come from warpuppies/wardogs-data under the Unlicense. The radius and the cell size do not.
Questions
Why is the total blank?
The total stays blank when the anchor record is missing, or when any included record has a null cost or a null max health. A null is not added as zero.
Does the grid enforce every placement rule?
It keeps a piece inside the configured circle and off occupied cells. It does not add coordinates the files do not contain. Rules remain the stored strings.