├── .github ├── ISSUE_TEMPLATE │ ├── 11_NEW-AIRCRAFT.yml │ ├── 12_NEW-LOADOUT.yml │ ├── 13_NEW-FACILITY.yml │ ├── 14_NEW-SHIP.yml │ ├── 15_NEW-SUBMARINE.yml │ ├── 16_NEW-SATELLITE.yml │ ├── 21_NEW-SENSOR.yml │ ├── 22_NEW-WEAPON.yml │ ├── 31_COPY-ENTRY.yml │ ├── 32_UPDATE-REQUEST.yml │ └── 33_BUG-REPORT.yml ├── labeler.yml └── workflows │ ├── issue-manager.yml │ └── labeler.yml ├── README.md └── forumpost.md /.github/ISSUE_TEMPLATE/11_NEW-AIRCRAFT.yml: -------------------------------------------------------------------------------- 1 | name: New Aircraft Request 2 | description: This form is used to request new aircraft. 3 | # title: "New Aircraft: " 4 | labels: ["addition", "aircraft"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new aircraft. 13 | 14 | - type: dropdown 15 | attributes: 16 | label: DB Selector 17 | description: Is this for DB3K, CWDB, or both? 18 | multiple: false 19 | options: 20 | - DB3K 21 | - CWDB 22 | - Both 23 | validations: 24 | required: true 25 | 26 | - type: input 27 | attributes: 28 | label: Baseline 29 | description: | 30 | Is there is an aircraft in the DB you recommend we start from? This is different from a "Copy Entry" in that most of its values will be changed, but we can use this to estimate anything we aren't sure of. 31 | 32 | For example, a Boeing 777 is different enough from a 747 that we couldn't simply copy one to make the other -- but it's a fair starting point. 33 | placeholder: ex. 2530 34 | validations: 35 | required: false 36 | 37 | - type: markdown 38 | attributes: 39 | value: | 40 | ## Basic Information 41 | 42 | - type: dropdown 43 | attributes: 44 | label: Hypothetical 45 | description: Is this a hypothetical aircraft, i.e. one not yet or never placed in service? 46 | multiple: false 47 | options: 48 | - "Yes" 49 | - "No" 50 | validations: 51 | required: true 52 | 53 | - type: input 54 | attributes: 55 | label: Name 56 | description: Provide designation and name (where applicable). 57 | placeholder: ex. VF-1 Valkyrie 58 | validations: 59 | required: true 60 | 61 | - type: input 62 | attributes: 63 | label: Country 64 | placeholder: ex. United Nations 65 | validations: 66 | required: false 67 | 68 | - type: input 69 | attributes: 70 | label: Service 71 | placeholder: ex. Space Force 72 | validations: 73 | required: false 74 | 75 | - type: input 76 | attributes: 77 | label: In Commission 78 | description: When was this aircraft in service for the specified country? 79 | placeholder: ex. 2008-2013 80 | validations: 81 | required: false 82 | 83 | - type: input 84 | attributes: 85 | label: Number in Service 86 | description: If this aircraft was in limited service, how many were there? 87 | placeholder: ex. 12x, 1x Crashed 2011 88 | validations: 89 | required: false 90 | 91 | - type: markdown 92 | attributes: 93 | value: | 94 | ## Dimensions and Weights 95 | 96 | - type: input 97 | attributes: 98 | label: Length (m) 99 | placeholder: ex. 14.2 100 | validations: 101 | required: true 102 | 103 | - type: input 104 | attributes: 105 | label: Wingspan (m) 106 | placeholder: ex. 14.8 107 | validations: 108 | required: true 109 | 110 | - type: input 111 | attributes: 112 | label: Height (m) 113 | placeholder: ex. 3.8 114 | validations: 115 | required: true 116 | 117 | - type: input 118 | attributes: 119 | label: Empty Weight (kg) 120 | placeholder: ex. 1400 121 | validations: 122 | required: true 123 | 124 | - type: input 125 | attributes: 126 | label: Maximum Takeoff Weight (MTOW) (kg) 127 | placeholder: ex. 1900 128 | validations: 129 | required: true 130 | 131 | - type: input 132 | attributes: 133 | label: Payload Weight (kg) 134 | placeholder: ex. 500 135 | validations: 136 | required: false 137 | 138 | - type: input 139 | attributes: 140 | label: Crew 141 | placeholder: ex. 2 142 | validations: 143 | required: true 144 | 145 | - type: markdown 146 | attributes: 147 | value: | 148 | ## Propulsion 149 | 150 | - type: input 151 | attributes: 152 | label: Propulsion 153 | description: Number and make of engines. 154 | placeholder: ex. 2x P&W FF-2001 155 | validations: 156 | required: true 157 | 158 | - type: input 159 | attributes: 160 | label: Rate of Climb (ft/min) 161 | placeholder: ex. 800 162 | validations: 163 | required: false 164 | 165 | - type: input 166 | attributes: 167 | label: Service Ceiling (ft) 168 | placeholder: ex. 36000 169 | validations: 170 | required: true 171 | 172 | - type: input 173 | attributes: 174 | label: Military/Afterburner Speed (kt) 175 | placeholder: ex. 520 176 | validations: 177 | required: true 178 | 179 | - type: input 180 | attributes: 181 | label: Cruise Speed (kt) 182 | placeholder: ex. 480 183 | validations: 184 | required: true 185 | 186 | - type: dropdown 187 | attributes: 188 | label: Supercruise 189 | description: Is this aircraft capable of supercruise? 190 | multiple: false 191 | options: 192 | - "Yes" 193 | - "No" 194 | validations: 195 | required: true 196 | 197 | - type: input 198 | attributes: 199 | label: Ferry Range (nm) 200 | description: Aircraft range at cruise speed w/ ferry loadout. 201 | placeholder: ex. 915 202 | validations: 203 | required: true 204 | 205 | - type: input 206 | attributes: 207 | label: Endurance (min) 208 | placeholder: ex. 600 209 | validations: 210 | required: false 211 | 212 | - type: input 213 | attributes: 214 | label: Takeoff / Landing Distance (m) 215 | placeholder: ex. 700 / 600 216 | validations: 217 | required: false 218 | 219 | - type: input 220 | attributes: 221 | label: Fuel Capacity (kg) 222 | validations: 223 | required: false 224 | 225 | - type: markdown 226 | attributes: 227 | value: | 228 | ## Sensing & Shooting 229 | 230 | - type: textarea 231 | attributes: 232 | label: Sensors 233 | description: | 234 | List the aircraft's sensors, placing each on a new line as in the example. 235 | placeholder: | 236 | 1x AWG-20 FCR 237 | 1x APS-21 Surveillance Radar 238 | 2x Generic FLIR 239 | 1x Generic EO/IR Ball 240 | validations: 241 | required: true 242 | 243 | - type: textarea 244 | attributes: 245 | label: Mounts 246 | description: | 247 | List the aircraft mounts (i.e., weapons), placing each on a new line as in the example. For aircraft, this will include only non-removable weapons, e.g. cannon; missiles, bombs, etc. should be listed as loadout options. 248 | placeholder: | 249 | 1x ROV-20 Laser Cannon 250 | 1x 55mm GU-11 Gun Pod (always installed) 251 | validations: 252 | required: true 253 | 254 | - type: textarea 255 | attributes: 256 | label: Loadout Options 257 | description: | 258 | If specific loadouts are known, list them here. In addition / otherwise, please list the weapons that the aircraft can employ. 259 | placeholder: | 260 | - 12x AMM-1 Hybrid Guided Multipurpose Missiles 261 | - 12x Mk82 LDGB 262 | - 6x RMS-1 AShM 263 | - 4x UUM-7 Micro-Missile Pods (14x HMM-01/pod) 264 | 265 | Or combinations of the above. 266 | validations: 267 | required: true 268 | 269 | - type: markdown 270 | attributes: 271 | value: | 272 | ## Miscellanious Capabilities 273 | 274 | - type: textarea 275 | attributes: 276 | label: Comms/Datalinks 277 | description: | 278 | List any known comms systems or datalinks, placing each on a new line as in the example. 279 | placeholder: | 280 | UHF Radio [Secure] 281 | VHF Radio [Secure] 282 | UHF Datalink 283 | validations: 284 | required: false 285 | 286 | - type: dropdown 287 | attributes: 288 | label: Aircraft Codes 289 | description: Indicate which (if any) of the following DB codes apply to this aircraft. 290 | multiple: true 291 | options: 292 | - Supermanouverability 293 | - HIFR Capable 294 | - Terrain Avoidance 295 | - Terrain Following 296 | - Fly-by-Wire 297 | - Blip Enhance 298 | - Night Navigation (Ferry, Air-to-Air, Air-to-Surface Missiles) 299 | - Night Navigation/Attack (Incl. Bomb, Rocket Delivery) 300 | - Bombsight - Basic 301 | - Bombsight - Ballistic Computing 302 | - Bombsight - Advanced Computing 303 | - Bombsight - Advanced Navigation (INS/GPS) 304 | - Helmet Mounted Sight / Display (HMS/HMD) 305 | - Probe Refuelling 306 | - Boom Refuelling 307 | - Centerline Drogue 308 | - Wing Drogue 309 | - Centerline Boom 310 | validations: 311 | required: false 312 | 313 | - type: markdown 314 | attributes: 315 | value: | 316 | ## Final Touches 317 | 318 | - type: textarea 319 | attributes: 320 | label: Comments 321 | description: Is there anything else you want to tell us so we can more effectively model this platform? 322 | validations: 323 | required: false 324 | 325 | - type: textarea 326 | attributes: 327 | label: Sources 328 | description: | 329 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 330 | 331 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 332 | validations: 333 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/12_NEW-LOADOUT.yml: -------------------------------------------------------------------------------- 1 | name: New Loadout(s) Request 2 | description: This form is used to request new loadouts for one or multiple aircraft. 3 | # title: "New Loadout: " 4 | labels: ["loadout"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new loadout. 13 | 14 | - type: dropdown 15 | attributes: 16 | label: DB Selector 17 | description: Is this for DB3K, CWDB, or both? 18 | multiple: false 19 | options: 20 | - DB3K 21 | - CWDB 22 | - Both 23 | validations: 24 | required: true 25 | 26 | - type: markdown 27 | attributes: 28 | value: | 29 | ## Loadout Information 30 | 31 | - type: input 32 | attributes: 33 | label: User(s) 34 | description: Which aircraft use this/these loadout(s)? If possible, please provide DBIDs; otherwise, a simple descriptor will suffice. 35 | placeholder: ex. USN F/A-18Cs, 2012- 36 | validations: 37 | required: true 38 | 39 | - type: textarea 40 | attributes: 41 | label: Weapons Carried 42 | description: | 43 | What weapons are carried? Include fuel tanks, sensor pods, etc. If requesting multiple loadouts, put a line between each so we can tell them apart. 44 | placeholder: | 45 | - 1x 12.7mm HMP 400 Gun Pod 46 | - 2x HYDRA APKWS II 70mm Rocket 47 | - 2x GBU-59/B Paveway II GPS/LGB 48 | validations: 49 | required: true 50 | 51 | - type: dropdown 52 | attributes: 53 | label: Requires Buddy Illumination 54 | description: Does this loadout require buddy illumination, i.e. is it carrying laser-guided weapons that the aircraft cannot direct organically? 55 | multiple: false 56 | options: 57 | - "Yes" 58 | - "No" 59 | validations: 60 | required: true 61 | 62 | - type: input 63 | attributes: 64 | label: Default Combat Radius (nm) 65 | description: How far is the aircraft capable of flying with this loadout under normal conditions? 66 | placeholder: ex. 3600 67 | validations: 68 | required: false 69 | 70 | - type: dropdown 71 | attributes: 72 | label: Weather Restrictions 73 | multiple: false 74 | options: 75 | - All-Weather 76 | - Limited All-Weather 77 | - Clear Weather 78 | validations: 79 | required: true 80 | 81 | - type: dropdown 82 | attributes: 83 | label: Time-of-Day Restrictions 84 | multiple: true 85 | options: 86 | - Day & Night 87 | - Day-Only 88 | - Night-Only 89 | validations: 90 | required: true 91 | 92 | - type: dropdown 93 | attributes: 94 | label: Capable of Quick Turnaround 95 | description: Can aircraft with this loadout be quickly reloaded and relaunched? 96 | multiple: false 97 | options: 98 | - "Yes" 99 | - "No" 100 | validations: 101 | required: true 102 | 103 | - type: markdown 104 | attributes: 105 | value: | 106 | ## Final Touches 107 | 108 | - type: textarea 109 | attributes: 110 | label: Comments 111 | description: Is there anything else you want to tell us so we can more effectively model this loadout? 112 | validations: 113 | required: false 114 | 115 | - type: textarea 116 | attributes: 117 | label: Sources 118 | description: | 119 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 120 | 121 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 122 | validations: 123 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/13_NEW-FACILITY.yml: -------------------------------------------------------------------------------- 1 | name: New Facility Request 2 | description: This form is used to request new facilities (SAMs, SSMs, etc.). 3 | # title: "New Facility: " 4 | labels: ["addition", "facility"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new facility. 13 | 14 | # ### Facility or Ground Unit? 15 | # As a rule of thumb, if the system is defined by the effect it has *on other domains*, it's probably best modelled as a facility. A SAM system, for example, is meant to engage targets in the air; a coastal defense missile battery is intended to engage targets at sea; this despite both technically being land-based platforms. 16 | 17 | # Modelling as a Ground Unit is more appropriate for land combat vehicles, i.e. vehicles whose primary purpose is to spot, engage, and destroy other targets on land or otherwise influence operations in that domain. Tanks, APCs/IFVs, trucks, and cars are all examples of vehicles best modelled in the Ground Units annex. 18 | 19 | - type: dropdown 20 | attributes: 21 | label: DB Selector 22 | description: Is this for DB3K, CWDB, or both? 23 | multiple: false 24 | options: 25 | - DB3K 26 | - CWDB 27 | - Both 28 | validations: 29 | required: true 30 | 31 | - type: markdown 32 | attributes: 33 | value: | 34 | ## Basic Information 35 | 36 | - type: dropdown 37 | attributes: 38 | label: Hypothetical 39 | description: Is this a hypothetical facility, i.e. one not yet or never placed in service? 40 | multiple: false 41 | options: 42 | - "Yes" 43 | - "No" 44 | validations: 45 | required: true 46 | 47 | - type: input 48 | attributes: 49 | label: Name 50 | description: Provide a name for the facility. 51 | placeholder: ex. SSM Btn (SM-62A Snark) 52 | validations: 53 | required: true 54 | 55 | - type: dropdown 56 | attributes: 57 | label: Facility Type 58 | description: Choose the type descriptor that best describes this facility. In most cases this will match the name. 59 | multiple: false 60 | options: 61 | - Radar 62 | - SAM 63 | - AAA 64 | - Arty 65 | - SSM 66 | - Armored 67 | - Inf 68 | - Mech 69 | - Motor 70 | - Ammo 71 | - Fuel 72 | - Supply 73 | validations: 74 | required: true 75 | 76 | - type: input 77 | attributes: 78 | label: Country 79 | placeholder: ex. United States 80 | validations: 81 | required: false 82 | 83 | - type: input 84 | attributes: 85 | label: Service 86 | placeholder: ex. Army 87 | validations: 88 | required: false 89 | 90 | - type: input 91 | attributes: 92 | label: In Commission 93 | description: When was the facility in service? 94 | placeholder: ex. 1959-1961 95 | validations: 96 | required: false 97 | 98 | - type: input 99 | attributes: 100 | label: Number in Service 101 | description: If this facility was in limited service, how many were there? 102 | placeholder: ex. 3x, 1x Decom. 1960 103 | validations: 104 | required: false 105 | 106 | - type: input 107 | attributes: 108 | label: Crew 109 | placeholder: ex. 40 110 | validations: 111 | required: false 112 | 113 | - type: input 114 | attributes: 115 | label: Dispersion Radius (m) 116 | description: How far apart are the individual "mounts" usually positioned? For example, in a SAM site, how far apart are the TELs? 117 | placeholder: ex. 40 118 | validations: 119 | required: false 120 | 121 | - type: markdown 122 | attributes: 123 | value: | 124 | ## Sensing & Shooting 125 | 126 | - type: textarea 127 | attributes: 128 | label: Sensors 129 | description: | 130 | List the facility's sensors where applicable, placing each on a new line as in the example. 131 | placeholder: | 132 | 1x KALKAN-II Radar 133 | 1x ASELFLIR-300D EOS 134 | validations: 135 | required: true 136 | 137 | - type: textarea 138 | attributes: 139 | label: Mounts 140 | description: | 141 | List the facility's mounts (i.e., weapons) where applicable, placing each on a new line. 142 | placeholder: | 143 | 3x HISAR-A TEL 144 | validations: 145 | required: true 146 | 147 | - type: textarea 148 | attributes: 149 | label: Magazines 150 | description: | 151 | List the facility's available reloads. 152 | placeholder: | 153 | 24x HISAR-A Missles 154 | validations: 155 | required: false 156 | 157 | - type: markdown 158 | attributes: 159 | value: | 160 | ## Miscellanious Capabilities 161 | 162 | - type: textarea 163 | attributes: 164 | label: Aircraft & Docking Facilities 165 | description: List any docking and/or aircraft facilities, placing each on a new line. 166 | placeholder: | 167 | 1x Pad (Medium Aircraft) 168 | validations: 169 | required: false 170 | 171 | - type: markdown 172 | attributes: 173 | value: | 174 | ## Final Touches 175 | 176 | - type: textarea 177 | attributes: 178 | label: Comments 179 | description: Is there anything else you want to tell us so we can more effectively model this platform? 180 | validations: 181 | required: false 182 | 183 | - type: textarea 184 | attributes: 185 | label: Sources 186 | description: | 187 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 188 | 189 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 190 | validations: 191 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/14_NEW-SHIP.yml: -------------------------------------------------------------------------------- 1 | name: New Ship Request 2 | description: This form is used to request new ships/boats/watercraft. 3 | # title: "New Ship: " 4 | labels: ["addition", "ship"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new ship. 13 | 14 | ### On Class Requests 15 | If you're requesting an entire class of ship rather than a specific vessel, please fill out the form as if for the class nameship. For example, if requesting the Arleigh Burke-class, fill out the form as if for DDG-51. 16 | 17 | If the class saw significant changes/blocks/flights/etc., it may be worth filing separate requests to cover these differences. Please fill out the follow-on forms as if for the block/flight nameship. For example, if requesting a Flight II Arleigh Burke-class, fill out the form as if for DDG-72. 18 | 19 | ### On Multinational Vessels 20 | Be cautious filing single requests for ships in the service of multiple countries. Most ships are sold with different fittings or refit on transfer; these changes often warrant separate requests. 21 | 22 | - type: dropdown 23 | attributes: 24 | label: DB Selector 25 | description: Is this for DB3K, CWDB, or both? 26 | multiple: false 27 | options: 28 | - DB3K 29 | - CWDB 30 | - Both 31 | validations: 32 | required: true 33 | 34 | - type: input 35 | attributes: 36 | label: Baseline 37 | description: | 38 | Is there is a ship in the DB you recommend we start from? This is different from a "Copy Entry" in that most of its values will be changed, but we can use this to estimate anything we aren't sure of. 39 | 40 | For example, a Pohang-class frigate is different enough from the Donghae-class that we couldn't simply copy one to model the other -- but it'd be a fair starting point. 41 | placeholder: ex. 2530 42 | validations: 43 | required: false 44 | 45 | - type: markdown 46 | attributes: 47 | value: | 48 | ## Basic Information 49 | 50 | - type: dropdown 51 | attributes: 52 | label: Hypothetical 53 | description: Is this a hypothetical vessel, i.e. one not yet or never placed in service? 54 | multiple: false 55 | options: 56 | - "Yes" 57 | - "No" 58 | validations: 59 | required: true 60 | 61 | - type: input 62 | attributes: 63 | label: Name 64 | description: Provide classification, pennant number, and name (where applicable). 65 | placeholder: ex. Y 467 Harekaze 66 | validations: 67 | required: true 68 | 69 | - type: input 70 | attributes: 71 | label: Class 72 | placeholder: ex. Kagerou-class 73 | validations: 74 | required: false 75 | 76 | - type: input 77 | attributes: 78 | label: Country 79 | placeholder: ex. Japan 80 | validations: 81 | required: false 82 | 83 | - type: input 84 | attributes: 85 | label: Service 86 | placeholder: ex. Navy 87 | validations: 88 | required: false 89 | 90 | - type: input 91 | attributes: 92 | label: In Commission 93 | description: | 94 | When was the *class* in service? 95 | 96 | If requesting a specific vessel, this will match the vessel's service dates. If requesting a class (and therefore modelling a nameship), the out-of-service date may be much later than the nameship's decommissioning. 97 | placeholder: ex. 1991-Present 98 | validations: 99 | required: false 100 | 101 | - type: input 102 | attributes: 103 | label: Number in Service 104 | description: If this ship was in limited service, how many were there? 105 | placeholder: ex. 5x, 3x Sunk/Scuttled 1993 106 | validations: 107 | required: false 108 | 109 | - type: markdown 110 | attributes: 111 | value: | 112 | ## Dimensions and Tonnage 113 | 114 | - type: input 115 | attributes: 116 | label: Length (m) 117 | placeholder: ex. 118.5 118 | validations: 119 | required: true 120 | 121 | - type: input 122 | attributes: 123 | label: Beam (m) 124 | placeholder: ex. 10.8 125 | validations: 126 | required: true 127 | 128 | - type: input 129 | attributes: 130 | label: Draft (m) 131 | placeholder: ex. 3.76 132 | validations: 133 | required: true 134 | 135 | - type: input 136 | attributes: 137 | label: Standard Displacement (t) 138 | description: Interchangeable with normal. If only a single number is provided for displacement, assume it's standard. 139 | placeholder: ex. 1600 140 | validations: 141 | required: true 142 | 143 | - type: input 144 | attributes: 145 | label: Full Displacement (t) 146 | placeholder: ex. 2000 147 | validations: 148 | required: false 149 | 150 | - type: input 151 | attributes: 152 | label: Empty Displacement (t) 153 | placeholder: ex. 1400 154 | validations: 155 | required: false 156 | 157 | - type: input 158 | attributes: 159 | label: Complement 160 | placeholder: ex. 31 161 | validations: 162 | required: true 163 | 164 | - type: input 165 | attributes: 166 | label: Max Sea State 167 | description: What is the highest Sea State in which this ship can effectively operate? 168 | placeholder: ex. 5 169 | validations: 170 | required: false 171 | 172 | - type: markdown 173 | attributes: 174 | value: | 175 | ## Propulsion 176 | 177 | - type: dropdown 178 | attributes: 179 | label: Primary Propulsion Type 180 | description: For CODAG, etc. select "Diesel". 181 | multiple: false 182 | options: 183 | - Diesel 184 | - Steam 185 | - Gas Turbine 186 | - Gasoline 187 | - Electric 188 | - Sail 189 | validations: 190 | required: true 191 | 192 | - type: input 193 | attributes: 194 | label: Propulsion 195 | description: Number, make, and type of engines. For CODAG, etc. you can specify here. 196 | placeholder: ex. 2x MAN 12V28/33D Diesels, 1x MT-30 Gas Turbine, CODAG 197 | validations: 198 | required: true 199 | 200 | - type: input 201 | attributes: 202 | label: Fuel Capacity (kg) 203 | placeholder: ex. 1300 204 | validations: 205 | required: false 206 | 207 | - type: input 208 | attributes: 209 | label: Flank Speed (kt) 210 | placeholder: ex. 26 211 | validations: 212 | required: true 213 | 214 | - type: input 215 | attributes: 216 | label: Range (nm) at Speed (kt) 217 | description: This will usually be at the ship's cruise speed. 218 | placeholder: ex. 1000nm @ 15kts 219 | validations: 220 | required: true 221 | 222 | - type: markdown 223 | attributes: 224 | value: | 225 | ## Sensing & Shooting 226 | 227 | - type: textarea 228 | attributes: 229 | label: Sensors 230 | description: | 231 | List the ship's sensors, placing each on a new line as in the example. 232 | placeholder: | 233 | 2x Generic Navigation Radar (Furuno) 234 | 1x TRS-3D 235 | 2x STIR 1.2 Mk2 236 | validations: 237 | required: true 238 | 239 | - type: textarea 240 | attributes: 241 | label: Mounts 242 | description: | 243 | List the ship's mounts (i.e., weapons), placing each on a new line as in the example. For torpedo tubes, VLS, etc. indicate what weapons are loaded. 244 | placeholder: | 245 | 1x 76mm/62 OTO Melara Super Rapido w/ DART Ammo 246 | 2x 533m Triple Torpedo Tube w/ Black Shark Torpedoes 247 | 2x MM.40 Quad Launchers w/ Exocet Blk 3A 248 | validations: 249 | required: true 250 | 251 | - type: markdown 252 | attributes: 253 | value: | 254 | ## Miscellanious Capabilities 255 | 256 | - type: textarea 257 | attributes: 258 | label: Aircraft & Docking Facilities 259 | description: | 260 | List any docking and/or aircraft facilities, placing each on a new line as in the example. 261 | placeholder: | 262 | 2x Davits for 7m RHIB 263 | 1x Pad/Hangar for Medium Helicopter 264 | validations: 265 | required: false 266 | 267 | - type: textarea 268 | attributes: 269 | label: Comms/Datalinks 270 | description: | 271 | List any known comms systems or datalinks, placing each on a new line as in the example. 272 | placeholder: | 273 | VHF/UHF Radio 274 | SATCOM 275 | Link 11 276 | Link 14 277 | Link 16 278 | validations: 279 | required: false 280 | 281 | - type: dropdown 282 | attributes: 283 | label: Ship Codes 284 | description: Indicate which (if any) of the following DB codes apply to this vessel. 285 | multiple: true 286 | options: 287 | - Nuclear Shock Resistant 288 | - Degaussed Steel Hull 289 | - Onboard Degaussing Gear (Magnetometer) 290 | - Prairie Masker 291 | - Advanced Quieting 292 | - Passive or Single Stabilizers 293 | - Dual or Triple Stabilizers 294 | - Hovercraft/SES 295 | - Catamaran/Trimaran Multihull 296 | - Wooden Hull Construction 297 | - Glass Reinforced Polyester (GRP) Construction 298 | - All Aluminum Construction 299 | - Aluminum Superstructure Only 300 | - Built to Mercantile Standards 301 | - Low Construction Standards 302 | - Laid Down Before 1930 303 | - Helo In-Flight Refuel (HIFR) Capable 304 | validations: 305 | required: false 306 | 307 | - type: markdown 308 | attributes: 309 | value: | 310 | ## Final Touches 311 | 312 | - type: textarea 313 | attributes: 314 | label: Comments 315 | description: Is there anything else you want to tell us so we can more effectively model this platform? 316 | validations: 317 | required: false 318 | 319 | - type: textarea 320 | attributes: 321 | label: Sources 322 | description: | 323 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 324 | 325 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 326 | validations: 327 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/15_NEW-SUBMARINE.yml: -------------------------------------------------------------------------------- 1 | name: New Submarine Request 2 | description: This form is used to request new submarines/USVs. 3 | # title: "New Submarine: " 4 | labels: ["addition", "submarine"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new sub. 13 | 14 | ### On Class Requests 15 | If you're requesting an entire class of sub rather than a specific vessel, please fill out the form as if for the class nameship. For example, if requesting the Virginia-class, fill out the form as if for SSN-774. 16 | 17 | If the class saw significant changes/blocks/flights/etc., it may be worth filing separate requests to cover these differences. Please fill out the follow-on forms as if for the block/flight nameship. For example, if requesting the Flight II Virginia-class, fill out the form as if for SSN-778. 18 | 19 | - type: dropdown 20 | attributes: 21 | label: DB Selector 22 | description: Is this for DB3K, CWDB, or both? 23 | multiple: false 24 | options: 25 | - DB3K 26 | - CWDB 27 | - Both 28 | validations: 29 | required: true 30 | 31 | - type: input 32 | attributes: 33 | label: Baseline 34 | description: | 35 | Is there is a sub in the DB you recommend we start from? This is different from a "Copy Entry" in that most of its values will be changed, but we can use this to estimate anything we aren't sure of. 36 | 37 | For example, a Type 035 is different enough from a Type 033 that we couldn't simply copy one to model the other -- but it'd be a fair starting point. 38 | placeholder: ex. 2530 39 | validations: 40 | required: false 41 | 42 | - type: markdown 43 | attributes: 44 | value: | 45 | ## Basic Information 46 | 47 | - type: dropdown 48 | attributes: 49 | label: Hypothetical 50 | description: Is this a hypothetical vessel, i.e. one not yet or never placed in service? 51 | multiple: false 52 | options: 53 | - "Yes" 54 | - "No" 55 | validations: 56 | required: true 57 | 58 | - type: input 59 | attributes: 60 | label: Name 61 | description: Provide classification, pennant number, and name (where applicable). 62 | placeholder: ex. SS-161 Stingray 63 | validations: 64 | required: true 65 | 66 | - type: input 67 | attributes: 68 | label: Class 69 | placeholder: ex. Balao-class 70 | validations: 71 | required: false 72 | 73 | - type: input 74 | attributes: 75 | label: Country 76 | placeholder: ex. United States 77 | validations: 78 | required: false 79 | 80 | - type: input 81 | attributes: 82 | label: Service 83 | placeholder: ex. Navy 84 | validations: 85 | required: false 86 | 87 | - type: input 88 | attributes: 89 | label: In Commission 90 | description: | 91 | When was the *class* in service? 92 | 93 | If requesting a specific vessel, this will match the vessel's service dates. If requesting a class (and therefore modelling a nameship), the out-of-service date may be much later than the nameship's decommissioning. 94 | placeholder: ex. 1943-1971 95 | validations: 96 | required: false 97 | 98 | - type: input 99 | attributes: 100 | label: Number in Service 101 | description: If this sub was in limited service, how many were there? 102 | placeholder: ex. 4x, 1x Sunk 1944 103 | validations: 104 | required: false 105 | 106 | - type: markdown 107 | attributes: 108 | value: | 109 | ## Dimensions and Tonnage 110 | 111 | - type: input 112 | attributes: 113 | label: Length (m) 114 | placeholder: ex. 95 115 | validations: 116 | required: true 117 | 118 | - type: input 119 | attributes: 120 | label: Beam (m) 121 | placeholder: ex. 8.3 122 | validations: 123 | required: true 124 | 125 | - type: input 126 | attributes: 127 | label: Draft (m) 128 | placeholder: ex. 5.1 129 | validations: 130 | required: true 131 | 132 | - type: input 133 | attributes: 134 | label: Standard Displacement (t) 135 | description: Interchangeable with normal. If only a single number is provided for displacement, assume it's standard. 136 | placeholder: ex. 1300 137 | validations: 138 | required: true 139 | 140 | - type: input 141 | attributes: 142 | label: Submerged Displacement (t) 143 | placeholder: ex. 1450 144 | validations: 145 | required: false 146 | 147 | - type: input 148 | attributes: 149 | label: Empty Displacement (t) 150 | placeholder: ex. 1000 151 | validations: 152 | required: false 153 | 154 | - type: input 155 | attributes: 156 | label: Max Depth (m) 157 | placeholder: ex. 350 158 | validations: 159 | required: false 160 | 161 | - type: input 162 | attributes: 163 | label: Complement 164 | placeholder: ex. 31 165 | validations: 166 | required: true 167 | 168 | - type: markdown 169 | attributes: 170 | value: | 171 | ## Propulsion 172 | Please provide some information on propulsion, speeds, etc. for the sub. 173 | 174 | - type: dropdown 175 | attributes: 176 | label: Primary Propulsion Type 177 | multiple: false 178 | options: 179 | - Nuclear 180 | - Diesel/Electric 181 | - Diesel/Electric w/ AIP 182 | - Electric (UUVs) 183 | validations: 184 | required: true 185 | 186 | - type: input 187 | attributes: 188 | label: Propulsion 189 | description: Number, make, and type of primary engines. On diesel-electric subs, this will be the diesel engines. 190 | placeholder: ex. 4x Fairbanks-Morse Model 38D8 Diesels 191 | validations: 192 | required: true 193 | 194 | - type: input 195 | attributes: 196 | label: Flank Speed at Surface (kt) 197 | placeholder: ex. 20 198 | validations: 199 | required: true 200 | 201 | - type: input 202 | attributes: 203 | label: Flank Speed Submerged (kt) 204 | placeholder: ex. 24 205 | validations: 206 | required: false 207 | 208 | - type: input 209 | attributes: 210 | label: Range (nm) at Speed (kt) 211 | description: This will usually be at the sub's cruise speed. 212 | placeholder: ex. 1000nm @ 15kts 213 | validations: 214 | required: true 215 | 216 | - type: input 217 | attributes: 218 | label: Range (nm) on AIP 219 | description: If the sub is capable of AIP, how far is its range when using this method of propulsion? 220 | placeholder: ex. 850 221 | validations: 222 | required: false 223 | 224 | - type: input 225 | attributes: 226 | label: Fuel Capacity (kg) 227 | validations: 228 | required: false 229 | 230 | - type: markdown 231 | attributes: 232 | value: | 233 | ## Sensing & Shooting 234 | 235 | - type: textarea 236 | attributes: 237 | label: Sensors 238 | description: | 239 | List the sub's sensors, placing each on a new line as in the example. 240 | placeholder: | 241 | 1x OMS 100 / SERO 400 Periscope Suite 242 | 1x Type 1007 Radar 243 | 1x DBQS-40 Sonar 244 | validations: 245 | required: true 246 | 247 | - type: textarea 248 | attributes: 249 | label: Mounts 250 | description: | 251 | List the sub's mounts (i.e., weapons), placing each on a new line as in the example. For torpedo tubes, VLS, etc. indicate what weapon(s) are loaded. 252 | placeholder: | 253 | 6x 533mm TT (BSA Torpedoes) 254 | 2x TAU-2000 DL 255 | validations: 256 | required: true 257 | 258 | - type: textarea 259 | attributes: 260 | label: Magazines 261 | description: | 262 | Describe the sub's available reloads, if known and applicable. 263 | placeholder: | 264 | 6x BSA Torpedoes 265 | validations: 266 | required: true 267 | 268 | - type: markdown 269 | attributes: 270 | value: | 271 | ## Miscellanious Capabilities 272 | 273 | - type: textarea 274 | attributes: 275 | label: Comms/Datalinks 276 | description: | 277 | List any known comms systems or datalinks, placing each mount on a new line as in the example. 278 | placeholder: | 279 | VHF/UHF Radio [Secure] 280 | SATCOM 281 | Link 11 282 | Link 14 283 | Link 16 284 | validations: 285 | required: false 286 | 287 | - type: dropdown 288 | attributes: 289 | label: sub Codes 290 | description: Indicate which (if any) of the following DB codes apply to this vessel. 291 | multiple: true 292 | options: 293 | - Shock Resistant 294 | - Nonmagnetic Hull 295 | - Titanium Hull 296 | - Double Hull 297 | - Shrouded Propulsor 298 | - Advanced Propulsor 299 | - Lithium-Ion Batteries 300 | - Snorkel 301 | - No Launch Transient 302 | - Low Construction Standards 303 | - Laid Down Before 1930 304 | validations: 305 | required: false 306 | 307 | - type: markdown 308 | attributes: 309 | value: | 310 | ## Final Touches 311 | 312 | - type: textarea 313 | attributes: 314 | label: Comments 315 | description: Is there anything else you want to tell us so we can more effectively model this platform? 316 | validations: 317 | required: false 318 | 319 | - type: textarea 320 | attributes: 321 | label: Sources 322 | description: | 323 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 324 | 325 | We do check these where possible. If we can't corroborate your information, we may provide replacements from our own sources or discard your request entirely. 326 | validations: 327 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/16_NEW-SATELLITE.yml: -------------------------------------------------------------------------------- 1 | name: New Satellite Request 2 | description: This form is used to request a new satellite / satellite series. 3 | # title: "New Satellite: " 4 | labels: ["addition", "satellite"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new satellite. 13 | 14 | - type: dropdown 15 | attributes: 16 | label: DB Selector 17 | description: Is this for DB3K, CWDB, or both? 18 | multiple: false 19 | options: 20 | - DB3K 21 | - CWDB 22 | - Both 23 | validations: 24 | required: true 25 | 26 | - type: markdown 27 | attributes: 28 | value: | 29 | ## Basic Information 30 | 31 | - type: dropdown 32 | attributes: 33 | label: Hypothetical 34 | description: Is this a hypothetical satellite, i.e. one not yet or never placed in service? 35 | multiple: false 36 | options: 37 | - "Yes" 38 | - "No" 39 | validations: 40 | required: true 41 | 42 | - type: input 43 | attributes: 44 | label: Series Name 45 | description: What is the satellite called? For satellite series, provide the general program name. 46 | placeholder: ex. Jumpseat 47 | validations: 48 | required: true 49 | 50 | - type: dropdown 51 | attributes: 52 | label: Satellite Type 53 | description: Which best describes this satellite/series? 54 | multiple: false 55 | options: 56 | - IMGSAT 57 | - SIGINT 58 | - ELINT 59 | - MASINT 60 | validations: 61 | required: true 62 | 63 | - type: input 64 | attributes: 65 | label: Country 66 | placeholder: ex. United States 67 | validations: 68 | required: false 69 | 70 | - type: input 71 | attributes: 72 | label: Service 73 | placeholder: ex. Air Force 74 | validations: 75 | required: false 76 | 77 | - type: input 78 | attributes: 79 | label: In Commission 80 | description: When was this satellite/series in service? 81 | placeholder: ex. 1971-1985 82 | validations: 83 | required: false 84 | 85 | - type: markdown 86 | attributes: 87 | value: | 88 | ## Dimensions and Weights 89 | These numbers are less important for satellites than, say, for aircraft, so don't worry if you can't find some (or any) of this data. 90 | 91 | - type: input 92 | attributes: 93 | label: Length (m) 94 | placeholder: ex. 1 95 | validations: 96 | required: false 97 | 98 | - type: input 99 | attributes: 100 | label: Width/Span (m) 101 | placeholder: ex. 1 102 | validations: 103 | required: false 104 | 105 | - type: input 106 | attributes: 107 | label: Height (m) 108 | placeholder: ex. 1 109 | validations: 110 | required: false 111 | 112 | - type: input 113 | attributes: 114 | label: Weight (kg) 115 | placeholder: ex. 100 116 | validations: 117 | required: false 118 | 119 | - type: markdown 120 | attributes: 121 | value: | 122 | ## Orbital Data 123 | 124 | - type: dropdown 125 | attributes: 126 | label: Is Geostationary 127 | multiple: false 128 | options: 129 | - "Yes" 130 | - "No" 131 | validations: 132 | required: true 133 | 134 | - type: textarea 135 | attributes: 136 | label: COSPAR ID 137 | description: | 138 | Provide the COSPAR ID for each satellite in the series. 139 | placeholder: | 140 | USH-10: 2006-015B 141 | validations: 142 | required: true 143 | 144 | - type: textarea 145 | attributes: 146 | label: Launch/Comm. & Decom./Deorbit Date(s) 147 | description: | 148 | Provide the launch dates (+ commission date, if different) and decom./deorbit dates for each satellite in the series. This is different from the "In Commision" date provided earlier, which covers the entire series. 149 | placeholder: | 150 | NAG-15A: 24 DEC 84 // 28 APR 04 (Deorbit: 4 OCT 07) 151 | validations: 152 | required: true 153 | 154 | - type: textarea 155 | attributes: 156 | label: TLE 157 | description: | 158 | Provide a two or three line TLE for each satellite in the series. 159 | placeholder: | 160 | 1 46320U 20061BA 21193.49823640 .00000228 00000-0 17253-4 0 9990 161 | 2 46320 97.4876 266.6950 0001318 223.9323 261.1888 15.11370748 47168 162 | validations: 163 | required: true 164 | 165 | - type: markdown 166 | attributes: 167 | value: | 168 | ## Sensor Package 169 | 170 | - type: textarea 171 | attributes: 172 | label: Sensors 173 | description: | 174 | List the satellite's sensors, placing each mount on a new line as in the example. Generic sensors are fine. 175 | placeholder: | 176 | 1x Generic Satellite Visual Camera (3rd Gen) 177 | 1x Generic Satellite SIGINT 178 | validations: 179 | required: true 180 | 181 | - type: markdown 182 | attributes: 183 | value: | 184 | ## Final Touches 185 | 186 | - type: textarea 187 | attributes: 188 | label: Comments 189 | description: Is there anything else you want to tell us so we can more effectively model this platform? 190 | validations: 191 | required: false 192 | 193 | - type: textarea 194 | attributes: 195 | label: Sources 196 | description: | 197 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 198 | 199 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 200 | validations: 201 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/21_NEW-SENSOR.yml: -------------------------------------------------------------------------------- 1 | name: New Sensor Request 2 | description: This form is used to request new sensors, specifically radar and sonar. 3 | # title: "New Sensor: " 4 | labels: ["addition", "sensor"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new sensor. Although *Command* models a wide variety of sensor types, this form is only intended for use with radar and sonar. Other sensors are simple enough to model that they will never require a separate subcomponent request (see below). 13 | 14 | ### A Note on Requesting Subcomponents 15 | Subcomponents -- such as weapons and sensors -- are of little use without a host. While it is true that weapon records / sensors may be added to various platforms in the mission editor, a weapon/sensor that is not currently employed on any platform in the DB is rarely worth the time it takes to add. 16 | 17 | If the weapon/sensor *is* employed on another platform but not represented in the DB, it may be better to file an addition, update, or loadout request instead. If we need you to file a separate subcomponent request, we'll let you know. 18 | 19 | - type: dropdown 20 | attributes: 21 | label: DB Selector 22 | description: Is this for DB3K, CWDB, or both? 23 | multiple: false 24 | options: 25 | - DB3K 26 | - CWDB 27 | - Both 28 | validations: 29 | required: true 30 | 31 | - type: input 32 | attributes: 33 | label: Baseline 34 | description: | 35 | Is there is a sensor in the DB you recommend we start from? This is different from a "Copy Entry" in that most of its values will be changed, but we can use this to estimate anything we aren't sure of. 36 | 37 | For example, the AN/APG-77 is different enough from the AN/APG-81 that we couldn't simply copy one to model the other -- but it'd be a fair starting point. 38 | placeholder: ex. 2530 39 | validations: 40 | required: false 41 | 42 | - type: markdown 43 | attributes: 44 | value: | 45 | ## Common Information 46 | 47 | - type: dropdown 48 | attributes: 49 | label: Hypothetical 50 | description: Is this a hypothetical sensor, i.e. one not yet or never placed in service? 51 | multiple: false 52 | options: 53 | - "Yes" 54 | - "No" 55 | validations: 56 | required: true 57 | 58 | - type: input 59 | attributes: 60 | label: Name 61 | description: Provide designation and name (where applicable). 62 | placeholder: ex. SBS-800-1 SharpEye 63 | validations: 64 | required: true 65 | 66 | - type: dropdown 67 | attributes: 68 | label: Sensor Generation 69 | description: Generally, a sensor is assigned a Generation based on the R&D phase rather than the deployment phase, so a sensor that was deployed in 2022 after being developed from 2018-2022 would have a Late 2010’s Generation. 70 | multiple: false 71 | options: 72 | - Early 1950s 73 | - Late 1950s 74 | - Early 1960s 75 | - Late 1960s 76 | - Early 1970s 77 | - Late 1970s 78 | - Early 1980s 79 | - Late 1980s 80 | - Early 1990s 81 | - Late 1990s 82 | - Early 2000s 83 | - Late 2000s 84 | - Early 2010s 85 | - Late 2010s 86 | - Early 2020s 87 | - Late 2020s 88 | validations: 89 | required: true 90 | 91 | - type: markdown 92 | attributes: 93 | value: | 94 | ## Capabilities 95 | 96 | - type: input 97 | attributes: 98 | label: Range (nm) 99 | description: Use instrumented range. Detailed detection info (e.g. 60nm w/ 5m2 RCS) can go in the comments section. 100 | placeholder: ex. 0.2-85.0 101 | validations: 102 | required: true 103 | 104 | - type: input 105 | attributes: 106 | label: Horizontal Arc (deg) 107 | description: If the sensor has a known horizontal arc/limitation, enter it here. (This is most relevant for aircraft radars.) 108 | placeholder: ex. 60deg 109 | validations: 110 | required: false 111 | 112 | - type: input 113 | attributes: 114 | label: Vertical Arc (deg) 115 | description: If the sensor has a known vertical arc/limitation, enter it here. (This is most relevant for older aircraft radars.) 116 | placeholder: ex. 20deg 117 | validations: 118 | required: false 119 | 120 | - type: dropdown 121 | attributes: 122 | label: Sensor Capabilities 123 | multiple: true 124 | options: 125 | - Air Search 126 | - Surface Search 127 | - Submarine Search 128 | - Land Search - Fixed Facility 129 | - Land Search - Mobile Unit 130 | - Periscope Search 131 | - C-RAM (Counter-Rocket, Artillery and Mortar) 132 | - Space Search - ABM 133 | - Mine & Obstacle Search 134 | - Torpedo Warning 135 | - Range Information 136 | - Altitude Information 137 | - Speed Information 138 | - Heading Information 139 | - Navigation Only 140 | - Ground Mapping Only 141 | - Terrain Avoidance / Following Only 142 | - Weather Only 143 | - Weather and Navigation Only 144 | validations: 145 | required: true 146 | 147 | - type: dropdown 148 | attributes: 149 | label: Sensor Codes 150 | description: Indicate which (if any) of the following capability codes apply to this sensor. 151 | multiple: true 152 | options: 153 | - Identification Friend or Foe (IFF) [Side Info] 154 | - Classification [Class Info] / Brilliant Weapon [Automatic Target Acquisition] 155 | - Non-Cooperative Target Recognition (NCTR) - Jet Engine Modulation [Class Info] 156 | - Non-Cooperative Target Recognition (NCTR) - Narrow Beam Interleaved Search and Track [Class Info] 157 | - Continuous Tracking Capability 158 | - Track While Scan (TWS) 159 | - Periscope Search - Basic Capability 160 | - Periscope/Surface Search - Fine Range Resolution + Rapid Scan [1980+] 161 | - Periscope/Surface Search - Advanced Processing [2000+] 162 | - Moving Target Indicator (MTI) 163 | - Low Probability of Intercept (LPI) 164 | - Pulse-Only Radar 165 | - Pulse Doppler Radar (Full LDSD Capability) 166 | - Pulse Doppler Radar (Limited LDSD Capability) 167 | - Passive Electronically Scanned Array (PESA) 168 | - Active Electronically Scanned Array (AESA) 169 | - Can Classify Ground Targets (SAR) 170 | - Continuous Wave Illumination 171 | - Interrupted Continuous Wave Illumination 172 | - Frequency Agile 173 | - Cognitive EW 174 | - Generates AAW Fire-Control Data 175 | - Shallow Water Capable (Partial) 176 | - Shallow Water Capable (Full) [Classification Flag Required] 177 | 178 | - type: markdown 179 | attributes: 180 | value: | 181 | ## Frequencies 182 | 183 | - type: dropdown 184 | attributes: 185 | label: Search/Track Frequencies 186 | multiple: true 187 | options: 188 | - A Band (30-250 MHz) [Old P Band (HF)] 100-300 cm 189 | - B Band (250-500 MHz) [Old P Band (VHF)] 60-100 cm 190 | - C Band (500-1000 MHz) [Old L Band (UHF)] 60-30cm 191 | - D Band (1-2 GHz) [Old L Band] 15-30 cm 192 | - E Band (2-3 GHz) [Old S Band] 10-15 cm 193 | - F Band (3-4 GHz) [Old S Band] 7.5-10 cm 194 | - G Band (4-6 GHz) [Old C Band] 5-7.5 cm 195 | - H Band (6-8 GHz) [Old C Band] 3.75-5 cm 196 | - I Band (8-10 GHz) [Old X Band] 3-3.75 cm 197 | - J Band (10-20 GHz) [Old X Band] 1.5-3 cm 198 | - K Band (20-40 GHz) [Old Ku Band] 0.75-1.5 cm 199 | - L Band (40-60 GHz) [Old Ka Band] 5-7.5 mm 200 | - M Band (60-100 GHz) [Old V/W Band] 3-5 mm 201 | - LF Sonar (1-5 KHz, 3 KHz Center Frequency) 202 | - MF Sonar (5-10 KHz, 7.5 KHz Center Frequency) 203 | - HF Sonar (10-500 KHz, 20 KHz Center Frequency) 204 | - VLF Sonar (0-1000 Hz, 200 Hz Center Frequency) 205 | validations: 206 | required: true 207 | 208 | - type: input 209 | attributes: 210 | label: Lower Frequency (Hz) 211 | description: If you know the specific frequency range, provide the precise lower frequency. 212 | placeholder: ex. 9,210,000,000 213 | validations: 214 | required: false 215 | 216 | - type: input 217 | attributes: 218 | label: Upper Frequency (Hz) 219 | description: If you know the specific frequency range, provide the precise upper frequency. 220 | placeholder: ex. 9,490,000,000 221 | validations: 222 | required: false 223 | 224 | - type: markdown 225 | attributes: 226 | value: | 227 | ## Radar Stats 228 | 229 | If requesting a radar, fill out as much of the following information as you can. 230 | 231 | - type: input 232 | attributes: 233 | label: Scan Interval (s) 234 | description: How often does the radar scan a section of sky? On rotating radars this will be 60/RPM. 235 | placeholder: ex. 3 236 | validations: 237 | required: false 238 | 239 | - type: input 240 | attributes: 241 | label: Target Altitude (ft) 242 | description: How high/low can a target be and still be successfully detected by this radar? Specify AGL or ASL. 243 | placeholder: ex. 200ft AGL - 36000ft ASL 244 | validations: 245 | required: false 246 | 247 | - type: input 248 | attributes: 249 | label: Horizontal Beamwidth (deg) 250 | placeholder: ex. 0.70 251 | validations: 252 | required: false 253 | 254 | - type: input 255 | attributes: 256 | label: Vertical Beamwidth (deg) 257 | placeholder: ex. 25.00 258 | validations: 259 | required: false 260 | 261 | - type: input 262 | attributes: 263 | label: System Noise Level (dB) 264 | placeholder: ex. 3.5 265 | validations: 266 | required: false 267 | 268 | - type: input 269 | attributes: 270 | label: Processing Gain/Loss (dB) 271 | placeholder: ex. 32.5 272 | validations: 273 | required: false 274 | 275 | - type: input 276 | attributes: 277 | label: Peak Power (W) 278 | placeholder: ex. 300 279 | validations: 280 | required: false 281 | 282 | - type: input 283 | attributes: 284 | label: Pulse Width (μs) 285 | placeholder: ex. 1.00 286 | validations: 287 | required: false 288 | 289 | - type: input 290 | attributes: 291 | label: Blind Time (μs) 292 | placeholder: ex. 1.00 293 | validations: 294 | required: false 295 | 296 | - type: input 297 | attributes: 298 | label: PRF (Hz) 299 | placeholder: ex. 1700 300 | validations: 301 | required: false 302 | 303 | - type: markdown 304 | attributes: 305 | value: | 306 | ## Sonar Stats 307 | 308 | If requesting a sonar, fill out as much of the following information as you can. 309 | 310 | - type: input 311 | attributes: 312 | label: Source Level (dB) 313 | placeholder: ex. 150 314 | validations: 315 | required: false 316 | 317 | - type: input 318 | attributes: 319 | label: Pulse Length (ms) 320 | placeholder: ex. 60 321 | validations: 322 | required: false 323 | 324 | - type: input 325 | attributes: 326 | label: TASS/VDS Length (m) 327 | description: If the sonar is a TASS/VDS, how long is the cable? 328 | placeholder: ex. 200 329 | validations: 330 | required: false 331 | 332 | - type: input 333 | attributes: 334 | label: TASS/VDS Depth (m) 335 | description: If the sonar is a TASS/VDS, how deep/shallow can it be trailed? 336 | placeholder: ex. 20m - 300m 337 | validations: 338 | required: false 339 | 340 | - type: input 341 | attributes: 342 | label: Convergence Zones 343 | description: If known, how many convergence zones does the sonar create? 344 | placeholder: ex. 60 345 | validations: 346 | required: false 347 | 348 | - type: markdown 349 | attributes: 350 | value: | 351 | ## Final Touches 352 | 353 | - type: textarea 354 | attributes: 355 | label: Comments 356 | description: Is there anything else you want to tell us so we can more effectively model this sensor? 357 | validations: 358 | required: false 359 | 360 | - type: textarea 361 | attributes: 362 | label: Sources 363 | description: | 364 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 365 | 366 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 367 | validations: 368 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/22_NEW-WEAPON.yml: -------------------------------------------------------------------------------- 1 | name: New Weapon Request 2 | description: This form is used to request a new weapon. 3 | # title: "New Weapon: " 4 | labels: ["addition", "weapon"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for taking the time to request a new weapon. 13 | 14 | Please note that filing this form will ONLY result in the weapon itself being added, not necessarily any associated loadouts, mounts, etc. These should be requested separately. 15 | 16 | ### A Note on Requesting Subcomponents 17 | Subcomponents -- such as weapons and sensors -- are of little use without a host. While it is true that weapon records / sensors may be added to various platforms in the mission editor, a weapon/sensor that is not currently employed on any platform in the DB is rarely worth the time it takes to add. 18 | 19 | If the weapon/sensor *is* employed on another platform but not represented in the DB, it may be better to file an addition, update, or loadout request instead. If we need you to file a separate subcomponent request, we'll let you know. 20 | 21 | - type: dropdown 22 | attributes: 23 | label: DB Selector 24 | description: Is this for DB3K, CWDB, or both? 25 | multiple: false 26 | options: 27 | - DB3K 28 | - CWDB 29 | - Both 30 | validations: 31 | required: true 32 | 33 | - type: input 34 | attributes: 35 | label: Baseline 36 | description: | 37 | Is there is a weapon in the DB you recommend we start from? This is different from a "Copy Entry" in that most of its values will be changed, but we can use this to estimate anything we aren't sure of. 38 | 39 | For example, the AGM-88 is different enough from the older AGM-45 that we couldn't simply copy one to model the other -- but it'd be a fair starting point. 40 | placeholder: ex. 2530 41 | validations: 42 | required: false 43 | 44 | - type: markdown 45 | attributes: 46 | value: | 47 | ## Common Information 48 | 49 | - type: dropdown 50 | attributes: 51 | label: Hypothetical 52 | description: Is this a hypothetical weapon, i.e. one not yet or never placed in service? 53 | multiple: false 54 | options: 55 | - "Yes" 56 | - "No" 57 | validations: 58 | required: true 59 | 60 | - type: input 61 | attributes: 62 | label: Name 63 | description: Provide designation and name (where applicable). 64 | placeholder: ex. MM.38 Exocet Blk 1 65 | validations: 66 | required: true 67 | 68 | - type: markdown 69 | attributes: 70 | value: | 71 | ## Dimensions and Weights 72 | 73 | - type: input 74 | attributes: 75 | label: Length (m) 76 | placeholder: ex. 4.70 77 | validations: 78 | required: true 79 | 80 | - type: input 81 | attributes: 82 | label: Width/Span (m) 83 | placeholder: ex. 1.10 84 | validations: 85 | required: true 86 | 87 | - type: input 88 | attributes: 89 | label: Diameter (m) 90 | placeholder: ex. 0.35 91 | validations: 92 | required: true 93 | 94 | - type: input 95 | attributes: 96 | label: Weight (kg) 97 | placeholder: ex. 670 98 | validations: 99 | required: true 100 | 101 | - type: markdown 102 | attributes: 103 | value: | 104 | ## Engagement Characteristics 105 | 106 | - type: input 107 | attributes: 108 | label: Range (nm) 109 | placeholder: ex. 2.0-23.0 110 | validations: 111 | required: true 112 | 113 | - type: input 114 | attributes: 115 | label: Target Altitude / Depth (ft) 116 | description: How deep/high can a target be and still be successfully engaged by this weapon? Specify AGL or ASL (or provide both). 117 | placeholder: ex. 200ft AGL - 35000ft ASL 118 | validations: 119 | required: false 120 | 121 | - type: input 122 | attributes: 123 | label: Target Speed (kts) 124 | description: How slow/fast can a target be and still be successfully engaged by this weapon? 125 | placeholder: ex. 50kts - 2000kts 126 | validations: 127 | required: false 128 | 129 | - type: input 130 | attributes: 131 | label: Launch Altitude / Depth (ft) 132 | description: How deep/high can a shooter be and still employ this weapon? Specify AGL or ASL (or provide both). 133 | placeholder: ex. 200ft AGL - 35000ft ASL 134 | validations: 135 | required: false 136 | 137 | - type: input 138 | attributes: 139 | label: LaunchSpeed (kts) 140 | description: How slow/fast can a shooter be and still employ this weapon? 141 | placeholder: ex. 270kts - 650kts 142 | validations: 143 | required: false 144 | 145 | - type: markdown 146 | attributes: 147 | value: | 148 | ## Lethality 149 | 150 | - type: input 151 | attributes: 152 | label: Warhead 153 | description: What is the warhead weight and type? 154 | placeholder: ex. 165kg HE Blast/Frag 155 | validations: 156 | required: true 157 | 158 | - type: dropdown 159 | attributes: 160 | label: Targets 161 | description: Indicate which of the following are valid targets for this weapon. 162 | multiple: true 163 | options: 164 | - Aircraft 165 | - Helicopter 166 | - Missile 167 | - Satellite 168 | - C-RAM (Counter Rocket, Artillery and Mortar) 169 | - Surface Vessel 170 | - Submarine 171 | - Mine 172 | - Torpedo 173 | - Land Structure - Soft 174 | - Land Structure - Hardened 175 | - Runway 176 | - Radar 177 | - Mobile Target - Soft 178 | - Mobile Target - Hardened 179 | - Mobile Target - Personnel 180 | validations: 181 | required: true 182 | 183 | - type: input 184 | attributes: 185 | label: CEP (m) 186 | description: What is the Circular Error Probable for the weapon against targets on land/surface? 187 | placeholder: ex. 4 188 | validations: 189 | required: false 190 | 191 | - type: markdown 192 | attributes: 193 | value: | 194 | ## Sensors 195 | 196 | - type: textarea 197 | attributes: 198 | label: Sensors 199 | description: | 200 | List the weapon's sensors, placing each on a new line as in the example. Most weapons will have one or two for terminal guidance. 201 | 202 | If you have specific information about the seekers' capabilities, you can include it here. 203 | placeholder: | 204 | 1x Active Radar Seeker (~5nm Range) 205 | 1x IIR Seeker (2nd Gen) 206 | validations: 207 | required: true 208 | 209 | - type: markdown 210 | attributes: 211 | value: | 212 | ## Capabilities 213 | 214 | - type: dropdown 215 | attributes: 216 | label: Weapon Codes 217 | description: Indicate which (if any) of the following DB codes apply to this weapon. 218 | multiple: true 219 | options: 220 | - Illuminate at Launch 221 | - Terminal Illumination 222 | - Supports Buddy Illumination 223 | - Home On Jam (HOJ) 224 | - Anti-Air Stern Chase 225 | - Anti-Air Rear-Aspect 226 | - Anti-Air All-Aspect 227 | - Anti-Air Dogfight (High Off-Boresight) 228 | - No Diving Target 229 | - Capable vs Seaskimmer 230 | - ARH AAW - No HQ Track Required 231 | - C-RAM Capable 232 | - Lock-On After Launch (LOAL) - CEC-Capable 233 | - Lock-On After Launch (LOAL) 234 | - Terrain Following 235 | - Launcher Occupied During Guidance 236 | - ARM Target Memory 237 | - Loiter Capability 238 | - Loiter Capability (Parachute) 239 | - Search Pattern 240 | - Drive-Through Logic 241 | - Bearing-Only Launch (BOL) 242 | - Ballistic Missile or Rocket Booster 243 | - Weapon - INS Navigation 244 | - Weapon - INS w/ GNSS Navigation 245 | - Weapon - TERCOM Navigation 246 | - Weapon - Pre-Briefed Target Only 247 | - Weapon - Can Target Specific Subsystems 248 | - Terminal Maneuver - Pop-up 249 | - Terminal Maneuver - Zig-Zag 250 | - Terminal Maneuver - Random (Advanced) 251 | - Re-Attack Capability 252 | - Weapon Altitude Control Possible 253 | - Attitude Control - Aerodynamic Only 254 | - Attitude Control - Non-Aerodynamic Only 255 | - Attitude Control - Combined 256 | - Uses GPS 257 | - Uses GLONASS 258 | - Uses BeiDou/COMPASS 259 | - Uses NavIC/IRNSS 260 | - Mine - Contact Fuze 261 | - Mine - Magnetic Fuze, Simple Magnetic 262 | - Mine - Magnetic Fuze, Total-Field Magnetometer 263 | - Mine - Passive Acoustic Fuze, Broad-Band (Simple) 264 | - Mine - Passive Acoustic Fuze, Narrow-Band (Advanced) 265 | - Mine - Pressure Fuze 266 | - Mine - Seismic Fuze 267 | - Mine - Delay Counter 268 | - Mine - Arming Delay 269 | - Mine - Target Discrimination / Identification 270 | - Mine - Remote Controlled 271 | - Is Retarded Munition 272 | - Torpedo - Straight-Running 273 | - Torpedo - Wake Homing (WH) 274 | - Torpedo - Straight-Running & Time Detonation 275 | - Torpedo - Pattern-Running 276 | - Level Cruise Flight 277 | validations: 278 | required: false 279 | 280 | - type: markdown 281 | attributes: 282 | value: | 283 | ## Final Touches 284 | 285 | - type: textarea 286 | attributes: 287 | label: Comments 288 | description: Is there anything else you want to tell us so we can more effectively model this weapon? 289 | validations: 290 | required: false 291 | 292 | - type: textarea 293 | attributes: 294 | label: Sources 295 | description: | 296 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 297 | 298 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 299 | validations: 300 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/31_COPY-ENTRY.yml: -------------------------------------------------------------------------------- 1 | name: Copy Entry 2 | description: This form is used to request additions based on extant entries. 3 | # title: "Copy Entry: " 4 | labels: ["copy"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | This form can be used to request an addition when an identical base platform already exists in the DB. 13 | 14 | The intent is to avoid unnecessary data entry for platforms which are the same or similar to existing entries. For example, a UH-60 that the US sells to the Philippines is still a UH-60; we don't want you to have to spend time providing info as if it's a new aircraft. We know how big it is. 15 | 16 | As a rule of thumb: if the platform you're requesting has the same name as something in the DB, or involves tacking letters onto an existing designation, you're probably good to use this form. 17 | 18 | With that said, if anything has changed beyond the sensors or mounts/loadouts, you may need to file a new platform request. 19 | 20 | - type: dropdown 21 | attributes: 22 | label: DB Selector 23 | description: Is this for DB3K, CWDB, or both? If copying from one DB to the other, indicate only the destination DB. 24 | multiple: false 25 | options: 26 | - DB3K 27 | - CWDB 28 | - Both 29 | validations: 30 | required: true 31 | 32 | - type: markdown 33 | attributes: 34 | value: | 35 | ## Origin Info 36 | 37 | - type: input 38 | attributes: 39 | label: DBID to Copy 40 | description: Which DBID should be copied as a baseline? (Please preface the ID with its annex, as in the example.) Also, please try to use same-DB references wherever possible. If you must provide a cross-DB reference, indicate the source DB. 41 | placeholder: ex. Aircraft 4071 (CWDB) 42 | validations: 43 | required: true 44 | 45 | - type: markdown 46 | attributes: 47 | value: | 48 | ## Basic Information for New Entry 49 | 50 | - type: dropdown 51 | attributes: 52 | label: Hypothetical 53 | description: Is this copy to create a hypothetical platform, i.e. one not yet or never placed in service? 54 | multiple: false 55 | options: 56 | - "Yes" 57 | - "No" 58 | validations: 59 | required: true 60 | 61 | - type: input 62 | attributes: 63 | label: Name 64 | description: Provide new designation and name (where applicable). 65 | placeholder: ex. SF.260W Genet [Warrior] 66 | validations: 67 | required: true 68 | 69 | - type: input 70 | attributes: 71 | label: Country 72 | placeholder: ex. Zimbabwe 73 | validations: 74 | required: true 75 | 76 | - type: input 77 | attributes: 78 | label: Service 79 | placeholder: ex. Air Force 80 | validations: 81 | required: true 82 | 83 | - type: input 84 | attributes: 85 | label: In Commission 86 | description: When was this platform in service for the specified country? 87 | placeholder: ex. 1976-Present 88 | validations: 89 | required: false 90 | 91 | - type: input 92 | attributes: 93 | label: Number in Service 94 | description: If this platform was in limited service, how many were there? 95 | placeholder: ex. 12x, 2x Destroyed 1991 96 | validations: 97 | required: false 98 | 99 | - type: markdown 100 | attributes: 101 | value: | 102 | ## Adjustments 103 | 104 | - type: textarea 105 | attributes: 106 | label: Sensors 107 | description: | 108 | List any changes/additions to the platform's sensors, placing each on a new line as in the example. 109 | placeholder: | 110 | 1x ASELFLIR-300T replaced by CATS 111 | FCR removed 112 | validations: 113 | required: false 114 | 115 | - type: textarea 116 | attributes: 117 | label: Mounts 118 | description: | 119 | List any changes to the platform's mounts (i.e., weapons), placing each on a new line as in the example. For aircraft, this will include only non-removable weapons, e.g. cannon; missiles, bombs, etc. should be listed as loadout options. 120 | placeholder: | 121 | Exocet missiles removed 122 | 7.62mm MGs replaced w/ 12.7mm Typhoon RWS 123 | validations: 124 | required: false 125 | 126 | - type: textarea 127 | attributes: 128 | label: Loadout Options 129 | description: | 130 | If for an aircraft and specific loadouts are known, list them here. In addition / otherwise, please list the weapons that the aircraft can employ. 131 | placeholder: | 132 | - 12x AMM-1 Hybrid Guided Multipurpose Missiles 133 | - 12x Mk82 LDGB 134 | - 6x RMS-1 AShM 135 | - 4x UUM-7 Micro-Missile Pods (14x HMM-01/pod) 136 | 137 | Or combinations of the above. 138 | validations: 139 | required: false 140 | 141 | - type: textarea 142 | attributes: 143 | label: Other Changes 144 | description: Are there any other changes we should know about? 145 | validations: 146 | required: false 147 | 148 | - type: textarea 149 | attributes: 150 | label: Sources 151 | description: | 152 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 153 | 154 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 155 | validations: 156 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/32_UPDATE-REQUEST.yml: -------------------------------------------------------------------------------- 1 | name: Update/Correction Request 2 | description: This form is used to request edits to extant entries. 3 | # title: "Update: " 4 | labels: ["update"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for requesting an update to the DB. An "update" is generally filed to correct inaccurate information and can be anything from correcting a typo to replacing a platform's mounts. 13 | 14 | # If current entries are correct but changed/will change in a certain period (e.g., a ship's AShMs are upgraded), please file a "Copy Entry" request. 15 | 16 | - type: dropdown 17 | attributes: 18 | label: DB Selector 19 | description: Is this for DB3K, CWDB, or both? 20 | multiple: false 21 | options: 22 | - DB3K 23 | - CWDB 24 | - Both 25 | validations: 26 | required: true 27 | 28 | - type: markdown 29 | attributes: 30 | value: | 31 | ## Update Details 32 | 33 | - type: input 34 | attributes: 35 | label: Affected DBID(s) 36 | description: Which DBID(s) does this request apply to? (Please preface the ID(s) with their annex, as in the example.) 37 | placeholder: ex. Facility 1305, 1402 38 | validations: 39 | required: true 40 | 41 | - type: textarea 42 | attributes: 43 | label: Summary of Changes 44 | description: Describe what you'd like us to change in the listed entries. 45 | validations: 46 | required: true 47 | 48 | - type: textarea 49 | attributes: 50 | label: Sources 51 | description: | 52 | Please list all the sources you used to find the information you provided. For offline sources, provide title, author, and page (as applicable). 53 | 54 | We do check these. If we can't corroborate your information, we may provide replacement data from our own sources or discard your request entirely. 55 | validations: 56 | required: true -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/33_BUG-REPORT.yml: -------------------------------------------------------------------------------- 1 | name: Bug Report 2 | description: This form is for reporting critical bugs in the DB. 3 | # title: "Bug Report: " 4 | labels: ["update", "bug"] 5 | # assignees: 6 | # - octocat 7 | 8 | body: 9 | - type: markdown 10 | attributes: 11 | value: | 12 | Thank you for bringing our attention to a bug! This form is similar to the update request form, but will attract more attention from the devs. 13 | 14 | Only use this form for things which are actually *broken*: i.e., they don't work, or are so significantly screwed up that they make gameplay impossible. For example: a SAM site that can't target aircraft. 15 | 16 | Typos, inaccurate entries, etc. should be reported via a normal update request. 17 | 18 | - type: dropdown 19 | attributes: 20 | label: DB Selector 21 | description: Does this bug occur using DB3K or CWDB? 22 | multiple: false 23 | options: 24 | - DB3K 25 | - CWDB 26 | - Both 27 | validations: 28 | required: true 29 | 30 | - type: markdown 31 | attributes: 32 | value: | 33 | ## Report Details 34 | 35 | - type: input 36 | attributes: 37 | label: Affected DBID(s) 38 | description: Which DBID(s) are affected by this bug? (Please preface the ID with its annex, as in the example.) If the bug affects a wide array of units, a simple descriptor will suffice. 39 | placeholder: ex. Weapon 1305 40 | validations: 41 | required: true 42 | 43 | - type: textarea 44 | attributes: 45 | label: Description of Problem 46 | description: What seems to be the problem? 47 | placeholder: | 48 | Plane has zero fuel. 49 | validations: 50 | required: true 51 | 52 | - type: textarea 53 | attributes: 54 | label: Recommended Fix 55 | description: If it's obvious what needs to be done to fix the problem, let us know. 56 | placeholder: | 57 | Give it fuel. 58 | validations: 59 | required: false -------------------------------------------------------------------------------- /.github/labeler.yml: -------------------------------------------------------------------------------- 1 | # Add 'DB3K' label if DB Selector is set to 'DB3K' or "Both". 2 | DB3K: 3 | - '### DB Selector\n+(DB3K|Both)' 4 | 5 | # Add 'CWDB' label if DB Selector is set to 'CWDB' or "Both". 6 | CWDB: 7 | - '### DB Selector\n+(CWDB|Both)' 8 | 9 | # Add 'hypo' label if Hypothetical selector is set to 'Yes'. 10 | hypo: 11 | - '### Hypothetical\n+Yes' 12 | 13 | # Add respective annex labels to update/copy requests if Affected DBID / DBID to Copy field begins with key letters. 14 | aircraft: 15 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Aa](?:ir\w*|\/?[Cc]) *#?\d{0,4}' 16 | 17 | facility: 18 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ff]a\w* *#?\d{0,4}' 19 | 20 | ship: 21 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ss]hip|[Bb]oat *#?\d{0,4}' 22 | 23 | submarine: 24 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ss]u\w* *#?\d{0,4}' 25 | 26 | weapon: 27 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ww]e\w* *#?\d{0,4}' 28 | 29 | sensor: 30 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ss]e\w* *#?\d{0,4}' 31 | 32 | satellite: 33 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ss]a\w* *#?\d{0,4}' 34 | 35 | loadout: 36 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Ll]o\w* *#?\d{0,4}' 37 | 38 | groundunit: 39 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Gg]r\w* *#?\d{0,4}' 40 | 41 | mount: 42 | - '### (?:Affected DBID\(s\)|DBID to Copy)\n+(?:(?:[Cc][Ww])?[Dd][Bb](?:3[Kk])?)? *[Mm]o\w* *#?\d{0,4}' 43 | -------------------------------------------------------------------------------- /.github/workflows/issue-manager.yml: -------------------------------------------------------------------------------- 1 | name: Issue Manager 2 | 3 | on: 4 | schedule: 5 | - cron: "0 0 * * *" 6 | issue_comment: 7 | types: 8 | - created 9 | issues: 10 | types: 11 | - labeled 12 | workflow_dispatch: 13 | 14 | jobs: 15 | issue-manager: 16 | runs-on: ubuntu-latest 17 | steps: 18 | - uses: tiangolo/issue-manager@0.4.0 19 | with: 20 | token: ${{ secrets.GITHUB_TOKEN }} 21 | config: > 22 | { 23 | "question": { 24 | "delay": 1814000, 25 | "message": "Requested additional info was not provided within three weeks, so the issue was closed. But don't worry: if you provide info later, the ticket will be reopened!" 26 | } 27 | } -------------------------------------------------------------------------------- /.github/workflows/labeler.yml: -------------------------------------------------------------------------------- 1 | name: "Issue Labeler" 2 | 3 | on: 4 | issues: 5 | types: 6 | - opened 7 | 8 | jobs: 9 | triage: 10 | runs-on: ubuntu-latest 11 | steps: 12 | - uses: github/issue-labeler@v3.0 13 | with: 14 | repo-token: "${{ secrets.GITHUB_TOKEN }}" 15 | configuration-path: .github/labeler.yml 16 | # not-before: 2020-01-15T02:54:32Z 17 | enable-versioned-regex: 0 -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # CMO DB Development (Public) 2 | Welcome to the public request/issue tracker for the *Command: Modern Operations* database. 3 | 4 | This is an issue-only repository intended to replace the old "DB Request Threads" on the Matrix Games Forums. 5 | 6 | You can read more about why we opted to move to GitHub in [this post](https://www.matrixgames.com/forums/tm.asp?m=5144985). 7 | 8 | ## What Is This, And How Does It Work? 9 | Anyone wishing for changes to the DB can post their request here. 10 | 11 | Please note **this is one of two trackers used by the DB team**. (The other is private/internal.) Moreover, **handling tickets is only one part of our DB workflow**. Dev activity on this tracker will wax and wane as priorities shift; tickets will often be handled out-of-order in support of larger objectives. 12 | 13 | While it can be frustrating to see your carefully-researched ticket languishing while others are handled out-of-turn, remember everyone is working towards the same goal: a comprehensive, accurate, and up-to-date database. 14 | 15 | ## How Do I Contribute? 16 | Anybody interested in supporting development of the *Command* DB is welcome to contribute. You do not need development experience, knowledge of code/databases, or even to own *Command*. 17 | 18 | We recommend aspiring contributors first visit the [Discussions page](https://github.com/PygmalionOfCyprus/cmo-db-requests/discussions) and review the [FAQs](https://github.com/PygmalionOfCyprus/cmo-db-requests/discussions/4). 19 | 20 | When you're ready to submit your first issue: 21 | 22 | 1. Navigate to the ["Issues" page](https://github.com/PygmalionOfCyprus/cmo-db-requests/issues). 23 | 2. Click the "New Issue" button and select a template. If necessary, you can open a blank issue. 24 | 3. Provide as much information as you can. 25 | 4. Submit the issue. 26 | 27 | If you don't have a request in mind but still want to help, try sorting issues by the "help wanted" label! 28 | 29 | As this is an issue-only repository, contributors do not need to use forks, pull requests, etc. 30 | 31 | ## Contact & Questions 32 | 33 | Contributors are encouraged to post regarding this repository on the [Discussions page](https://github.com/PygmalionOfCyprus/cmo-db-requests/discussions). 34 | 35 | This does not replace the Matrix Games Forums and should not be used for general game discussion. -------------------------------------------------------------------------------- /forumpost.md: -------------------------------------------------------------------------------- 1 | We are extremely excited to introduce a new system for handling DB requests! 2 | 3 | From now on, we'd like to ask everyone to post their DB requests in the new [public issue tracker](https://github.com/PygmalionOfCyprus/cmo-db-requests). This replaces the old DB request threads. 4 | 5 | If you're not familiar with GitHub, don't worry. We've provided guidance that should help you get started, and will continue to update those materials as questions come in. 6 | 7 | ## Why Move to GitHub? 8 | As a rule of thumb, if a team is spending more time wrestling with their systems than working...it's probably time to replace the systems. 9 | 10 | The DB threads were especially problematic because they required each request to be manually copied into our internal trackers. This obviously ate up large chunks of time. 11 | 12 | Worse, with no way to guide submissions, we found a large number of the requests we were spending so much time to copy, sort, and triage were lacking critical information. In fact, of the 2,500 "open" issues clamoring for attention in our internal tracker, we estimated that less than 1/3 were actionable. And because we were tracking issues off-site, we had no way of following up with clarifying questions -- or even to let reporters know when their requests had been handled. 13 | 14 | We wanted to do better. 15 | 16 | At first (inspired partly by [this post](https://www.matrixgames.com/forums/tm.asp?m=5124696)) we considered several forum-based solutions. However, we determined that merely expanding the forums would not address our biggest problems with the legacy system. 17 | 18 | GitHub offered an alternative with numerous advantages: 19 | 20 | * It was a platform we were already using 21 | * We could easily coordinate across our internal and public trackers (no more manual copying!) 22 | * We could create "issue forms" and templates to guide submissions 23 | * We could use labels and milestones to categorize and prioritize work 24 | * We could automate labelling (and more!) to handle basic sorting, triage, etc. 25 | * Requests were "threaded," letting us communicate directly with reporters per-issue 26 | * People could easily track the status of their requests (or any issue they were interested in) 27 | * Community members could contribute to others' requests with comments, research, etc. 28 | 29 | GitHub's focus on open-source development also offered some tantalizing possibilities for community collaboration. For example, the ongoing [Review and Editing of Unit Descriptions](https://www.matrixgames.com/forums/tm.asp?m=5080875) could be handled as a branch on this (or a separate) repository, allowing users to make additions and edits before submitting a pull request for review by the project managers. But that's getting ahead of things! 30 | 31 | ## In Conclusion 32 | Changing long-running systems -- even flawed ones -- is disruptive and can be controversial. We hope you can see why we feel the advantages we stand to gain outweigh any short-term disruption. 33 | 34 | Although we don't see ourselves ever returning to the old method, this replacement should still be considered a beta program. There will inevitably be growing pains. We'd welcome any feedback, and ask for your patience as we make changes accordingly. 35 | 36 | We look forward to your contributions on the new tracker! --------------------------------------------------------------------------------