HowTo:Make Weapons - Revision history

Tbeholder at 03:03, 5 February 2014

2014-02-05T03:03:05Z

Tbeholder at 01:26, 5 February 2014

2014-02-05T01:26:37Z

Tbeholder at 01:22, 5 February 2014

2014-02-05T01:22:31Z

Tbeholder at 01:00, 5 February 2014

2014-02-05T01:00:01Z

Augie.ben.doggie: [vega-bot] [replace] 1 instances of 'http://vegastrike.sourceforge.net/forums' for 'http://forums.vega-strike.org'

2013-01-08T21:29:49Z

[vega-bot] [replace] 1 instances of 'http://vegastrike.sourceforge.net/forums' for 'http://forums.vega-strike.org'

Turbo beholder at 17:13, 22 June 2011

2011-06-22T17:13:32Z

Turbo beholder at 05:48, 22 June 2011

2011-06-22T05:48:58Z

Turbo beholder at 18:53, 21 June 2011

2011-06-21T18:53:30Z

Turbo beholder at 15:02, 20 June 2011

2011-06-20T15:02:58Z

Turbo beholder at 15:01, 20 June 2011

2011-06-20T15:01:34Z

@@ Line 23: / Line 23: @@
 An entry starts with the weapon type. Valid values: <code>Beam</code>, <code>Bolt</code>, <code>Ball</code>, <code>Missile</code>.
-<<code>''Weapon_type''</code> '''Name'''="<code>name</code>" '''MountSize'''="<code>Mount_type_1 Mount_type_2 ...</code>" '''Role'''="<code>AI_Role_1 AI_Role_2 ... </code>" AntiRole="<code>AI_Role_1 AI_Role_2 ... </code>">
+<<code>''Weapon_type''</code> '''Name'''="<code>name</code>" '''MountSize'''="<code>Mount_type_1 Mount_type_2 ...</code>" '''Role'''="<code>AI_Role_1 AI_Role_2 ... </code>" '''AntiRole'''="<code>AI_Role_1 AI_Role_2 ... </code>">
 * <code>'''Name'''</code> [string] - Its name (duh), the same as used in <code>units.csv</code> for mount attributes.
 * <code>'''MountSize'''</code> - Mount size, to be checked against mount attributes in <code>units.csv</code>. Valid values currently are "light", "medium", "heavy", "capship-light", "capship-heavy", "special", "light-missile", "medium-missile", "heavy-missile", "light-capship-missile", "heavy-capship-missile", "special-missile", "autotracking".
