The weapon data in <samp>Data/Weapons</samp> consists of a string → model lookup, where...
The weapon data in <samp>Data/Weapons</samp> consists of a string → model lookup, where...
−
* The key is the unqualified [[#Custom items|item ID]] for the weapon.
+
* The key is the unqualified [[Modding:Common_data_field_types#Item_ID|item ID]] for the weapon.
* The value is model with the fields listed below.
* The value is model with the fields listed below.
Line 1,529:
Line 1,529:
|-
|-
| <samp>CustomFields</samp>
| <samp>CustomFields</samp>
−
| The [[#Custom data fields|custom fields]] for this entry.
+
| The [[Modding:Common_data_field_types#Custom_fields|custom fields]] for this entry.
|}
|}
Weapons have a hardcoded category of -98 (<samp>Object.weaponCategory</samp>).
Weapons have a hardcoded category of -98 (<samp>Object.weaponCategory</samp>).
Line 1,541:
Line 1,541:
<ol>
<ol>
−
<li>Match weapons whose minimum mine level ([[#Format|field 10]]) is less than the current mine level.</li>
+
<li>Match weapons whose [[#Game logic|minimum mine level]] is less than the current mine level.</li>
−
<li>From that list, match weapons with a probability check based on the gap between the base mine level ([[#Format|field 9]]) and current mine level. The probability is a bell curve centered on the base mine level:
+
<li>From that list, match weapons with a probability check based on the gap between the [[#Game logic|base mine level]] and current mine level. The probability is a bell curve centered on the base mine level: