Equipment List Standards

From Supreme Ruler Wiki
Jump to: navigation, search

Contents

Equipment File Information[edit | edit source]

  • File is S:\Documentation\ColdWar\DATA\CWUNITS.mdb
  • variable order is customizable in the lists
  • Exports to \Maps\Data\DEFAULT.UNIT for the version selected

What's in?

There is a dedicated page for the [/docs.google.com/document/edit%3Fid%3D1IPxIuO1HKZN4y80q90I8wa%20ozsvyG6LfGsTfPUqfDcU%26hl%3Den Criteria for Included Unit Types].

Variable Details[edit | edit source]

Each variable has unique standards that must be followed. The variables listed below match in most part the title of a column in the unit database. Clean up in progress.

Unit Picture Variables[edit | edit source]

  • Picnum
  • Picnumbase (Legacy SR2010)
  • Picnumturret (Legacy SR2010)

The Picnum is a unique value assigned to a 3D Mesh. Defining a 3D Mesh must be done in the database using the "Mesh" button for a record using the given Picnum. TheDEFAULT.PICNUMS file is generated when the equipment file is exported and defines the mesh properties for the engine.

ID[edit | edit source]

This is the Database key. Never touch.

SRxActive[edit | edit source]

  • There is a column for x=5, 6, 7 and 8.
    • 8 should be changed to 9 in anticipation of a CW expansion?
  • Indicates unit is active for SRx
  • Only mark active if unit entry has all required data filled in

PendingWork[edit | edit source]

used to track status of units and some key clasifications

  • UX - X indicates version of game released in
    • CW and Apollo used for now since no released versions
  • use to mark duplicate entries
  • use to indicate rejected
  • use to indicate mod version
  • use to leave notes for others

ClassNum[edit | edit source]

Numeric value assigned as follows;

Class # Included ‘subtypes’ Notes
0 – Infantry
  • No penalty for move and shoot
  • Should be generally good at close combat
1 – Recon Radar Trucks, Cavalry
  • Advantage?
  • Radar: These units should be Strength 1
  • All "armored cars"
  • Green Archer types
2 – Tank ETC Tank, EM Tank, EM Rail Gun Tank, Laser Tank
  • No penalty for move and shoot
  • Usually Demolition capable (always?)
  • ETC Tank; Lvl 114, tech 158,
  • EM Tank; lvl 116, tech 157, 127mm
  • EM Rail Gun Tank; lvl 120, tech 160, 133mm, 6km range
  • Laser Tank; lvl 120, tech 252, 4mm, 10km range
3 – Anti-Tank Gun, ATGM,

Mech (all types)

  • Subject to Move & Shoot Penalty
  • Generally worse (lower) Initiative than Tanks; Used w/Turretless & limited firing arc Vehicles, also those without stabilized guns
  • Also for Anti-Tank armed Infantry
4 – Artillery Ballistic, MLRS, Mortar,

Launch Vehicle,

ETC

  • Standardized range per gun size
  • Ballistic: Ballistic = Y, Missile Cap = 0
  • MLRS: Ballistic=N, higher ammo usage
  • Mortar: Ballistic = Y; Missile cap = 0
    • Shorter Ranges; weak Hard Attack, but good Soft attack? Also, make lower ammo use, and longer combat time; Also, higher initiative (faster reload times)
  • Launch Vehicle: Missile cap > 0, attack values = 0, ammo = 0
  • ETC Artillery: dbl barrel 160mm gun on SP, single barrel towed
5 – Air Defense Gun, Missile, Combo
  • High rates of fire;
  • Radar FCS tech improves defensive rating
  • Missile: evaluate Reaction Time ratings
6 – Transport Bridging, supply
7 – Helicopter Attack, armed UAVs Not transport helos
8 – Missiles
9 – Interceptor best at air to air, armed UAVs also
10 – Tactical Bomber best at Air to ground, armed UAVs also
11 – Multi-Role
  • Multi-Role if Any Ground Attack >= 20 and Any Air Attack >= 30
  • armed UAVs
12 – Strategic Bomber
  • Units in this class are those that are indirect attacking vs. ground
  • what about light bombers? (Some notes on Discussion Page)
13 – Patrol/Fixed Wing Patrol, AWACS, Recon/Surveillance, ECM, ASW
14 – Transport Fixed Wing/Heli Cargo, Tankers WIG currently not used
15 – Submarines SS, SSN, SSBN, SSGN
16 – Carriers Aircraft/Heli Carriers, LHD/LHA class SR8 - includes Seaplane tenders with capacity > 10 aircraft
17 – Capital Ships BB, CG
  • Battleships, BattleCruisers, Monitors, Dreadnaughts
  • Heavy Cruisers, all types
  • (Pre-SR1936, included Light Cruisers, Destroyer Leaders, Torpedo Destroyers)
  • Generally ships > 10,000 tonnes
18 – Escort Ships Destroyers,

Frigate,

Missile Frigate, Heavy Corvettes

  • Sloops, Frigates, Heavy (long range) Corvettes
  • Destroyers, Destroyer Escorts, Light Cruisers
  • (Pre-SR1936, was Frigates)
  • Generally 1000-10000 tonnes; Crew complement usually over 150
  • Over 5000 km travel range
19 – Patrol Ships Light Corvettes,

Patrol Ships,

Support Ships?,

Spy Ships?

  • minesweepers not currently included
  • Motor Torpedo Boats
  • ASW Patrol
  • (Pre-SR1936, was "Patrol/Support")
  • Generally Under 1000 tonnes; Crew complement usually under 100
  • Under 5000 km travel range
20 – Transport Troop Transport, Cargo Ships,

Supply Ships, Landing Ships

  • Command Ships
  • Seaplane tenders?
21 – Upgrades

Excluded types

  • Dispatch Ships
  • River Monitors/River Patrol/River Gunship/etc.
  • Floating Barges
  • Yachts
  • Fishery Protection Vehicles
  • WiG aircraft

ClassText[edit | edit source]

  • Originally used as a combination of the class number with text for clarification. Officially replaced by ClassNum. Not used by the engine
  • Now being used to leave notes on how a unit works within its class such as "MLRS" for a class 4 unit or "Biplane" for a class 9 unit.

SR5ID[edit | edit source]

  • RENAME to UNITID in DB
  • This is the unique ID number assigned to the unit used by SR5, SR6 and SR7 (all versions at this time)
  • DO NOT CHANGE if unit has been marked active for any project
  • Do not assign until ClassNum has been assigned
  • Numbered from 1 to 1000 for each Class
  • Unit ID must be within Class # * 1000+1 to Class # * 1000+999
  • Duplication not allowed

Implementation Note: UI should sort by spec, ie year etc, so ID # should be irrelevant; never any need to ‘renumber’ or be concerned about sequence in list, just don’t duplicate #s! SR4 required upgrades to have higher ID than original; this is not required for SR5

SR5IDText[edit | edit source]

This is a text field that contains the SR5ID number at the time of conversion from the spreadsheet, kept to be able to find any "KJ" numbered units.

Model Code[edit | edit source]

Equipment alpha-numerics ie M1A1, BGM-109

  • There should be no spaces in this cell at all, begin typing in Equipment Name as of first space.
  • the quotation mark character " is not allowed in this field.
  • Russian Ground Types prefix “T-xx”
  • Japanese Ground Types prefix “J-xx”
  • Chinese Ground Types prefix Chinese Local Designations:
