Hearts of Iron 4 mythical nomenclature

I recommend replacing the loosely historical M/P/B/C system with a unified Joint Materiel Designation System: every HOI4 production design begins with a compact operational code, then ends with the D&D creature flavor name.

The result is immediately readable in a production queue: who uses it, what it is, what it does, its generation, and its principal fit all appear before the name—e.g., USA-ARM/MT-G2-KIN-BR “Minotaur”.

Standard designation

Use this master format:

[Service]-[Family]/[Role]-[Generation]-[Loadout]-[Employment] “Creature”

Not every item needs every field. For ordinary infantry equipment, omit irrelevant platform or employment fields; for designed tanks, aircraft, and ships, use the full form.

Full examples

The code is deliberately left-to-right operational: organizational ownership first, physical type second, battlefield purpose third, and only then loadout and specialty. You can understand the design before reaching the creature name.

Service and family codes

Service prefix

For a standard historical-style United States run, use USA, USAAF, USN, and USMC almost exclusively. Reserve JNT for truly strategic or cross-service systems, particularly ballistic missiles, nuclear delivery projects, and experimental late-game equipment.

Equipment-family prefix

This avoids a common nomenclature problem: a term such as “Basilisk” no longer has to carry all the information by itself. USA-ARM/TD tells you that it is a tank destroyer before you ever read the flavor name.

Role codes

Ground systems

Air systems

Naval systems

Generation coding

Use a unified generation marker rather than equipment-specific model numbers. It works across every branch and maps cleanly to HOI4’s progression without pretending that a 1940 destroyer, improved medium tank, and advanced fighter share the same literal procurement history.

Example progression

A generation change signifies a fundamentally new production model, usually because you changed the chassis, airframe, hull, or the central research tier. A minor refit should not become a new generation.

Loadout codes

The loadout field identifies the primary physical armament or defining systems fit. It should tell you what the design is built to kill or support.

Ground loadouts

Aircraft loadouts

Naval loadouts

Employment codes

The final short code describes how the equipment is meant to be used operationally. It prevents two designs with similar roles and weapons from becoming indistinguishable.

Recommended final names

These are the clearest standardized designations for a U.S. WWII-style campaign using the creature system.

Variant rules

Use a final slash suffix only for a materially distinct production design built on the same underlying platform.

Base designation /[Variant]

Do not create a suffix for a trivial module swap. Use it when the altered design would be assigned to a different wing, task force, battalion type, or operational mission.

The key principle is simple: the code tells you the military reality; the creature name tells you the program’s identity. USN-SEA/DDE-G2-ASW-ESC “Merrow” is much more useful in a crowded production screen than “Merrow II,” but it still preserves the thematic character you wanted.

A dot-delimited system is much more readable than one continuous PascalCase string. I would use a short three-to-five block code, followed by one space and the full D&D creature name:

Branch.Role.Generation.Fit.Employment CreatureName

For example:

Ar.Md.2.Gn.Br Minotaur

Army · Medium tank · Generation 2 · Main gun · Breakthrough · Minotaur

The dots divide the functional elements into visual “words,” while the single space cleanly separates the technical designation from the flavor name.

Final standard

Core form

Br.Rl.Gn.Ft.Em CreatureName

The first three elements are the minimum name:

Ar.Md.2 Minotaur

The complete five-element version is used for customized chassis, airframe, and hull designs:

Ar.Md.2.Gn.Br Minotaur

This avoids adding codes that do not meaningfully distinguish a simple rifle or a generic support-equipment line, but preserves all relevant information for designed equipment.

Formatting rules

• Use dots only between technical fields.
• Use exactly one space before the creature flavor name.
• Use two letters or fewer for every alphabetic code.
• Use a single digit for generation; it is clearer and shorter than G2.
• Use PascalCase for compound creature names: DragonTurtle, AncientRoc, DisplacerBeast, StormGiant.
• Do not use punctuation after the creature name.
• Omit Fit and Employment only when they add no useful distinction.

Branch codes

The useful distinction for HOI4 air power is therefore straightforward:

Role codes

Army and Marine equipment

Land-based aircraft

Carrier aircraft

Naval vessels

The same role code can safely mean something different across branches when the branch itself removes ambiguity. For example, Cs means close-support aircraft under Af, but cruiser submarine under Nv.

Fit codes

The fit code says what the equipment is physically built around. It should describe the primary weapon, payload, or defining systems package—not every installed module.

Employment codes

The employment code identifies the mission for which the design is optimized.

Recommended production names

These are the compact forms I would actually use in your U.S. HOI4 production screen.