-* <code>'''Role'''</code> [string] - ''Exclusive'' space-separated list of AI roles (Combat_Role of an unit, assigned in <code>units.csv</code> and used in data/ai) against which the weapon will be used. See [[HowTo:Make_Weapons#Weapon_and_AI|Weapon and AI]] below. Currently used only for Tractor (but not Heavy Tractor): <code>role="CARGO INERT"</code>. Empty list or absent field allows everything.
+* <code>'''Role'''</code> [string] - Space-separated list of AI roles (Combat_Role of an unit, assigned in <code>units.csv</code> and used in data/ai) against which the weapon will be used. ''Exclusive'', but empty list or absent field allows everything. Note that it's applied after - and thus added to - the restrictions of a carrying unit's own Role, and if the weapon launches an unit (missile), it will act upon its own Role only. See also [[HowTo:Make_Weapons#Weapon_and_AI|Weapon and AI]] below. Currently it's used only for Tractor (but not Heavy Tractor): <code>role="CARGO INERT"</code>.
-* <code>'''AntiRole'''</code> [string] - Matters only if <code>'''Role'''</code> is absent. The same, but gives AI roles against which the weapon will ''not'' be used, everything else is allowed.
+* <code>'''AntiRole'''</code> [string] - Used only if <code>'''Role'''</code> is absent. Works much the same way, but gives AI roles against which the weapon will ''not'' be used, everything else is allowed.
 ===Appearance===
@@ Line 48: / Line 48: @@
 ** <code>refire</code> - Rest time, in seconds, between firing.
 *** If game difficulty is > 0.98 or weapon name doesn't end on "_Computer". If it is, this rate is scaled, inversely proportional to difficulty value and using <code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''refire_difficutly_scaling'''</code>" variable (default=<code>3.0</code>, with 1 scaling to the given value).
 ** <code>locktime</code> - Time to lock on the target, in seconds. Could work with any weapon but is actually checked only for missiles, since it doesn't have much sense for most non-guided weapons.
@@ Line 80: / Line 81: @@
 ** <code>consumption</code> ''or'' <code>rate</code> - Energy requirement is per second.
 ** <code>stability</code> - Maximum continuous firing duration.
-** <code>refire</code>
+** <code>refire</code> - Does not depend on whether the weapon was fired for maximum duration or a single frame.
 ** <code>locktime</code> - purely decorative.
 * <code><'''Damage''' ... /></code>
@@ Line 97: / Line 98: @@
 ** <code>detonationrange</code> - N/A
 ** <code>volume</code> - Ammo volume is set per shot: if used, 1 unit of ammo is fully spent when the beam is fired, even if it's interrupted later.
-*** Works only if "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/ '''reduce_beam_ammo'''</code>" variable is set to "<code>true</code>" (default <code>false</code>). Currently the only beam with ammo is Jackhammer.
+*** Works only if "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''reduce_beam_ammo'''</code>" variable is set to "<code>true</code>" (default <code>false</code>). Currently the only beam with ammo is Jackhammer.
 ===Bolt===
@@ Line 137: / Line 138: @@
 * <code><'''Damage''' ... /></code>
 ** <code>rate</code> - Damage is given per shot.
-*** {{fixme}} Uses a complicated formula; at zero distance the damage is 2x this much, at <code>radialspeed</code> it's 1x.
+*** {{fixme}} Uses a complicated formula; at zero distance the damage is 2x this much, at <code>radialspeed</code> it's 1x, then fades out.
 ** <code>phasedamage</code> - Damage is given per shot.
 ** <code>longrange</code>
 * <code><'''Distance''' ... /></code>
@@ Line 147: / Line 147: @@
 ** <code>length</code> - N/A
 ** <code>pulsespeed</code> - N/A
-** <code>range</code> - It obviously haven't much practical sense for maneuverable ones, so what it really does is set self-destruct to Range/Speed and lets AI know at what range to use it.
+** <code>range</code> - It obviously haven't much practical sense for maneuverable ones, so what it really does is: sets self-destruct to Range/Speed and lets AI know at what range to use it.
 ** <code>detonationrange</code> -  {{fixme}} The maximum distance from a target at which the missile detonates, in meters.
-*** Negative values are used for drones.
+*** Negative values are used for interceptors/drones.
 ** <code>volume</code>
@@ Line 156: / Line 156: @@
 Missiles ''must'' have their own AI files, "unitname"+".xai" (see <code>data/ai/script/</code>). If this file is not found, this "missile" is launched as an interceptor unit instead.
-<code>'''Role'''</code> as described above may be used to prevent attempts to waste a heavy missile or bomb on targets both fast and unworthy, like missiles or interceptors. Generally it's a good idea to set the weapon corresponding to the missile's role behaviour set in <code>data/ai/VegaPriorities.csv</code> - then if it won't hunt the unit, AI won't launch it at this unit in the first place. If roles are pre-filtered correctly, <code>[[Manual:Config:Advanced:Variables#.22AI.22_section|AI]]/Firing/MissileProbability</code> may be set higher as NPC will not be inclined to waste missiles early on.
+<code>'''Role'''</code> as described above may be used to prevent attempts to waste a heavy missile or bomb on targets both fast and unworthy, like missiles or interceptors. Generally it's a good idea to set the weapon corresponding to the missile's role behaviour set in <code>data/ai/VegaPriorities.csv</code> - so that if it won't hunt the unit, AI doesn't launch it at this unit in the first place. If roles are correctly pre-filtered, <code>[[Manual:Config:Advanced:Variables#.22AI.22_section|AI]]/Firing/MissileProbability</code> may be set higher, since NPC will not waste missiles before they get to proper targets.
 ==Example 1: Beam Weapon==
@@ Line 191: / Line 191: @@
 After CSV split ([https://sourceforge.net/p/vegastrike/code/13666/ [r13666]]), weapon effect parameters still are in data/'''weapon_list.xml''', but upgrade stats are in data/units/'''weapons.csv''' and trade in data/parts/'''trade_equipment.csv'''; add a line with picture in data/units/'''units_description.csv''' like ones for existing weapons, and everything should be covered.
-# To have a custom mount model (visible when enabled by <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''draw_weapons'''</code> config variable), add it as mounts/mylaserbeam.bfxm (lower case) - this works exactly the same way as with ships and subunits (including [[HowTo:Add_LODs|LODs]]). It's a good idea to check the model's size on the smallest ship able to carry it and check the muzzle of a weapon other than beam by setting the speed very low.
+To have a custom mount model (visible when enabled by <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''draw_weapons'''</code> config variable), add it as mounts/mylaserbeam.bfxm (lower case) - this works exactly the same way as with ships and subunits (including [[HowTo:Add_LODs|LODs]]). It's a good idea to check the model's size on the smallest ship able to carry it and check the muzzle of a weapon other than beam by setting the speed very low.
 =See also=

@@ Line 26: / Line 26: @@
 * <code>'''Name'''</code> [string] - Its name (duh), the same as used in <code>units.csv</code> for mount attributes.
 * <code>'''MountSize'''</code> - Mount size, to be checked against mount attributes in <code>units.csv</code>. Valid values currently are "light", "medium", "heavy", "capship-light", "capship-heavy", "special", "light-missile", "medium-missile", "heavy-missile", "light-capship-missile", "heavy-capship-missile", "special-missile", "autotracking".
-* <code>'''Role'''</code> [string] - ''Exclusive'' space-separated list of AI roles (Combat_Role of an unit, aa set in <code>units.csv</code> and used in data/ai) against which the weapon will be used. Currently used only for Tractor (but not Heavy Tractor): <code>role="CARGO INERT"</code>. Empty (or absent) list allows everything. See [[HowTo:Make_Weapons#|Weapon and AI]].
+* <code>'''Role'''</code> [string] - ''Exclusive'' space-separated list of AI roles (Combat_Role of an unit, assigned in <code>units.csv</code> and used in data/ai) against which the weapon will be used. See [[HowTo:Make_Weapons#Weapon_and_AI|Weapon and AI]] below. Currently used only for Tractor (but not Heavy Tractor): <code>role="CARGO INERT"</code>. Empty list or absent field allows everything.
-* <code>'''AntiRole'''</code> [string] - Matters only if <code>'''Role'''</code> is absent. The same, but gives AI roles against which the weapon will ''not'' be used.
+* <code>'''AntiRole'''</code> [string] - Matters only if <code>'''Role'''</code> is absent. The same, but gives AI roles against which the weapon will ''not'' be used, everything else is allowed.
 ===Appearance===

@@ Line 26: / Line 26: @@
 * <code>'''Name'''</code> [string] - Its name (duh), the same as used in <code>units.csv</code> for mount attributes.
 * <code>'''MountSize'''</code> - Mount size, to be checked against mount attributes in <code>units.csv</code>. Valid values currently are "light", "medium", "heavy", "capship-light", "capship-heavy", "special", "light-missile", "medium-missile", "heavy-missile", "light-capship-missile", "heavy-capship-missile", "special-missile", "autotracking".
-* <code>'''Role'''</code> [string] - ''Exclusive'' space-separated list of AI roles (Combat_Role of an unit, aa set in <code>units.csv</code> and used in data/ai) against which the weapon will be used. Currently used only for Tractor (but not Heavy Tractor): <code>role="CARGO INERT"</code>. Empty (or absent) list allows everything.
+* <code>'''Role'''</code> [string] - ''Exclusive'' space-separated list of AI roles (Combat_Role of an unit, aa set in <code>units.csv</code> and used in data/ai) against which the weapon will be used. Currently used only for Tractor (but not Heavy Tractor): <code>role="CARGO INERT"</code>. Empty (or absent) list allows everything. See [[HowTo:Make_Weapons#|Weapon and AI]].
 * <code>'''AntiRole'''</code> [string] - Matters only if <code>'''Role'''</code> is absent. The same, but gives AI roles against which the weapon will ''not'' be used.
@@ Line 62: / Line 62: @@
 ** <code>speed</code> - Speed at which projectile or beam head travels linearly through space, in meters/second.
 *** If "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''gun_speed_adjusted_game_speed'''</code>" variable is set to "<code>true</code>" (default <code>false</code>), speeds are moderated (below 1000 raised, otherwise reduced) and adjusted using <code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''gun_speed'''</code>.
-** <code>radialspeed</code> - Speed at which bolt/beam reaches its full radius and full damage, in meters/second.
+** <code>radialspeed</code> - Speed at which bolt/beam reaches its full radius and full damage, in meters/second. For missiles, determines explosion fall-off profile.
-** <code>radius</code> - Beam radius, in meters
+** <code>radius</code> - Beam/bolt radius, in meters. For '''missile''', explosion cut-off radius, in meters (geometry should be given via unit mesh anyway).
 ** <code>length</code> - Has any effect only for '''bolt'''.
 ** <code>pulsespeed</code> - Controls visual wave effect. Used only for '''beam'''.
@@ Line 93: / Line 93: @@
 ** <code>length</code> - N/A
 ** <code>pulsespeed</code> - Controls visual wave effect in beam.
-*** E.g. for tractor beams it should be negative, so that the beam texture moved toward the weapon and not from it.
+*** E.g. for tractor beams it's negative, because the beam texture should move toward the weapon and not from it.
 ** <code>range</code>
 ** <code>detonationrange</code> - N/A
@@ Line 152: / Line 152: @@
 ** <code>volume</code>
-==Weapon AI's==
+==Weapon and AI==
 Missiles ''must'' have their own AI files, "unitname"+".xai" (see <code>data/ai/script/</code>). If this file is not found, this "missile" is launched as an interceptor unit instead.

@@ Line 137: / Line 137: @@
 * <code><'''Damage''' ... /></code>
 ** <code>rate</code> - Damage is given per shot.
-*** {{fixme}} Uses a complicated formula; it looks like at zero distance the damage is twice this much, but don't count on this.
+*** {{fixme}} Uses a complicated formula; at zero distance the damage is 2x this much, at <code>radialspeed</code> it's 1x.
 ** <code>phasedamage</code> - Damage is given per shot.
 *** {{fixme}} Currently non-lethal ("negative") phasedamage for missiles is ignored.
@@ Line 143: / Line 143: @@
 * <code><'''Distance''' ... /></code>
 ** <code>speed</code>
-** <code>radialspeed</code> - {{fixme}} Seems to be explosion profile: how damage falls off with distance.
+** <code>radialspeed</code> - {{fixme}} "radial multiplier", sets the explosion profile: at this distance explosion causes 1x nominal damage and the fall-off function changes.
-** <code>radius</code> - {{fixme}} Seems to be the explosion radius, in meters.
+** <code>radius</code> - {{fixme}} Explosion radius, in meters. It doesn't affect the fall-off profile, beyond this point damage is simply not calculated.
 ** <code>length</code> - N/A
 ** <code>pulsespeed</code> - N/A
-** <code>range</code> - It obviously haven't much practical sense for maneuverable ones, so missiles have self-destruct is set to Range/Speed instead.
+** <code>range</code> - It obviously haven't much practical sense for maneuverable ones, so what it really does is set self-destruct to Range/Speed and lets AI know at what range to use it.
 ** <code>detonationrange</code> -  {{fixme}} The maximum distance from a target at which the missile detonates, in meters.
 *** Negative values are used for drones.
@@ Line 154: / Line 154: @@
 ==Weapon AI's==
-Missiles ''must'' have their own AI files, "name"+".xai" (see <code>data/ai/script/</code>). If this file is not found, this "missile" is launched as an interceptor unit instead.
+Missiles ''must'' have their own AI files, "unitname"+".xai" (see <code>data/ai/script/</code>). If this file is not found, this "missile" is launched as an interceptor unit instead.
-<code>'''Role'''</code> as described above may be used to prevent attempts to waste a heavy missile or bomb on targets both fast and unworthy, like missiles or interceptors. Generally it's a good idea to set the weapon corresponding to the missile's role behaviour set in <code>data/ai/VegaPriorities.csv</code> - if it won't hunt the unit, don't launch it in the first place. In this case <code>[[Manual:Config:Advanced:Variables#.22AI.22_section|AI]]/Firing/MissileProbability</code> may be set higher.
+<code>'''Role'''</code> as described above may be used to prevent attempts to waste a heavy missile or bomb on targets both fast and unworthy, like missiles or interceptors. Generally it's a good idea to set the weapon corresponding to the missile's role behaviour set in <code>data/ai/VegaPriorities.csv</code> - then if it won't hunt the unit, AI won't launch it at this unit in the first place. If roles are pre-filtered correctly, <code>[[Manual:Config:Advanced:Variables#.22AI.22_section|AI]]/Firing/MissileProbability</code> may be set higher as NPC will not be inclined to waste missiles early on.
 ==Example 1: Beam Weapon==
@@ Line 179: / Line 179: @@
 =Creating a weapon upgrade=
-[[prestidigitator]] documented his steps to create new weapons in a [http://forums.vega-strike.org/viewtopic.php?t=8732 forum post].  Here it is:
+[[prestidigitator]] documented his steps to create new weapons in a [http://forums.vega-strike.org/viewtopic.php?t=8732 forum post].  Here's the part that isn't obsolete yet:
+----
 Here is what I have done:
 # '''weapon_list.xml''': Copied the entire <Beam name="LaserBeam' ...> node to the end of the file (just before the </WEAPONS> end tag), changed the name from "LaserBeam" to "MyLaserBeam", and modified the values to be what I wanted (I left the "mountsize" attribute as "light").
 # '''master_part_list.csv''': Copied the line starting with "laser_beam" to the end of the file and changed "laser_beam" to "my_laser_beam".
 # '''units/units.csv''': Copied the line starting with "laser_beam__upgrades" to the end of the file, changed "laser_beam__upgrades" to "my_laser_beam__upgrades", changed "./factions/upgrades/laser_beam" to "./factions/upgrades/my_laser_beam", changed the second "laser_beam" to "my_laser_beam", and finally changed the "LaserBeam" to "MyLaserBeam".
-# '''units/factions/upgrades/''': Copied the "laser_beam/laser_beam" file to "my_laser_beam/my_laser_beam" and changed the "weapon" attribute of the <mount> node from "LaserBeam" to "MyLaserBeam".
+[...]
 There's an ordering problem. I moved all the additions to immediately after those entries for the laser beam, and it worked.
 So, I guess if you are trying to do this, consider my steps above to be a mini-HowTo, with the caveat that you should be careful about WHERE in the files you add things.
 # To have a custom mount model (visible when enabled by <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''draw_weapons'''</code> config variable), add it as mounts/mylaserbeam.bfxm (lower case) - this works exactly the same way as with ships and subunits (including [[HowTo:Add_LODs|LODs]]). It's a good idea to check the model's size on the smallest ship able to carry it and check the muzzle of a weapon other than beam by setting the speed very low.

@@ Line 179: / Line 179: @@
 =Creating a weapon upgrade=
-[[prestidigitator]] documented his steps to create new weapons in a [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=8732 forum post].  Here it is:
+[[prestidigitator]] documented his steps to create new weapons in a [http://forums.vega-strike.org/viewtopic.php?t=8732 forum post].  Here it is:
 You will need to create an upgrade file for this weapon that appears in [[master_parts_list.csv]] as well as [[units.csv]].

@@ Line 21: / Line 21: @@
 ===General Properties===
 <<code>''Weapon_type''</code> '''Name'''="<code>name</code>" '''MountSize'''="<code>Mount_type_1 Mount_type_2 ...</code>" '''Role'''="<code>AI_Role_1 AI_Role_2 ... </code>" AntiRole="<code>AI_Role_1 AI_Role_2 ... </code>">
 * <code>'''Name'''</code> [string] - Its name (duh), the same as used in <code>units.csv</code> for mount attributes.
 * <code>'''MountSize'''</code> - Mount size, to be checked against mount attributes in <code>units.csv</code>. Valid values currently are "light", "medium", "heavy", "capship-light", "capship-heavy", "special", "light-missile", "medium-missile", "heavy-missile", "light-capship-missile", "heavy-capship-missile", "special-missile", "autotracking".
@@ Line 30: / Line 30: @@
 ===Appearance===
 <code><'''Appearance''' ... /></code>
 * <code>file</code> [string/file] Texture file name.
 * <code>soundmp3</code> [string/file] Sound file.
 * <code>soundwav</code> [string/file] Sound file.
-* <code>OffsetX</code> <code>OffsetY</code> <code>OffsetZ</code> [float] - {{fixme}} Offset of the muzzle from the mount's coordinates? Offset of the texture?
+* <code>OffsetX</code> <code>OffsetY</code> <code>OffsetZ</code> [float] - Offset of the muzzle from the mount's coordinates, i.e. location of the weapon model's muzzle. Affected by config variables <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''weapon_xyscale'''</code> and <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''weapon_zscale'''</code>.
 * <code>r</code> <code>g</code> <code>b</code> <code>a</code> [float] [0.0 - 1.0] - Color components (with transparency) of the texture.
 ** E.g.: Tractor and Repulsor use the same texture, but different colors.
@@ Line 41: / Line 42: @@
 ===Energy===
 * <code><'''Energy''' ... /></code>
 ** <code>consumption</code> ''or'' <code>rate</code> - Energy requirement, in units of 100s of MJ. Depending on the weapon type, per second or per shot.
@@ Line 56: / Line 58: @@
 ===Distance===
 * <code><'''Distance''' ... /></code>
 ** <code>speed</code> - Speed at which projectile or beam head travels linearly through space, in meters/second.
@@ Line 72: / Line 75: @@
 ===Beam===
 <code><'''Beam''' ... ></code>
 * <code>'''Energy'''</code>
@@ Line 96: / Line 100: @@
 ===Bolt===
 <code><'''Bolt''' ... ></code>
 * <code><'''Energy''' ... /></code>
 ** <code>rate</code> - Energy requirement is per shot.
@@ Line 118: / Line 122: @@
 ===Ball===
 Mostly similar to Bolt, but is spherical, so there's one difference.
 <code><'''ball''' ... ></code>
 * <code><'''Distance''' ... /></code>
@@ Line 123: / Line 128: @@
 ===Missile===
 <code><'''missile''' ... ></code>
 * <code><'''Energy''' ... /></code>
@@ Line 186: / Line 192: @@
 So, I guess if you are trying to do this, consider my steps above to be a mini-HowTo, with the caveat that you should be careful about WHERE in the files you add things.
-# To have a custom mount model (visible when enabled by <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''draw_weapons'''</code> config variable), add it as mounts/mylaserbeam.bfxm (lower case) - this works exactly the same way as with ships and subunits, including [[HowTo:Add_LODs|LODs]]. It's a good idea to check the model's size on the smallest ship able to carry it.
+# To have a custom mount model (visible when enabled by <code>[[Manual:Config:Advanced:Variables#.22graphics.22_section|graphics]]/'''draw_weapons'''</code> config variable), add it as mounts/mylaserbeam.bfxm (lower case) - this works exactly the same way as with ships and subunits (including [[HowTo:Add_LODs|LODs]]). It's a good idea to check the model's size on the smallest ship able to carry it and check the muzzle of a weapon other than beam by setting the speed very low.
 =See also=

@@ Line 10: / Line 10: @@
 Weapon descriptions are stored in the '''[http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/vegastrike/data4.x/weapon_list.xml?rev=HEAD&content-type=text/vnd.viewcvs-markup weapon_list.xml]''' in the data directory.
-Weapons are classified as {{fixme}} ''DIFFERENCES BETWEEN CATEGORIES''
+Weapons are classified as
 * Beam
 * Bolt
@@ Line 16: / Line 16: @@
 * Missile
-If more than one is given as <code>property1</code> ''or'' <code>property1</code> this means, that they are both read, do the same ''and the latter synonymous property overwrites the former''(!).
+If more than one is given as <code>property1</code> ''or'' <code>property2</code> this means, that they are both read, do the same ''and the latter synonymous property overwrites the former''(!).
 ==Weapon XML Schema==
 {{fixme}} ''ADD DESCRIPTIONS TO SCHEMA''
 ===General Properties===
-<<code>Weapon_type</code> '''name'''="<code>name</code>" '''MountSize'''="<code>Mount_type_1 Mount_type_2 [string]</code>" '''role'''="<code>AI_Role_1 AI_Role_2 ... [string]</code>" antirole="<code>AI_Role_1 AI_Role_2 ... [string]</code>">
+<<code>''Weapon_type''</code> '''Name'''="<code>name</code>" '''MountSize'''="<code>Mount_type_1 Mount_type_2 ...</code>" '''Role'''="<code>AI_Role_1 AI_Role_2 ... </code>" AntiRole="<code>AI_Role_1 AI_Role_2 ... </code>">
-An entry starts with the weapon type. Valid values: <code>Beam</code>, <code>Ball</code>, <code>Bolt</code>, <code>Missile</code>.
+An entry starts with the weapon type. Valid values: <code>Beam</code>, <code>Bolt</code>, <code>Ball</code>, <code>Missile</code>.
 * <code>'''Name'''</code> [string] - Its name (duh), the same as used in <code>units.csv</code> for mount attributes.
 * <code>'''MountSize'''</code> - Mount size, to be checked against mount attributes in <code>units.csv</code>. Valid values currently are "light", "medium", "heavy", "capship-light", "capship-heavy", "special", "light-missile", "medium-missile", "heavy-missile", "light-capship-missile", "heavy-capship-missile", "special-missile", "autotracking".
@@ Line 45: / Line 45: @@
 ** <code>stability</code> - Maximum continuous firing duration. Used only for '''beam'''s.
 ** <code>refire</code> - Rest time, in seconds, between firing.
-*** If game difficulty is > 0.98 or weapon name doesn't end on "_Computer". If it is, this rate is scaled, inversely proportional to difficulty value and using physics/<code>refire_difficutly_scaling</code>" variable (default=<code>3.0</code>, with 1 scaling to the given value).
+*** If game difficulty is > 0.98 or weapon name doesn't end on "_Computer". If it is, this rate is scaled, inversely proportional to difficulty value and using <code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''refire_difficutly_scaling'''</code>" variable (default=<code>3.0</code>, with 1 scaling to the given value).
 ** <code>locktime</code> - Time to lock on the target, in seconds. Could work with any weapon but is actually checked only for missiles, since it doesn't have much sense for most non-guided weapons.
@@ Line 58: / Line 58: @@
 * <code><'''Distance''' ... /></code>
 ** <code>speed</code> - Speed at which projectile or beam head travels linearly through space, in meters/second.
-*** If "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/ '''gun_speed_adjusted_game_speed'''</code>" variable is set to "<code>true</code>" (default <code>false</code>), speeds are moderated (below 1000 raised, otherwise reduced) and adjusted using <code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/ '''gun_speed'''</code>.
+*** If "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''gun_speed_adjusted_game_speed'''</code>" variable is set to "<code>true</code>" (default <code>false</code>), speeds are moderated (below 1000 raised, otherwise reduced) and adjusted using <code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''gun_speed'''</code>.
 ** <code>radialspeed</code> - Speed at which bolt/beam reaches its full radius and full damage, in meters/second.
 ** <code>radius</code> - Beam radius, in meters
@@ Line 64: / Line 64: @@
 ** <code>pulsespeed</code> - Controls visual wave effect. Used only for '''beam'''.
 ** <code>range</code> - Max damaging range, in meters.
-*** "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/ '''gun_speed_adjusted_game_speed''' and <code>'''gun_speed'''</code> (see above) control ranges adjustment as well.
+*** "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''gun_speed_adjusted_game_speed'''</code> and <code>'''gun_speed'''</code> (see above) control ranges adjustment as well.
 ** <code>detonationrange</code> - The maximum distance from a target at which the missile detonates, in meters. '''Missile''' only.
 ** <code>volume</code> - ammo volume (for one shot), in meters<sup>3</sup>.
-*** For beams, works only if "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/ '''reduce_beam_ammo'''</code>" variable is set to "<code>true</code>" (default <code>false</code>).
+*** For beams, works only if "<code>[[Manual:Config:Advanced:Variables#.22Physics.22_section|physics]]/'''reduce_beam_ammo'''</code>" variable is set to "<code>true</code>" (default <code>false</code>).
 ==By weapon type==