Z: Armoured T: Tank S: Amphibious
Z: Main Battle
S: APC L: Wheeled
D: Tracked
B: IFV (L / D)
D: Missile Launcher F: Anti-Tank
H: Services B: Supplies
P: Artillery L: Howitzer (Gun) Z: Self-Propelled
L: Towed
P: Mortar
G: AA (Z / L)
T: Anti-Tank Gun (Z / L)
  • For Aircraft, use local region designations (MiG-17, F-18A)
  • Leave blank if no part # type for equipment.
  • If not named flag as "Needs Name"
  • For Chinese missiles, use this link
  • Ships with "type" or "project" in the name, replace with the following prefix, use the project/type number as the suffix
Battleship BB BBN could be used for Nuclear
Cruiser CC/CG/CGN Don't think we've had an occurrence of CC at this time
Destroyer DD/DDG/DDH G is Guided Missile, H is Helo
Frigate FF/FFG/DE/FFL DE is Destroyer Escort, FFL is for Corvette/Light Frigate
Patrol PC/PG/PGM
Transport Class specific many forms including AP/LCM/LPD/LST/LCU/etc.
  • Example a Slava Project 1164 Cruiser would be a CG-1164 Slava
  • Russian Ships; Do not use the BPK term

Equip Name[edit | edit source]

Equipment English Name, ie “Abrams”, “Tomahawk”

  • the quotation mark character " is not allowed in this field.
  • Also, NATO names (ie ‘Frogger’) go here
  • the intention is to use Class names, not Unit names such as Arleigh Burke Class.
  • Do not use the term "improved"
    • Where we include multiple units within a given class to represent improved versions use the pennant and name of the version where the improvement is introduced. For example the SSN-764 Boise is an Improved Los Angeles class Sub
    • Ideally we would use only the class name for the unit and use the orbats to distribute pennant names and numbers to each ship.
      • This should also be done anywhere a ship is reclassified. Use the original class entry and use the Orbat to assign it's new name/number
  • Include post-name part numbers here, ie: “Leopard 2A3”
  • Include post-name ‘Mark’ indicators here, ie “Chieftain Mk 5”
    • Abbreviate Mark as "Mk" or optionally use dash (ie "Tomahawk-5")
  • Do not include modifier "Block", use dash or space instead (ie "Harpoon 1C")
  • Do not include redundant elements such as "Type", "Project", etc
    • Use J-90 instead of Japanese Type-90 etc
    • Use "CV-1143.4 Kiev" instead of Russian Carrier "Kiev Project 1143.4 CV"
  • Avoid redundancy (don’t use words “Tank”, “Missile” etc)
    • Keep terms of "Phaser, Ion, Gun, just lose the additional word.
  • remove AA or SPAAG from anti air names, AT or ATGM from AT units
  • watch for use of dashes to link parts of names that are not normally linked.
  • Where units use "w/" for with removed these characters, leave the name of the other associated equipment
  • Upper & Lower Case except for acronyms
  • Descriptors such as “Light”, “Heavy” should be capitalized first letter
  • Special Cases:
    • Infantry: Generic types such as ‘Engineer’, ‘Light Infantry’
    • Artillery: If Equipment has a Common name, ie ‘Rhino’, use it;
      • Name should include Mobility, Gun size, Type;
        • Mobility = “Towed” or blank for self-propelled
        • Gun Size in mm with no space
        • Type = “Howitzer” (exclude if has name), “MLRS”
      • Ie "Towed 155mm Howitzer", "214mm MLRS", "Rhino 155mm"
      • Inches should be "6in", no use of double-quote
    • Don’t include ‘SP’ (Self Propelled) or SPG, SPH
      • This standard is not consistently applied and is under challenge
    • Anti-Air: Follow similar rules to Artillery; use Common name if avail;
      • Otherwise Mobility, Gun size, Type;
      • Ie "Towed 85mm Gun"
    • NBC Missiles no longer need to include "NUCLEAR" or "CHEM" in name
      • Based on the fact that all GUI displays of missile name must include Nuclear icon shown
  • name ideas for India; [/www.hindilearner.com/hindi%20words.html link]
  • For ships added as "non-buildable" to generate opening inventories, naming conventions can be less accurate but should follow these standards as much as possible.
  • Unit Naming Issues and Decisions:  See [/docs.google.com/document/edit%3Fid%3D1JvR54oA37a1d1yX7om6pM9Y-7oKv2lNgZux4pgiWPCU Equipment List Standards - Unit Name Issues].

Implementation Note

  • UI will try to show full Model/Name entirely.
    • name is combined with model code on export
  • Maximum # of characters in Model & Name combined is 27 (enforced?); recommend under 20.
  • Effective Update 7 & CW, the GUI will display the full Equipment name (ie "27th TANK Leopard 2A4"), so no dashes or other elements are required to workaround clipping of important name elements. This also means that unnecessary name elements should be shortened or eliminated.

Naming Notes

  • Where NATO Model Codes and Names exist, use NATO Names only - any local names go into 'Alternate Name' field.
  • Where different names used in different countries, use the original (first developed) name, or if not known, use the most common name; other name(s) go into 'Alternate Name' field.

Errors[edit | edit source]

Errors for units are generated and listed here when using QA Run

NeedName[edit | edit source]

If this field is selected it indicates that the name of the unit does not match the standards for either the Equipment Name or Model Code data bits. This will also appear as an error in teh QA Run.

Region Codes[edit | edit source]

This is sometimes refered to as "Researched by" or "Region of Origin".Region codes determine where a unit comes from.  The letters assigned should represent countries where the design could be achieved any time after game's start date without any other region having discovered it first.  A heavy preference should be given to regions how originally invented a design, regions building a design under licence should only get their code added to this field if their discovery of the design was "inevitable".  Some consideration is given to outdated designs to provide options to lower tech regions.

These are the available categories:

  • * Universal, available World-Wide
  • A South Africa
  • B Brazil/Argentina
  • C China
  • D Belgium, Netherlands, Luxembourg (BeNeLux)
  • E Europe, Ireland, Spain, Portugal, Turkey, Greece
  • F French
  • G German
  • H Italy
  • I Israel
  • J Japan
  • K South Korean
  • L North Korean
  • M British
  • N Canada/Australia
  • O Other
  • P Unused
  • Q India
  • R Russia, Ukraine, Former Soviet, Belarus
  • S Sweden, Swiss, Denmark, Norway
  • T Czech, Austria, Yugoslavia, Finnish, Poland, Romanian
  • U Units are generally made by and for the USA
  • V Taiwan, Philippines
  • W Same as *
  • X Unused
  • Y General Pacific (some of the common R/C stuff), Singapore
  • Z Arab (Iran/Iraq/etc) including Pakistan

Region Code SR1936

  • Region codes should usually be for one region only if < 1960.  World Avail. mostly for fictional units
    • If A requires B and B has more region codes, those regions can't research B without being traded A.

TechReq(x)[edit | edit source]

There are two TechReq fields. Each one can be used to list a prerequisite technology required for research of a unit design. For information on how to assign technologies review the latest Tech Tree

  • When using form view the DB links to the CWTechTree DB
  • Until the techtree database is completed list intended tech tree prereqs in the notes.

Builder[edit | edit source]

Text field used for making notes on countries of the world that build a certain unit type.

U/G to[edit | edit source]

Unit ID# considered an ‘Upgrade’ of this equipment type.

  • ie M1A1 to M1A2
  • This is meant for Upgrades that can be physically done, or make sense for Gameplay purposes; ie, Leopard 1A4 to 1A5 is OK, Leopard 1 to 2 is not.
  • future engine may allow players to upgrade existing units along this path.
  • ID of unit to upgrade to may be lower than ID of the older unit
  • Units may be upgraded into a new class (interceptor to multi-role)
  • Make sure upgrades are equal or greater in tech year.
  • Entries in class “Upgrades” are not replaced by a unit listed as “upgrade to” being researched. Players have the option of building Micro and Mid goods plants even if they do have the research for Large.