The cleanest flagship examples are:

Ar.Md.2.Gn.Br Minotaur

Af.Fi.2.Cn.Lr Griffon

Na.Cf.2.Cn.As Hippogriff

Nv.De.2.As.Es Merrow

Nv.Cv.2.Ai.Fl Phoenix

Mc.Am.1.Ap.Sh DragonTurtle

They remain short enough for HOI4’s production lines, but every dot-separated block provides useful information before you reach the creature name.

Revised designations in nomenclature

Use a two-layer, U.S.-style system: a formal designation that communicates equipment family and generation, followed by a memorable D&D creature codename that denotes its doctrinal role. This produces names that feel like American wartime materiel—e.g., Medium Tank, M4 “Minotaur” or P-51 “Pegasus”—while staying scalable through late-game chassis, airframe, and ship designs.

HOI4’s present designers make this particularly suitable: tank chassis, aircraft airframes, and ship hulls are foundations on which you create many module-defined variants, rather than a fixed one-name-per-research-item catalogue. The convention below therefore names every relevant production-equipment family and technology generation, then gives deterministic rules for every custom variant you create.[1][2][3]

Core format

Ground equipment

Use:

[Official type], M[family]-[generation] “[Creature]”

Examples:

• Rifle, Cal. .30, M1 “Kobold”
• Medium Tank, M4 “Minotaur”
• Tank Destroyer, M10 “Basilisk”
• Self-Propelled Gun, M7 “Chimera”
• Armored Car, M8 “Griffon”

Use the base M number for the underlying equipment/chassis family; append a dash plus generation when you replace it with a materially new design. A revised module layout that retains the same operational job can be a letter suffix—e.g., M4A1 “Minotaur”, M4A2 “Minotaur II”.

Aircraft

Use real-world U.S. mission prefixes plus a manufacturer-neutral type number:

[Mission prefix]-[number][variant] “[Creature]”

Examples:

• P-40 “Wyvern” — fighter
• A-24 “Manticore” — close-support / attack aircraft
• B-17 “Roc” — strategic bomber
• C-47 “Hippogriff” — transport
• PB-1 “Leviathan” — land-based naval patrol-bomber
• F4F “Harpy” — carrier fighter

This is deliberately more immersive than calling all small-airframe designs “fighters,” since HOI4 roles derive from armament/modules on the same airframe family.[1][4]

Ships

Use:

[Hull/type] class “[Creature]”

Individual vessel: USS [Creature]-class name or related creature

Examples:

• Destroyer class “Sea Serpent”
• Light Cruiser class “Kraken”
• Fleet Carrier class “Phoenix”
• Submarine class “Chuul”

Do not recycle an existing class codename for a new hull generation. A 1936 destroyer and a 1940 destroyer should be different classes even if their modules look similar. This matters because HOI4 ship designs are built from hulls and module slots, and their role can change significantly with armament, sensors, aircraft capacity, armor, and torpedo fit.[2][3]

Creature taxonomy

Assign creature groups by function, not merely by how intimidating they sound. That lets you recognize an item’s role instantly in the production screen or logistics ledger.

Army materiel catalogue

The entries below are a coherent full U.S. catalogue for the normal HOI4 production families. “Generation” corresponds to research progression; when a chassis designer permits a custom design, use the listed name for the first standardized production version and reserve variants for specialized module fits.

Infantry and support

Artillery and anti-armor

Avoid duplicate identities: “Cockatrice” should remain your anti-air family, while “Basilisk” stays anti-tank/tank-destroyer. The mythology overlaps, but the in-game production screen becomes much easier to read if every creature family has one stable operational meaning.

Tank chassis and variants

Use a chassis name for the principal tank and retain that creature root across derivatives. A tank destroyer based on the Minotaur chassis therefore becomes a related “Minotaur” program rather than a wholly unrelated vehicle.

For your historically flavored USA campaign, I would make M4 “Minotaur” the standardized general-purpose medium, with M4A1 through M4A4 representing improved engine, armor, reliability, or gun configurations—not entirely new mythological names. The tank designer supports exactly this kind of chassis-plus-variant approach.[5][6]

Air-force catalogue

The airframe designer means you should name the aircraft design, not every module. Keep each creature root tied to one role even when you change engines, fuel tanks, armor plates, or armament.

Airframe suffixes

Use suffixes only when the design has a distinct operational fit:

• -A — standard day combat version
• -B — long-range / drop-tank version
• -C — carrier-optimized version
• -D — dive-bombing or direct-support version
• -N — night-fighter or night-bomber version
• -R — reconnaissance version
• -T — torpedo-bomber or anti-shipping version

