Source desk

Sources & patch notes

What is stable doctrine, what is patch-sensitive, and how to keep the manual trustworthy after Hell Let Loose updates.

Patch-sensitiveCommunity-derived dataUse doctrine confidently; recheck exact values

Roles, vehicle costs, damage behavior, artillery values, and map data should be verified after major patches.

Trust model

Stable vs patch-sensitive guidance

The manual separates durable public-match doctrine from exact values that can change.

Stable doctrine

Spawn discipline, garrison layers, active defense, concise comms, smoke before crossings, armor with infantry screens, and recon pressure on logistics remain useful across patches.

Patch-sensitive

Tank damage, fuel costs, exact loadouts, artillery behavior, vehicle roster labels, map variants, and balance changes need live verification.

Community-derived

Map plates, possible capture points, tank images/identifiers, and Tank Bible-era armor lessons are treated as field references, not official current data.

After a patch

Update checklist

Run this whenever HLL receives a major update.

  1. Check official patch notes for role, weapon, vehicle, artillery, and map changes.
  2. Verify tank classes, costs, names, and image identifiers in the Tanking page.
  3. Spot-check map images, default garrisons, possible capture points, and layer overlays.
  4. Re-test artillery calculator values and danger-close guidance.
  5. Review beginner recommendations for any loadout or meta shifts.
  6. Run the maintenance checklist, browser console checks, and cache-bust changed assets.

Open full maintenance checklist

Credits and disclaimers

Reference notes

Hell Let Loose names, icons, maps, and vehicle references are used for guide/reference purposes. This site is not affiliated with Team17, Expression Games, or Cover 6 Studios.

Patch audit ledger

What to re-check after every major update

Use this table to keep claims honest without watering down durable strategy.

TopicDurable guidancePatch-sensitive dataIntentional non-claims
TankingCrew rhythm, kiting, infantry screens, angle discipline.Costs, roster labels, penetration/damage behavior, vehicle availability.Exact current shot-count tables unless verified live.
MapsTerrain family behavior, spawn-web logic, choke discipline.Map variants, default markers, capture-point possibilities.Guaranteed live garrison/capture locations.
RolesSupport enables garrisons, Engineer enables economy, SL controls tempo.Loadouts, role limits, weapon availability.One fixed meta role list for every server.
ArtilleryObserver correction, splash calls, munition discipline.Mil curves, shell timing, commander resource costs.Perfect ballistic truth beyond calculator reference.
Patch audit runbook

Revalidate the risky facts first

After a Hell Let Loose update, audit the manual in this order so stale data does not hide inside polished prose.

1. Tanks and vehicles

  • Roster names and class labels.
  • Fuel costs and spawn-menu availability.
  • Damage/penetration assumptions and special vehicle behavior.

2. Roles and loadouts

  • Beginner-safe role advice.
  • Support/Engineer supply interactions.
  • AT, satchel, mine, and repair-station assumptions.

3. Artillery and resources

  • Mil conversion behavior and splash assumptions.
  • Munitions/resource economy.
  • Danger-close and counter-battery recommendations.

4. Maps and spawns

  • Map imagery and geometry changes.
  • Default garrison overlays and capture-point locations.
  • Opening-move cards for new or reworked maps.

5. Usability smoke test

  • Can a new player find the first-10-min route?
  • Can an SL find collapse decision trees?
  • Do search terms like “no garrisons”, “spawn trapped”, and “tank ricochet” work?

Publish rule

If exact values are not verified, keep them labeled patch-sensitive and prefer durable doctrine over false precision.