Replace By[edit | edit source]

Unit ID# considered a ‘Replacement’ of this equipment type

  • ie Leopard 1 to Leopard 2 To Challenger to Abrams
  • This is used to filter Build lists for players, to prevent display of obsolete types and provide suggestions on what new types to research. It is also used across similar units from different region codes to keep the list more manageable as players acquire foreign designs.
  • Units may be replaced by a new class (interceptor by multi-role)
  • ID of unit to replace with may be lower than ID of the older unit
  • Players will not be able to upgrade existing units along this path
  • Make sure replacements are equal or greater in tech year.
  • Entries in “Upgrades” class should use “Replaced by” values if we make generational versions of upgrades. So a 1930 industrial plant node added for modding/missions would get a “replaced by” value pointing to the current industrial node entry

Abandon to: (Upgrades only)[edit | edit source]

Indicates upgrade ID# that is used for “Rubble” version of this facility.

  • implemented?

Refit To[edit | edit source]

Currently Unused. If implemented as currently entered, the ID number indicates the other unit record to which a given you can be "refit".

Year Avail[edit | edit source]

First Year of quantity ‘production line’ production. IOC date.

  • Should be introduction date, not first flight.  Having proper tech prereqs is however the critical factor.
  • Where unit is not yet/never was commercially produced, this will generally be a few years after prototype stage.
  • Tech level required to research = Year Avail – 1900
  • Year Avail must be > tech year of all prerequisite techs
  • For boats, using either data laid down or date commissioned.

Crew[edit | edit source]

Soldiers per squad or equipment piece.

NumSquadInBatt[edit | edit source]

This is the default number of Squads or Equipment pieces in a Battalion, as determined by the standards of the producing region, for Scenario Design purposes.

  • Ships are always Quantity 1
  • ‘Single Purpose’ Units with no combat or supply purpose are Quantity 1
    • Command Unit – should be Quantity 1
    • Bridging Unit (non-Combat) – should be Quantity 1
  • In-Game, new construction defaults to ‘Standard Quantities’ set by WMData file
    • Can no longer adjust using a 50%-150% Strength Slider or over/under str.
    • This value is only used to determine the strength of units assigned via orbats

Classe Defaults[edit | edit source]