For example:

• P-51B “Griffon” — long-range fighter with extra fuel tanks
• P-61N “Nightgaunt” — radar-equipped night interceptor
• A-24D “Peryton” — dive-bomber-optimized attack design
• PB-2T “Leviathan” — torpedo-focused maritime striker

Navy catalogue

Ship names should operate at the class level, not the individual-hull level. You can then name individual ships after related creatures, famous locations, or historical American themes without muddling what class they belong to.

Ship-fit labels

Add a short capability label after the class only when it helps distinguish two otherwise similar designs:

• Merrow class (ASW) — sonar, depth charges, radar, escort focus
• Hydra class (Fleet) — gun/torpedo destroyer for main battle-force screening
• Kraken class (AA) — light cruiser with dual-purpose batteries and dense anti-air suite
• Phoenix class (Strike) — carrier designed around naval-strike wings
• Phoenix class (Air Superiority) — carrier emphasizing fighters and fleet air defense
• Chuul class (Raider) — long-range submarine with heavy torpedo armament
• Tarrasque class (Fast Battleship) — battle-line unit optimized for carrier task-force speed

This preserves one clean class identity while reflecting that HOI4 naval hulls can be configured into substantially different combat designs through batteries, torpedoes, AA, radar, sonar, engines, armor, and aircraft facilities.[2][3][7]

Practical rules

1. Do not use names randomly. A name should predict the equipment’s job. If you see “Basilisk,” it should always be anti-armor; “Phoenix,” always aviation-capital-ship or strategic-air power; and “Chuul,” always submarine warfare.

2. Keep the service branch visible. Use M for Army ground equipment, U.S. air prefixes for aircraft, and “class” for ships. The creature codename adds flavor; the designation tells you what you are actually producing.

3. Reserve the grandest names. Save Tarrasque, Empyrean, World Serpent, and Astral Dreadnought for super-heavy armor, late battleships, advanced bombers, nuclear vessels, or end-game missiles. Giving an early artillery gun the name “Tarrasque” dilutes the hierarchy.

4. Treat old designs as legacy materiel. When a 1936 design becomes obsolete, keep its original name rather than renaming it. In the logistics screen, “M3 ‘Chimera’” visibly communicates that it is a previous-generation medium tank.

5. Use actual model numbers selectively. For an immersive U.S. WWII game, assign historically plausible numbers only to designs you intend to standardize and mass-produce. It is perfectly acceptable to call a niche prototype T23 “Gorgon” and only award it an M designation after you commit it to production.

6. Name designed equipment, not every abstract modifier. Naming is meaningful for equipment that exists as a production line or chassis/airframe/ship design. Doctrine upgrades, generic special-forces stat improvements, MIO traits, and installed modules should influence the design, but normally do not need their own creature codename. This keeps the system usable rather than becoming administrative clutter. The U.S. has MIO coverage for material, armor, aircraft, and naval production families, so standardizing a small number of named core designs also pairs well with focused MIO development.[6][8]

The clearest “canonical” U.S. WWII core under this scheme would be: M2 “Hobgoblin” infantry kit, Mule truck, M4 “Minotaur” medium tank, M10 “Basilisk” tank destroyer, P-51 “Griffon” fighter, A-24 “Peryton” CAS, B-29 “Ancient Roc” strategic bomber, Hydra-class destroyer, Kraken-class light cruiser, Phoenix-class fleet carrier, and Chuul-class fleet submarine.

Sources
[1] Aircraft designer - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Aircraft_designer
[3] Naval technology - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Naval_technology
[5] Ship - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Ship
[7] Air technology - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Air_technology
[9] Variant - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/index.php?title=Variant&mobileaction=toggle_view_desktop
[10] usa-wwii-preparation-guide.pplx.md usa-wwii-preparation-guide.pplx.md
[11] Naval support technology - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Naval_support_technology
[12] Military industrial organization - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Military_industrial_organization
[13] Editing Equipment - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/index.php?title=Equipment&veaction=edit&section=3&mobileaction=toggle_view_desktop
[14] Aircraft - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Aircraft
[15] Triggers - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Triggers
[16] Naval technology (Basic) - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Naval_technology_(Basic)
[17] Division modding - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Division_modding
[18] Equipment modding - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/Equipment_modding
[19] Naval support technology - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/index.php?title=Naval_support_technology&mobileaction=toggle_view_desktop
[20] Equipment modding - Hearts of Iron 4 Wiki https://hoi4.paradoxwikis.com/index.php?title=Equipment_modding&veaction=edit&section=17