Reading this field manual

What this site is

This is an unofficial field manual for WARDOGS. It is not published by Bulkhead or Team17, and it is not endorsed by either of them. Nothing on a page is a patch note, a store listing, or a statement from the developer.

The numbers come from the public repository warpuppies/wardogs-data, which is released under the Unlicense. An ingest script downloads that repository, checks each consumed file against the published manifest, and writes a stable set of JSON files into this site. The site build reads those files from disk. It does not call the game, and it does not call the network, while it renders a page.

The header of every page names the game build those files were taken from. For the articles in this chapter, that build is 25937608. When you cite a figure from this site, cite the build in the header. A later ingest can replace the files and keep the same address. If the header build and a remembered number disagree, the header wins.

What the files contain

The home page prints the live counts for this ingest. This paragraph is filled from the same file when the page is built: 40 weapons, 298 attachments, 521 attachment modifiers, 37 projectiles, 23 vehicles, 599 items, 52 loot tables, 3 maps, 6 roles, 131 skills, and 34 constructables. If a later ingest changes a count, the home page changes with it. Treat a count typed into a chat, or remembered from an older copy of this paragraph, as stale until you have checked that table.

The six roles stored by name are Driver, Infantry, Medic, Pilot, Recon, and Support. Each role carries an experience table. Skill trees sit beside the roles. Fewer than half of the skills have per-level effects in the files, and point costs and prerequisites are not in the dataset. This manual does not invent a build order for a skill tree, and it does not assign a role a recommended weapon.

The three maps are Ozeti, Bakurani, and Zestafona. The files name the worlds europe, kavkazi, and north-america. Bounds, objective configs, simplified buildings, and placed objects are in the map records. Tile images and heightmap images are not in the git repository the ingest reads, so this site does not draw a substitute map and does not guess a scale from a picture that is not here.

Icon paths in the dataset point at images that are not in that git repository either. A page does not invent a picture to fill the gap. Where you expected a silhouette, you get the record instead.

Chapters that are open

The weapon index and each weapon page are the working chapter. A weapon page shows the base stats stored on that weapon, the damage-falloff curve when the files include one, the recoil pattern when the files include one, the attachment slots, and a list of fields the files leave empty. Weapons and attachments explains how those pieces fit together before you open a row. It does not repeat the tables.

Forward operating bases explains the constructables file: the FOB record, the pieces placed around it, the placement tags the files actually store, and the two planner values the files do not store. The numbers for a piece belong on the FOB planner, not in that note.

The attachment chapter lives at attachments. Modifier rows, magazine blocks, and slot families are there. This guide names the shape of a row. It does not copy one.

Other chapters described in the site's architecture — vehicles, items, loot, maps, roles, and the attachment simulator — are not given made-up figures here. When a chapter has no page yet, the manual says so instead of sketching a placeholder table. An address in a sentence is the address the manual uses. It is not a promise that the page already answers.

How to read a blank

A blank cell means the game files omit that field. It does not mean zero. A zero is printed only when the files stored a zero. Do not add the two up in your head and treat the blank as a small number, a rounded number, or a number you saw on another weapon.

Two fields are empty on every weapon in this ingest: reload time and ergonomics. The upstream files do not contain them. Every weapon page leaves those rows empty on purpose. Comparing two weapons by a reload time this site does not have is a comparison you invented.

Aim-down-sight time is filled in for only some weapons. A blank ADS row is not a fast weapon. A handful of stored ADS values are far too large to read as a person's time-to-aim in seconds. The weapon page prints them as stored and marks them as implausible. It does not rescale them into a stopwatch reading, and it does not drop them to make the column look tidy.

Damage is not a single weapon field. A projectile carries a base damage, and a falloff curve multiplies that by distance. The weapon page shows the projectile's base damage only when the weapon's caliber token matches one projectile id exactly. When a caliber fans out into several projectile ids, the cell stays blank. The site does not pick a variant for you. The weapons note walks through that rule with the M4 and the M500, and the weapon pages are where the cells are.

Distances in the files are meters. Speeds are meters per second. The site does not convert a stored value into a friendlier unit, and it does not average the weapons that do have a value in order to fill one that does not.

Languages

Korean is the default language of this site. English is the fallback. A string that is missing, or an empty string, is read from the English file. These guides are written in Korean and in English. Every other language on the switcher opens the English article until a translation is filed beside it. The switcher does not machine-translate a page, and it does not mix a Korean paragraph into an English one.

Names of weapons, attachments, maps, roles, and constructables are the display names stored in the files. They are not community nicknames. Where a record has no display name, the stable handle is the id. The FOB note lists the constructable records that are in that state. Do not coin a short name for them in a citation.

What this manual will not do

It will not rank a weapon. It will not recommend a loadout, a sight, or a base layout. It will not fill the leaderboard with sample standings. Live standings come from the game server, which is outside these files, and that route stays empty of invented rows.

It will not quote a muzzle velocity, a recoil sample, a piece's cost, or a piece's health inside these articles. Those figures exist, when they exist, on the data pages, tied to one build. Copying them into a paragraph is how a manual goes stale while looking confident. Follow the link, and read the cell.

It will not treat a developer record as if it were issued kit, and it will not hide one. The weapon file contains test records alongside the weapons a soldier is meant to hold. The weapon index prints a dev mark only when that weapon's record sets the flag.

Where to go next

If you want the tables, open the weapon index. If you want the shape of a weapon record, a caliber join, and an attachment modifier before you trust a column, read weapons and attachments. If you are looking at buildables, read forward operating bases and then the FOB planner. The planner's placement radius and grid snap are not in the dataset. The guide says what that absence means. It does not supply a radius of its own.