Class # Standard Qty Notes
0 – Infantry 54 (Special Forces usually 35? Mechs s/b 24?)
1 – Recon 38
2 – Tank 44 (Allows str range 22-66)
3 – Anti-Tank 45
4 – Artillery 18
5 – Air Defense 40 Long range AA usually ½ this
6 – Transport 24
7 – Helicopter 24
9 – Interceptor 18
10 – Attack Fighter 18
11 – MultiRole Fighter 18
12 – Strategic Bomber 12 what about light bombers?
13 – Patrol/Fixed Wing 6 / 12 SR2020, SRCW: 6  / SR1936 (pre '49 units): 12
14 – Transport 12 non-Mission Air units will get this Doubled

Cost[edit | edit source]

Cost per SQUAD / EQUIP PIECE

  • Does NOT include Mil Goods cost (which is from weight of unit)
  • Should be the real-world ‘Per Additional Unit’ cost
    • CW change - Cost is based on Year of introduction (IOC).  A 1960s unit should have it's 1960s price
    • CW - price is adjusted based on inflation and the world economy
      • a 1960s unit will cost less in 1949 and more in 1980 than it's cost listed in the database
    • Ie Development cost should not be included, only ‘per unit cost’
      • (“Development cost” is part of tech prereq research costs, etc)

DaystoBuild[edit | edit source]

Days to build/train 1 squad/piece

  • Costlier Units should experience higher build times
  • Heavier Units should experience higher build times
  • An approximate guideline for Ground units is also ‘Cost in Millions / 2’
  • Presence of tech pre-requisites does not affect build time or cost (it is part of ‘development time’, which is not included here)

Speed[edit | edit source]

‘Standard’ (cruise) traveling speed of Unit

  • In km/h, if not researched as such use Online Conversions website
    • mph*1.6
    • knots*1.852
    • 1 mach = 1 225.044 kilometer/hour
      • Should be ‘standard’ (cruise) speed, not burst/peak speed.
    • In cases where only maximum speed is listed, it is preferable to assume 80% of maximum as cruise speed.
      • This has not been applied to many aircraft from SR2020 even through some early Apollo entries.
      • The entry for the F-4 Phantom in Persicope offers a good view that this is a poor system.  We should be using max speed and using the engine to trim that.  Else we never know if we entered the right value
  • For ground, should be cruise/travel speed in clear/road terrain.
  • For towed units use common speed of 25km/h
    • KJ methodology - fuel value per gun weight/year range
      • older/light guns
        • 25-30km/h, range 200km, fuel 1.0
      • Medium caliber ~75-120mm
        • 25-30km/h, range 200km, fuel 2.0
      • Heavy guns >140mm
        • 25-km/h, range 200km, fuel 3.0
      • guns after ~1940
        • 35km/h, range 225-250km, fuel value 1.5-3.5

MoveType[edit | edit source]

Integer value assigned as follows;

  • 0 Leg
  • 1 Wheel
  • 2 Half-Track
  • 3 Tracked
  • 4 Towed (generally same as ‘Wheel’)
  • 5 Variable (Track/Wheel)
  • 6 Mech
  • 7 Hover (Also Special Case: Amphibious Water on Land)
  • 8 Unused
  • 9 Unused
  • 10 Naval
  • 11 Unused
  • 12 Air – Close (Helicopters)
  • 13 Air – Mission (Fixed Wing)
  • 14 Internal Use (Special Case: Amphibious Land Unit on Water)
  • 15 Internal Use (Special Case: Supply Route)

Notes:

  • Hover Type always allowed on Water; only allowed on land if ‘Amphibious’ Flag set
  • Amphibious Land units get set with their main type (ie Wheel); when on water, movement type is over-ridden to special case.

MoveTypeText[edit | edit source]

This is the old Move Type field which used to contain the number for the move type and some text to further specify subtype. In newer entries it is being used only to indicate move subtypes.

  • For air units we should begin listed ceiling altitude here for help assigning other values if standards change.
    • big job to push back to existing.
  • Also used at times for indicating # of wheels
  • could be used to specify prop/jet and move service ceiling values to TargetTypeText?

MoveRange[edit | edit source]

Used to calculate fuel range for units. Important to be accurate!

  • Ground: Typical Move range in Clear Terrain - usually range on 1 tank of fuel.
  • Towed units always 350km
  • Air: Indicates Standard travel distance with typical load
    • Ideally look for values listed as "normal range"
    • Usually double the ‘combat radius’; use ‘2x max combat radius’ as alternate
    • Do not use ‘ferry range’ since that assumes no weapons load.
      • 1x combat radius was used in SR4 at times REVIEW!
      • ferry range/2 was used in some cases. Case by case
  • Tanker Air: Fuel Range must include the total distance tanker would travel with a full load of fuel in refueling tanks available!
  • Naval: Distance traveled on one tank of gas. If nuclear, =spd*17520 hours
  • Facilities: 0

FuelCap[edit | edit source]

Volume in Barrels of petroleum carried by each squad/aircraft/ship/sub.

  • Gas/Diesel/Fuel Oil:
    • use Online Conversion website to barrel US liquid
    • gallons p/pound fuel – 0.138 (or 7.24 lbs p/gallon;
    • or 304 pounds / barrel
    • Pounds per gallon: 6.04 Pounds / barrel: 304
    • Barrels per Metric ton – 7.25
    • U.S. gallon = 3.78 liters (or 0.264 U.S. barrel)
    • U.S. barrel = 42-gallons (or 158.98 liters)
  • Residual fuel oil, ie naval fuel oil has differing weights that standard Gas/Diesel/Fuel oil above – being:
    • Pounds per gallon: 7.88
    • Pounds / barrel: 331
    • Barrels / metric ton: 6.66
  • Motor gasoline also has differing weights:
    • Pounds per gallon: 5.83
    • Pounds / barrel: 259
  • Tanker Aircraft: Include Standard capacity PLUS Refuel Capacity
  • 1 barrel = 0.155 tons (tonnes/.155= barrels)
  • Ships: Special Rules Apply:
    • Fuel Consumption is 0.360 lbs per hp per hour
    • To calculate Fuel use rate per hour: [Fuel Cap/ (Km Range/Km Speed)]
    • When setting fuel capacity for Diesel or Gas ships the consumption rate can be used to reverse guess the total fuel capacity.
      • Expected ship fuel capacity is:(Engine HP*Max Move per day/Move Spd*0.36/2000/0.155).
    • Consumption rate per class will generally be in the following ranges:
      • Benchmark: Arleigh Burke, 100,000hp @ 61km/h is ~120 b/h (Barrels per Hour)
      • Diesel Sub: 1.8 to 6 b/h
      • Non-nuclear Carriers: around 250b/h
      • LHD Carriers: around 100b/h
      • Naval-Electric Carriers: around 180b/h
      • Non-nuclear Cruisers/Battleships: 150-220b/h
      • Destroyers: 60-130b/h
      • Frigates: 30-90b/h
      • Corvettes: 10-60b/h
      • We could program a common factor, consistent with the period of 4 Prop aircraft of the period.
        • That CONSUMPTION figure is: 0.50 LBs/HP/Hour of Flight Time, for each Engine.  Therefore, if the unknown is a single engine 9 Fighter type, use the above figure.  If the type is a 2-Engine, double the Consumption rate....3-Engine, triple, etc. etc.
  • Forum thread

Spotting Types[edit | edit source]

Units can be assigned two different spot types. Lookup ID for Spotting Type from list

  • Optional Secondary Spotting Type, usually used for ASW
  • Lookup Provides Spotting Range & Spotting Strength.
    • Details on how to determine range and strength of a radar type are in the Spotting Type page.
  • Spotting Type ‘0’ (no spotting) will not even spot ‘own hex’
  • If SpottingType1 is not set, then SpottingType2 is ignored
  • Entries in “Upgrades” class can also be given a Spotting type.
    • Required if the node/container is to have the ability to spot (radar/Airstrip)
  • any ship with a spot type in the 500s (sonars) should have tech #110 if it does not already have two more important prereqs
  • It has been proposed to add the ability to give an advanced order to air units for "low detection range" during movement. The effect would cause them to move down to "close" range for flight and targeting but decrease their profile making them harder to spot. This is based on notes in the Target Level Rules Ballistic Anti air units should have inherently a lower profile than SAM Anti air units due to the electronic "noise" generated by SAM stations.

Stealth Strength[edit | edit source]

Rating of how visible unit is. Used in conjunction with spotting strength and range.

  • Lower values will make units more visible.
  • Stealth = 255 will make the unit invisible.
    • modifiers such as efficiency can result in that not being the case
  • Stealth = 10 will make the unit visible to any level of spotting.
  • Stealth = 0 will make the unit visible even under fog of war.
  • Details on spotting system are in /Design Docs/SR5_LOSRules.doc

Weight[edit | edit source]

Weight of Military Goods in metric tonnes of each Squad or Equipment piece.

  • Weight regarding vehicles, ships and aircraft is without Fuel, Ammunition, or Cargo (to include passengers).
  • Weight in game is used as follows
    • Air Units: Empty Weight, shown in metric tonnes (MT).  Where Empty Weight is not known, a general estimate of ~70% of Take-Off Weight (T/O) can be used, which is a rough average of the aircraft empty weight without fuel, ammunition, pilot/crew, etc. (not "max take-off" weight)
    • Naval Units: ships shall be Standard displacement value.
    • Land Units - generally, either Empty Weight or British term "Unstowed Weight" shall suffice for Vehicles.

Note: Military goods used to build are 1:1 for weight, except Naval classes where ½ weight is used.

Industrial Weight[edit | edit source]

Weight of Industrial Goods in metric tonnes; generally for Facilities.

Uranium Weight (Ur Weight Kg)[edit | edit source]

Weight of Uranium in kilograms for each unit; generally for Nuclear Missiles.

  • Standard of Raw Uranium kg to Nuclear Yield:
    • Uranium kg = Sqrt( Yield ) * 10,000
    • This means smaller yield will require a more reasonable amount,
    • but huge-yield will not be unusually large.

TransportCap[edit | edit source]

Weight that can be carried in cargo by the unit.

  • This includes max payload + sling load.
  • Units will fill with supplies up to this value x # of units in battalion.

Common values:

  • Utility Helicopters: 4-2
  • Cargo Helicopters: 5-20
  • Planes: 7.5-40 (some as large as 150-250)
  • Carriers: 1000-25000
  • Cargo ships: 1000-5000 (some as large as 30000)

Long Deck Carrier[edit | edit source]

(Y/N)Indicates whether ‘Long Deck’ squadrons can land on this ship. - ‘Short Deck Takeoff’ units can land on any carrier - ‘Long Deck Takeoff’ units require a carrier with this flag set Entries in “Upgrades” class use this value to indicated if aircraft can land on the node

Air Carrier Capacity[edit | edit source]

Indicates the number of air squadrons which can land on the ship.

  • Type of air units allowed to land depends upon ‘Long Deck Carrier’ setting
  • SR8 - used for Seaplane Tender ships.  They are treated as short deck carriers.
    • only ships with capacity > 10 are included
    • know issue that this will make them capable of landing helicopters and VTOL in late games

TargetType[edit | edit source]

Indicates Unit ‘Target Defense’ type. Determines what attack values unit will defend against and where they are located as relates to "levels" within the game.

  • 0 Soft (ground level target)
  • 1 Hard (ground level target)
  • 2 Fort (used for facilities)
  • 3 Close Air
  • 4 Mid Air
  • 5 High Air
  • 6 Surface (ground level target)
  • 7 Submerged (Submarine)

For rules on which level of air a unit should be assigned, see the Target Level Rules

TargetTypeText[edit | edit source]

Carry over field from SR2010, now being used to note key characteristics of units such service ceiling or to note special technologies used that should be considered when assigning values.  Not used by the game engine, for DB editing and notes only.

Initiative[edit | edit source]

Unit ‘Initiative’, generally 1 (low) to 8 (high)

  • "First Shot / First Move" base value
  • Higher val = more likely first shot & Faster Reloading
  • Units without Combat capability get Initiative (1)

See Baseline Charts at end of Document.

Indirect[edit | edit source]

(Y/N)Indicates if damage targets a unit in the hex or entire hex.

  • Y for Artillery, Bombers, Battleships, Ships using 155mm AGM guns.
    • Battleships and Battle Cruisers generally had main guns > 300mm capable of indirect
  • Should be for Surface-to-Ground and Surface-to-Surface ranges > 1 hex

Ground Attack Range[edit | edit source]

Range of fire for attack weapons versus ground targets

  • Range for most gun types can be researched (Periscope)
  • Missile Ranges also used for units that fire missiles not modeled as units.
  • Land Guns, AA, Surface to Surface Missiles: Periscope
  • Ballistic Artillery: Charted range according to gun size
  • Fighter: usually 24km (Mavericks)
  • Other basic units: 5-10 km

Air Attack Range[edit | edit source]

Range of fire for attack weapons versus air targets

  • AA: Research (Periscope)
  • AA-ADATS: 10/25/40km for techs 254/255/256
  • Jet: AMRAAM: 75-100km, BVRAAM: 145km, AA-12: 80km
  • Other basic units: 5-10 km
  • Land force pre Cold War should have far less AA capabilities
    • tanks with <13mm guns given no AA value

Surface Attack Range[edit | edit source]

Range of fire for attack weapons versus surface naval targets

  • Value often equal to ground attack, particularly for land units
  • Air: Gun, torpedo or missile range. 24km for missile is common (Maverick)
  • Subs: torpedo range
  • Ships: torpedo or main gun range

Submerged Attack Range[edit | edit source]

Range of fire for attack weapons versus submarine naval targets

  • (0) for land units
  • Air, and Sub: torpedo range
  • Ship: Torpedo or Depth Change range
  • Ship w/ ASW helo:
    • 60-km for Agusta AB-212, MD-500 ASW
    • 100-km for SH-60/SH-70/AS.532 Cougar/Lynx
    • 100-km for Ka-27?

Attack Values[edit | edit source]

To determine if a unit should have a given attack value, see the Target Level Rules

Soft Attack

Hard Attack

Fort Attack

Low Air Attack

Mid Air Attack

High Air Attack

Naval Surface Attack

Naval Submerged Attack

Value representing strength of attack versus specific types of targets.

  • Factor in all weapons systems of units and any unmounted squads (inf).
  • Damage should be evaluated by ammo of weapon type and amount of that ammo expended per “shot”. See also “Supply use per squad”

Certain factors should be variables in the weighting;

  • Maneuverability (including Speed/Climb Rate for Air Units)
  • Fire control
  • Onboard Weapons (not those modeled separately as missiles)
  • Ammo Weight per shot (and associated weapons used to determine weight)

Class Notes[edit | edit source]

  • Carriers are zero vs. all land types (As of SR8)
  • land are zero vs. all sub types
  • to determine if the AA capabilities of a unit are within low/med/high use the Target Level Rules
  • The AA values for towed artillery units before MANPADS capabilities should be zero. (As of SR8)
  • Tanks with nothing but Machine Guns should have hard attack = 1
  • Tanks with 37mm ~ 1930 hard attack = 6

Close Combat Attack[edit | edit source]

An override value for Soft Attack AND Hard Attack Value, used when:

  • Attack type is Direct (not Indirect/Artillery fire)
  • Defender Unit is in ‘Close Combat’ (Urban/Low Vis) Terrain
  • Applies to attacks from Ground and Air Units
    • Attacker can be in either open terrain or close terrain; only defender terrain decides.

Ground defense[edit | edit source]

Value used when any unit type attacked from direct-fire Ground/Naval/Sub Units Special Cases:

  • Landed Air Units – use ‘Close Defense’ value
  • Defending Ground Unit in Close Combat Terrain – use ‘Close Defense’ value

Tac Air defense[edit | edit source]

  • For Ground & Naval Units: Defense against close air (bombing/strafing)
  • For Air Units: Defense against attack from other air units
  • Aircraft with Afterburner or greater maneuverability should get a benefit

Indirect defense[edit | edit source]

Indirect Fire: Artillery, Strategic Bombing, and Indirect (Area Effect) Missiles.

  • For Ground & Naval Units: Defense against Indirect Fire
  • For Air Units: Defense when unit is landed and hit by Indirect Fire
  • Value is not used by Missiles and Submarine

Close Defense[edit | edit source]

  • For Ground Units: Defense when defender in ‘Close Combat’ (Urban/Low Vis) Terrain
    • Attacker can be in either open terrain or close terrain; only defender terrain decides.
  • For Air Units: value used when landed and attacked directly by ground forces
  • Value is not used by Missiles, Naval Surface, and Submarine
    • Subs might need this value if we make them surface to fire on land/naval targets

Combat Time[edit | edit source]

The number of “shots” the unit can take with a single load of ammo.

  • Rate of fire should be factored in. Units that fire faster should do more damage but have less combat time if they have the same supply cap.
  • Generally reported as Combat Time in ‘hours’, but this is not entirely accurate depending upon units firing rate; in-game, this is the number of shots per full load.

Supply cap per squad[edit | edit source]

Sum weight of all ammunition stored for each weapon system assuming max payload.

  • Supply cap is decreased by weight of missiles units loaded on.
    • Loading heavy missiles could “empty” stores of a unit
    • High supply capacity to accommodate missile units could cause a unit to have “too many shots”.
  • Special Baseline Rules for Ships:
    • Supply cap is set as percentage of total fully loaded weight
    • Ammo use (to determine combat time) is also fixed
    • For Ships with main gun turrets > 90mm:
      • 1.5% Supply Cap, 5 tonne/hour per main gun turret use rate
    • For Ships without a main gun turret > 90mm:
      • 1% Supply Cap, 2 tonne/hour use rate

Supply Values

  • A P-47 carried about 2.5t of MG ammo for 8x12.7mm guns
  • BF-110 carried about .04t of MG ammo for 2x20mm+5x792mm
    • currently modeling an increase in supply carried for class 9 @ '34 and '39 and'42

Weapons Variables[edit | edit source]

There are three weapons related variables

  • Weapons
  • PrimaryWeapon
  • SecondaryWeapon

currently they are not used by the engine but at times an effort has been made to record the weapons systems on ships so that all boats with "2x127mm" have similar stats.

Missile Points Value[edit | edit source]

  • numeric value, Missiles Only
  • Number of points used when missile is loaded onto platform.
    • KJ heavily reviewed from 05/09 - 10/09

Value Assignment

Generally, Missiles were rated along following lines:

  • 2 point = AS-10 Karen, Nord AS-30/-30L, AGM-12 Bullpup…..and several of the bomb types.
  • 3 “ = Exocet, Harpoon, Otomat, YJ-82/83 and a few others
    • hence a surface ship with a Missile Capacity indicated as ‘23” would be carrying normally 8 Harpoon, or Exocet, etc.
  • 4 and 5 – several of the larger Russian SSMs, got this rating because of their larger size than found in standard Western SSMs (usually rate 3s)
    • Example, #17770 Slava CG with 16xP-500 Basalt (SS-N-12s) SSMs was rated ‘112’ in order to carry 16.
    • Similar situation with #177768 Kirov (Orlan) CGN with ‘140’ rating because of its 20xP-700 SSMs.
  • P-500 and P-700 are the largest SSMs around and were rated “7”

Because of the SR2020s design system, one could in theory arm a standard US or Japanese DD/DDG with capacity of ‘24” (standard with 8xHarpoon) with 3 of these missiles, but there is no way to prevent this given the game design as you explained it (it causes potential aberrations – but it is the closest to keeping it realistic.

Several Chinese DDDG – such as #17417 Luda III/Zhanjiang are carrying 16xSSMs – all Ying-ji-82s – Each rated at “3” and therefore have a capacity of 48. Same type of thing happens with new Indian missile corvettes of Kora class – 16xUran/SS-N-25. Too large to rate as “2” (comment follows).

In Aircraft rating for missile capacity, the smaller ASMs – based on weight and size – were rated ‘2’. Others, most common like AM-39 Exocet, remain at “3”, the bigger “7” ASMs carried on Tu-95KM (Bear-C) etc are translated into how many they can carry (as with case of Tu-16s, missiles like KSR-5/AS-6A capacity was only 2 missiles, and thus Tu-16s are limited to ‘14’. That in theory they could therefore carry 4xExocet or PJ-10 BraMos cannot be avoided, only minimized. Later, Tu-142M-Sea Dragon (II) /#13929 has been specifically modified to Indian Navy spec’s to carry PJ-10 on special under-wing racks, and therefore rating higher capacity.

Some of the larger AGMs, like Raptor/Popeye and others got bumped up to “4” size – and thus, an aircraft like the F-4E is limited to carrying 2xAGM-142, which is historical. Israeli’s for example us Popeye as standard on their F-4E-2000 – as was proposed for the Turkish F-4 upgrade program.

And, like the huge Mikoyan Kh-20/Kh-20M (AS-3 Kangaroo) were so large as to be comparable with the size of a Mig-19 fighter (in fact, prior to missile carriage, the R’s tested a modified Mig-19 airframe on one aircraft to test drop characteristics, impact on flight characteristics, performance, etc.) rated 9, which limits the Tu-95KM Bear-C to its historical “1” missile capacity. Later aircraft, such as #12206/ Bear-G are modified to accommodate their general AGM loads of cruise missiles.

On balance, the overall Missile Cap assigned does not imbalance the game, but does in some cases require more Port reloading (where several surface ship classes were rated ‘30’, they got knocked down to ‘24’ because of the standard 8xHarpoon or Exocet carried. Older French DDs often only carried 4xMM.38/39 series or 12 rating.

Missile Points Capacity[edit | edit source]

  • numeric value, never for missiles
  • Number of points available for loading missiles
    • Land units: value indicates maximum size of missiles that can be loaded
    • Air units: value indicates maximum size of missiles that can be loaded (/2?)
    • Naval units: maximum size of missiles that can be loaded = value/4
      • The 4x multiplier on ships means historical two on board missiles will actually get four.
        • Assuming minimum size of Anti-Ship missile being a 3, 12/4 = 3 pts size capacity.
  • If value given to an “upgrade” type unit may encounter situations the GUI is not built to accommodate.
  • Assign values according to notes on missile size values.

NuclearYield[edit | edit source]

  • Missiles Only
  • Kt yield of warhead for nuclear missile units.
  • Researched value, displayed in game but directly used by engine. (?)
    • need to confirm this
  • Used to determine damage values based on separate Nuclear Yield Damage chart.

NBC Prot[edit | edit source]

  • Y/N Unit is equipped for protection from nuclear, chemical or biological attacks.
  • Value can generally be researched.
  • For Facilities also

StratNuke[edit | edit source]

  • Y/N Strategic Nuclear Missile (generally 90 KT or greater and/or longer range)
  • Used only for missiles – Different ‘specialty’ icon in game, but not used in calcs/no engine effect

TacNuke[edit | edit source]

  • Y/N Tactical Nuclear Missile (generally less than 90 KT and/or shorter range)
  • Used only for missiles – Different ‘specialty’ icon in game, but not used in calcs/no engine effect

GuidedMis[edit | edit source]

  • Y/N unit follows target unit after launch. Missiles only.
  • Otherwise will always hit original target hex.

No Eff Loss / Move[edit | edit source]

  • Y/N unit can move without a loss of efficiency.
    • need to confirm this defeats long term flight efficiency loss not just "move/fire penalty" style.
  • Set Y for Air Patrol class (ie multiple crews, resting not required)

Move&Fire penalty[edit | edit source]

  • Y/N unit suffers penalties for moving and firing at the same time.
  • Y for all land classes except Infantry and Tanks
    • should turretless tanks be N? (Stridsvagen)

Turret Arc[edit | edit source]

  • numeric value, If ‘Limited Firing Arc’ and ‘Turret Rotation’ is set, this is total firing arc in degrees
    • Ie 90 would allow turret to rotate 45 degrees to left or right
  • If ‘Limited Firing Arc’ or ‘Turret Rotation’ is not set, then this is ignored.

Limited Firing Arc[edit | edit source]

  • Y/N can unit fire 360 degrees
  • If Unit has Turret, Set Y if Turret Rotation Arc is limited (see ‘TurretArc’ Value)
  • If Unit has no Turret, Set Y if Unit must turn to face direction of fire.
  • Set Y for most units without Turret (new SR5 standard), ie Anti Tank, AA
  • Set N for Infantry types (can shoot in all directions)
  • Set N for Air units (fighters, bombers) that don’t need to face unit to attack

Turret Rotation[edit | edit source]

  • Y/N Turret can Rotate.
  • Set Y for Tanks, units with Turrets.
  • If Set to N, then unit must turn to fire if ‘Limited Firing Arc’ is set.

Turret Immediate[edit | edit source]

  • Y/N Turret Rotations are ‘immediate’.
  • Unit with Turret can immediately turn turret towards any target.
  • No common use for this at present.

No land cap.[edit | edit source]

  • Y/N Unit cannot capture terrain.
  • Y for Art, AA, aircraft, missiles and submarines
    • CW - also for Class 20 transport
    • SR8 - also for class 16 carrier

River Xing[edit | edit source]

  • Y/N unit is fording capable
  • Unused

Amphibious[edit | edit source]

  • Y/N Unit can move across terrain using amphibious move rules

Airdrop[edit | edit source]

  • Y/N Unit can be unloaded from cargo while transporting unit is flying (and land safely)

Air Tanker[edit | edit source]

  • Y/N Unit can give fuel to a unit marked Air refuel=Y while flying

Air refuel[edit | edit source]

  • Y/N Unit can take fuel from a unit marked Air Tanker=Y while flying

ECM Equipped[edit | edit source]

  • Y/N unit has ECM effects
  • For Facilities also
  • Unimplemented

Dock to unload[edit | edit source]

  • Y/N. If N unit can unload cargo onto any shore hex using amphibious move rules

Has Production[edit | edit source]

  • True/False - Node produces a commodity
  • Facilities only.

LowVis[edit | edit source]

  • True/False - reduced spotting and sets hex as close combat
  • Facilities only

Naval Port[edit | edit source]

  • True/False - can load/unload even if Dock to unload = true
  • ships will use as home base
  • Facilities only

Military Base[edit | edit source]

  • True/False -Anything more than storage and fabrication nodes? Check usage
  • Facilities only

Industry[edit | edit source]

  • True/False - is an industry. All nodes related to commodities
  • Facilities only

Urban[edit | edit source]

  • True/False - is a city
  • Facilities only

Transportation[edit | edit source]

  • True/False - is transport type. Roads, rails and cities.
  • Facilities only

Bridging[edit | edit source]

  • True/False - can be used to cross rivers. Roads, rails and cities.
  • Facilities only

Rubble[edit | edit source]

  • True/False - type of rubble.
  • Facilities only

Synthetic Production[edit | edit source]

  • True/False - node does not require on map resource. Includes goods and power (other than hydro)
  • Facilities only

SynthAddCost[edit | edit source]

  • True/False - ?
  • Facilities only

Container[edit | edit source]

  • True/False - is a central hub upgrade
  • Facilities only

Civilian Node[edit | edit source]

  • True/False - Indicates type of container or where node can be placed
  • Facilities only

Industrial Node[edit | edit source]

  • True/False -
  • Facilities only

Military Node[edit | edit source]

  • True/False -
  • Facilities only

Water Node[edit | edit source]

  • True/False -
  • Facilities only

Short Deck Take-off[edit | edit source]

  • True/False - unit is capable of landing on any Carrier Units
    • Helicopters
    • VTOL
    • Seaplanes within certain sizes

Long Deck Take-off[edit | edit source]

  • True/False - the unit is capable of landing on AirCarrier=Y units that are not short deck

Direct Def[edit | edit source]

  • True/False -

For missile units, Y will give Launch Authority on by default

When minister queues missiles Autodeploy is on if Launch Authority on

When AI queues missiles all non-WMD Autodeploy on by default

When player queues missiles Autodeploy matches last used setting.

Ballistic Artillery[edit | edit source]

  • True/False - Unit is affected by all ballistic artillery technologies (Howitzer/Gun & Mortar)
  • Artillery without this flag set are considered Missile (MLRS) types

Stand-off unit[edit | edit source]

  • True/False - Unit is ‘Stand Off’ for Battle situations
    • Unit cannot be directly targeted if any Stand-off=N units are in the hex
      • Unit cannot knowingly enter ZOC of enemy units
      • Applies to Land and Naval units. Does not apply to Air units.
  • Generally Set for Land Unit Types: Artillery, Air Defense, Transport.
  • Generally Set for Naval Unit Types: Carrier, Transport

Bridge Build[edit | edit source]

  • True/False - can function as a bridge for other units.
  • Must be amphibious=Y

U/G Demol[edit | edit source]

  • True/False - can allow destruction of upgrades in non-loyal territory

Engineering unit[edit | edit source]

  • True/False - provides construction bonus for facilities in same hex

UPGRADE Unit[edit | edit source]

  • True/False - unit is a facility
  • Class 21/units IDed 21xxx only

No Research[edit | edit source]

  • True/False - is not shown in list of available to research units.
    • Used for units that are “refits” of other existing units, that are never built from scratch

No Build[edit | edit source]

  • True/False - Redundant?
    • would only be useful if we wanted a known design to be

Def Res[edit | edit source]

  • True/False - flagged as researched for all regions

Out of Prod[edit | edit source]

  • True/False - Tech level at which unit is hidden as “obsolete”
    • will not be shown in unit lists unless filter for “view obsolete” is made active.

Specialty:[edit | edit source]

  • Indicates a facility of a given specialty
  • Facilities only

StoreCap[edit | edit source]

  • Indicates a facility can store a limited number of units compatible to its StoreType.
  • Facilities only

StoreType[edit | edit source]

  • Bitmask. Indicates a facility stores units. Database presents bitmask in common named groupings. Request has been made to specify built type by class instead of by branch.
  • Facilities only

HexReqs[edit | edit source]

  • Bitmask. Unique equipment file ID# of facility that precedes this unit in build hierarchy. Max of 2 facility prereqs.
  • Facilities only

Special Tech[edit | edit source]

  • numeric value, two fields
  • Technology required before unit can be researched

Launch type[edit | edit source]

  • bitmask value, Missiles Only
  • Indicates platform type missile can be launched from. Used only for missiles
    • 1 Land
    • 2 Air
    • 4 Sea
    • 8 Sub
    • 16 Silo

Market Availability[edit | edit source]

(numeric value 0-9)

Probability of unit being offered by World Market. Does this exist in SR2020? 0 Never 1 Rarely 9 Often

Uses larger Block Size[edit | edit source]

  • Facilities: Set to indicate that node shows ‘full hex’ (don’t display other nodes). Generally should only be used for full-hex containers (ie large cities)
  • Units: Unused.

Mesh Flags1[edit | edit source]

  • bitmask value

[Valid]-[Mesh#]-[TurretView]-[TeamAlpha]-[Resvd]-[Resvd]-[Resvd]-[Resvd] Valid: T/F if this Mesh Entry is valid/used Mesh#: 0/1 for which main Mesh is referenced TurretView: T/F if this object is part of the Turret transformation (rotation) TeamAlpha: T/F if the texture contains a team alpha colour mask

Mesh Flags2[edit | edit source]

  • bitmask value

[Resvd]-[NoTexture]-[Fastanim]-[Pitchonly]-[ Resvd]-[Resvd]-[Resvd]-[Resvd] Resvd: For future use (Vertical axis flag?) OpDraw: Optional Draw Item (ie Medallion) can be set on/off Fastanim: Animation/lights act ‘fast’ Pitchonly: Only show when view is pitched (else always)

Mesh Objects[edit | edit source]

(byte value)

[Resvd 4 bits]-[Submesh # 4 bits] Submesh: 0-14 for Submesh for object, or 15 for ‘Use all Submeshes’

Mesh Type[edit | edit source]

  • byte value
  • [Resvd 4 bits]-[Mesh Type 4 bits]
    • Mesh Type: Mesh Usage type 0-15
      • 0: Ground Plane / Overhead quad
        • Always drawn when Pitchonly False
      • 1: Overhead quad (No-pitch use, also shadow use)
        • Overhead use: Pitchonly False, bhasshadow False
          • (Only shown if NO pitch; full colour)
        • Shadow use: Pitchonly True, bhasshadow True
          • (Colour modulated to ½ alpha black)
        • Both: Pitchonly False, bhasshadow True
          • (Shadow if pitch, Overhead if no pitch)
      • 2: Standard Object (Hull/base or Turret if ‘TurretView’ true)
      • 3: Non-Rotation Object (keeps facing in same direction)
      • 4: Reserved
      • 5: Animated (Rotating) object, full rotation loop
      • 6: Animated (Rotating) object, ping-pong using limited arc
      • 7: Reserved
      • 8: Reserved
      • 9: Reserved
      • 10: Light, fade in/out
      • 11: Light, Blink
      • 12: Ammo object – Regular Ammo
      • 13: Ammo object – Missile Ammo
      • 14: Point – Shot Point
      • 15: Point – Smokestack Point

Mesh ID[edit | edit source]

  • 2 numeric values

Mesh ID #s (two Meshes per unit), or 0

Texture[edit | edit source]

  • 4 numeric values
    • Texture Name overrides for each Mesh – Default is to use Mesh Default Texture
      • [0] – Texture Override for Mesh[0] Overhead Textures (Type 0/1)
      • [1] – Texture Override for Mesh[0] Other Textures
      • [2] – Texture Override for Mesh[1] Overhead Textures (Type 0/1)
      • [3] – Texture Override for Mesh[1] Other Textures

Mesh Scale[edit | edit source]

  • numeric value
  • Override Scale value for Mesh Draw (Default 1.0)

Fire SND [3][edit | edit source]

  • (numeric value)

Units / Facilities :

0: Direct Fire

1: Indirect Fire

2: AntiAir Fire

Missiles:

0: Launch Sound

1: Hit Sound

2: Unused

Indicates to use [n].wav as Regular fire sound for unit where[n] = value

  • See [/docs.google.com/spreadsheet/ccc%3Fkey%3D0Au2h6D7Ato7PdDlIc0tVVmNGVTFyZHFPT2lzX2FmSVE%26hl%3Den%20US Sound Index] for values of [n]
  • GG: For air units, 0 is direct fire on ground (could be gun like A-10 or dive bomb like Stuka); 1 is strategic bombing on ground targets; 2 is air to air fire.

Death Sound[edit | edit source]

  • (numeric value)

Sound for Unit Destruction (or Missile Interception)

Move Sound[edit | edit source]

  • (numeric value)

Sound unit makes while moving? Usage unknown.

Pic [4][edit | edit source]

Animation / Shot Graphic Effects 0: Direct fire 1: Indirect Fire 2: AntiAir Fire 3: Death (Only Death defined for Missiles?)

Description[edit | edit source]

  • Used only by designer currently for notes on unit entry.

Webdata[edit | edit source]

  • Used only by designer to track sources.

Gun Size[edit | edit source]

  • This column is not used in calculations; for show, & reference use
  • Keep this up to date for tanks & artillery in particular – in mm.

Engine HP[edit | edit source]

  • Not used in calculations; keep for show (ie web info interface?)
  • Only for self-propelled ground units & ships; blank for rest

Fuel Type[edit | edit source]

  • Not used in calculations, keep for show
    • EXCEPT Nuclear – make sure that is flagged accurately for future use
      • 1 Diesel
      • 2 Gas / Gas Turbine
      • 3 MultiFuel
      • 4 Jet Fuel – 4 Prop was also used to indicate prop planes
      • 8 Nuclear
  • As of SR2020 not even shown.

Special Unit Notes[edit | edit source]

UAV[edit | edit source]

UAVs are now considered by their role and specs:

  • UAVs with less than 100 km range are now ‘integrated’ with Infantry, Tank, and Recon units, as a ‘Spotting Range Enhancement’ (for Recon UAVs) Production Technology. Not modeled as separate units.
  • UAVs with greater than 100 km range may to be added to the appropriate Air class for their purpose – Attack or Patrol Class; depending on their limitations, they could also treated as integrated.
  • UAVs that would normally be attached to a battalion are not intended to be modeled separately. Only those that would be used independently.

Land Mines[edit | edit source]

Minefields are not simulated in SR5. As such, dedicated Mine Layer and Mine Sweeper units are not to be included.

Naval Mines[edit | edit source]

Naval Mines are not simulated in SR5. Dedicated Naval Mine-Laying vessels are not to be included in the equipment list, and dedicated Naval Mine-Sweeping vessels are also not to be included. Only vessels that have a primary role outside of Mine warfare are still be in.

Air Tankers[edit | edit source]

All tankers are assumed to have the ability to ‘refuel themselves’; as such, the maximum range of an air refueling tanker is to be recorded as the maximum ‘self-refuelled’ traveling range.

Cargo & Tender Ships[edit | edit source]

All Resupply, Cargo and Tender vessels are assumed to be able to adjust their cargo capacity between ‘Military Goods’ (fuel and/or Ammo) and Unit Transport.

Mortar Artillery[edit | edit source]

Weaker Hard Attack than Gun/Howitzer Artillery, but good Soft attack Lower ammo use, and longer combat time Higher initiative (faster reload times) Ranges are generally short, much shorter than Gun types Should be Cheaper Cost & Faster Build than Gun types

Hovercraft, Mechs[edit | edit source]

Class for unit is based on role and specs. - Hovercraft would tend to be Naval Patrol - Mechs would tend to be Infantry or Recon

BASELINE DATA VALUES[edit | edit source]

Values are per Squad/Equipment Piece.

‘Baselines’ are for average/median units of a certain type.

Unit Type Cost

(incl goods)

Build

Days

Initiative S H F CA MA HA N S CL GD AD ID CD CT
Soft Infantry $0.5M 0.25 3-4 14 10 4 10 0 0 2 0 25
Hard Inf 1970 $1-1.5M 0.5 3-4 16 16 9 8 0 0 2 0 25
Hard Inf 1990 $1.5-2.0M 0.75 3-4 24 18 12 10 0 0 3 0 25
Laser Inf
Mech 2
Elite Infantry 50
Tank 1970 $1.5-2.5M 1.1 2-5 10
Tank 1990 $2.5-4.5M 1.75 3-6 10
Laser Tank 3-6
Recon 3-4 24
Anti-Tank Gun 3-4 12
Anti-Tank HOT/TOW 1-2 8
Artillery Ballistic 1-2 6
Artillery Mortar 5-6 24
Artillery MLRS 1-2 2-4
AA – Short Range 7-8 10
AA - MANPADS 7-8 3
AA – Long Range 1-2 1-4
Helicopter 3-4 4
Interceptor 5-6 12
Fighter/Bomber 3-4 8
Multi-Role 4-5 12
Strategic Bomber 2
Other Aircraft 4-7
Patrol Boat 1-2 40
FF Class 3-4 80
DD Class 125 3-4 120
BB / CG 140
CV Class 2 120
Transport Class 1
Submarine 1 40

Facilities[edit | edit source]

Columns generally have the same meaning. The following columns are either different for Facilities or else only used for Facility types:

Cost[edit | edit source]

Notes:

In the wake of Turkey's joining NATO, prior to this there were not jet airfields in Turkey.  Longest concrete airfields were at Istanbul and Ankara with regard to civil / commercial airline service.  With US aid,  NATO  embarked on on the construction of 11 new airbases, all with jet fighter capable airfields.  The average cost was US$3.477 million - say $3.5 million average - as the total cost of the program was some L7.5 million (Pounds). - KJ

Ground Move Cost[edit | edit source]

  • numeric value, Terrain/Hex Move Cost when Facility Present – Only for Container/Centre Elements!

Naval Move Cost[edit | edit source]

  • numeric value, Terrain/Hex Move Cost when Facility Present – Only for Container/Centre Elements!

Supply Level[edit | edit source]

  • numeric value 0.00-1.00, Indicates level of supply generated by facility (cumulative among all nodes in hex)

Pollution[edit | edit source]

  • numeric value 0-255? Indicates level of Pollution generated by facility. Not currently used.

IG Cost[edit | edit source]

  • numeric value, Total value of industrial goods required during construction of facility.
Agri Output numeric value 0.00-1.00
Ore Output numeric value 0.00-1.00
Petrol Output numeric value 0.00-1.00
Coal Output numeric value 0.00-1.00
Uranium Output numeric value 0.00-1.00
Timber Output numeric value 0.00-1.00
Water Output numeric value 0.00-1.00
Electricity Output numeric value 0.00-1.00
C. Good Output numeric value 0.00-1.00
I. Goods Output numeric value 0.00-1.00
M. Goods Output numeric value 0.00-1.00

Maximum output for this type of resource when built in a hex

Raw Source[edit | edit source]

  • Products (by bitmask) used as raw materials for production output.
  • Raw Material use is from cvars2 value for amount used per output unit.
  • Both Synth and non-Synth use the Raw Materials as per this bitmask!
  • Caution: Bitmask and cvars2 values must be ‘in sync’ for each facility type.

uSynth[edit | edit source]

  • True/False, Facility is ‘Synthetic’, and so does not require map-resources.

uSynthAdd[edit | edit source]

  • True/False, Used for Synth production – when this is set, then the base cost of production is still added to the raw materials to get the total production cost. If this is not set, then the base cost of production is zero (only raw materials per Raw Source setting are used).
  • Electricity and Hydroponics has this flag set; Agri-Fuel does not have it set.

Facility Types[edit | edit source]

  • as returned by getugtype():
SR2010 SR2020
0 Urban 0 Unknown
1 Transport 1 Urban Container
2 Bridge 2 Industrial Container
3 Fort 3 Military Container
4 Base/Port 4 No-Container (Emplacement)
5 Industry 5 Industry
6 SpecialBase
  • 1 - Research
  • 2 - Missile Silo
  • 3 - Launch Pad
  • 4 - Spy/Intel
6 Business/Tourism
7 Other Base (supply point) 7 Mil Base (reserves)
8 8 Military Production
9 9 Research
10 10 Missile Silo
11 11 Launch Pad
12 12 Intel Academy
13 13 Other Military
  • Radar, Airdef, L/M Control etc
14 14 Bridge

Military Base Facilities[edit | edit source]

  • Reserve Bases: Must have ‘carriercap’ to indicate reserves capacity (option controlled)
    • Air: Set ‘Long Deck Carrier’ flag
    • Naval: Set ‘Naval Port’ flag
    • Land: Any others
  • (Note: should be possible to have airfields / seapiers by setting flags but no carriercap)
  • Production Bases:
    • Must have ‘buildcap’ to indicate number of build slots (usually 1)
    • Must have ‘buildclass’ value to indicate what classes can be built
  • (Allowing one facility to build multiple of land/air/sea/miss types not supported)