Orion Pirate template and generation of ships - Revision history

Firesoul: moved OP+: Orion Pirate template and generation of ships to Orion Pirate template and generation of ships: simplified title

2011-05-04T08:08:37Z

moved OP+: Orion Pirate template and generation of ships to Orion Pirate template and generation of ships: simplified title

Firesoul: /* Introduction */

2011-05-04T02:22:30Z

‎Introduction

Firesoul: /* Option Mount weapon data */

2011-05-04T02:01:01Z

‎Option Mount weapon data

Firesoul: /* shiplist template file changes */

2011-05-04T01:59:53Z

‎shiplist template file changes

Firesoul: /* Races templating */

2011-05-04T01:59:40Z

‎Races templating

Firesoul: /* Process */

2011-05-04T01:59:26Z

‎Process

Firesoul: /* shiplist template file changes */

2011-05-04T01:59:15Z

‎shiplist template file changes

Firesoul: /* shiplist template file changes */

2011-05-04T01:59:05Z

‎shiplist template file changes

Firesoul: /* shiplist template file changes */

2011-05-04T01:58:50Z

‎shiplist template file changes

Firesoul: /* Introduction */

2011-05-04T01:58:13Z

‎Introduction

@@ Line 1: / Line 1: @@
 === Introduction ===
@@ Line 5: / Line 7: @@
 The plan: to create templates based on the SFB SSDs where the option mounts are clearly marked, and coded in each item's cost, effect, etc. I will effectively ''generate'' the pirates from data entered. The pirate templates will be accurate, and the many many ships generated from each template will also be, with the correct BPV adjustment, weapons and systems.
 === Process ===

@@ Line 64: / Line 64: @@
 * ships with PFs are in the OrionTigerHeart race. (T-)
 ** this is why sometimes you'll see 2 versions of the same ship: with fighters or with PFs.
 === Option Mount weapon data ===
 The option mounts data (Annexes #8B and #8H) is coded in and ready to be used.
@@ Line 109: / Line 112: @@
 The following data points are coded:
 * '''weapon''': the actual SFC weapon for use in the shiplist
 ** this may be different than the name in the entry. For example, there's 2 Disruptor-30 entries: Dis3 and Dis3X. The biggest difference here is that Dis3X is for advanced technology ships, and has a minimum sizeclass of 4 (instead of 3).
@@ Line 128: / Line 132: @@
 ** this is for DroG and DroGX entries.
 ** if undefined, assume default of 0 (no)
 example code:
 <pre>
    "PLaS_no_swivel" => {
@@ Line 147: / Line 153: @@
    },
 </pre>
 ==== Annex 8B Systems  (systems installed into Orion weapon option mounts) ====
 '''List of valid systems that work with standard Orion Options:'''
 * APR
 * AuxControl
@@ Line 180: / Line 188: @@
 * add_boarding_parties: used if adding Barracks. Tells the script to increase the # of marines.
 ** Default is 0.
 example code:
 <pre>
    "AuxControl" => {
@@ Line 192: / Line 200: @@
    },
 </pre>
 Usage example: (APR)
 <pre>
    "X-HDW3" => { 'template' => 'X-HDW', 'race' => 'OrionOrion',
@@ Line 207: / Line 217: @@
    }, },
 </pre>
 ==== Annex 8H Weapons (HDW Weapon Option Mounts data) ====
 '''List of valid HDW rear-facing weapons'''
 * ADD12
 * ADD6
@@ Line 235: / Line 247: @@
 The following data points are coded:
 * '''weapon''': the actual SFC weapon for use in the shiplist
 ** this may be different than the name in the entry. For example, there's 2 Disruptor-30 entries: Dis3 and Dis3X. The biggest difference here is that Dis3X is for advanced technology ships, and has a minimum sizeclass of 4 (instead of 3).
@@ Line 255: / Line 268: @@
 ** If not defined, default is 0.
 * '''hydran_escort_only''': For PhG -- can only be installed onto Hydran escort
 example code:
 <pre>
    "Dis2" => { 'weapon' => 'Dis2', 'BPV' => 4, 'is_heavy' => 1, },
    "Dis3X" => { 'weapon' => 'Dis3', 'BPV' => 5, 'is_heavy' => 1, 'xtech' => 1, },
 </pre>
 ==== Annex 8H Systems (HDW NWO Mounts data) ====
 '''List of valid Non-Weapon options:'''
 * AuxControl
 * Barracks
@@ Line 283: / Line 300: @@
 The following data points are coded:
 * '''BPV''': the BPV adjustment for buying this weapon for your ship
 ** this value is based on the Annex8B data, but may have been modified and adapted for SFC
@@ Line 295: / Line 313: @@
 * '''add_shuttle_base''': Add to the basic number of shuttles. (NOT CURRENTLY USED)
 ** default is 0.
 example code:
 <pre>
    "AuxControl" => {

@@ Line 50: / Line 50: @@
 * OrionCamboro
 ** 70% Mirak/Kzinti, 20% Fed and Lyran
 === shiplist template file changes ===

@@ Line 17: / Line 17: @@
 ** use Heavy (X) Photon for HDW rear weapons
 * add up the BPV except for the weapons and save the ship
 === Races templating ===
 * use race Orion for generic pirates
 * use OrionOrion for fighter carriers
 * use OrionTigerHeart as race for PFTs
 ==== Orion Weapons sources ====
@@ Line 46: / Line 50: @@
 * OrionCamboro
 ** 70% Mirak/Kzinti, 20% Fed and Lyran
 === shiplist template file changes ===

@@ Line 5: / Line 5: @@
 The plan: to create templates based on the SFB SSDs where the option mounts are clearly marked, and coded in each item's cost, effect, etc. I will effectively ''generate'' the pirates from data entered. The pirate templates will be accurate, and the many many ships generated from each template will also be, with the correct BPV adjustment, weapons and systems.
 === Process ===
 * create a template shiplist file for pirates.
 * set up placeholders for weapon option mounts

← Older revision		Revision as of 01:58, 4 May 2011
Line 5:		Line 5:

	The plan: to create templates based on the SFB SSDs where the option mounts are clearly marked, and coded in each item's cost, effect, etc. I will effectively ''generate'' the pirates from data entered. The pirate templates will be accurate, and the many many ships generated from each template will also be, with the correct BPV adjustment, weapons and systems.		The plan: to create templates based on the SFB SSDs where the option mounts are clearly marked, and coded in each item's cost, effect, etc. I will effectively ''generate'' the pirates from data entered. The pirate templates will be accurate, and the many many ships generated from each template will also be, with the correct BPV adjustment, weapons and systems.
−

	=== Process ===		=== Process ===