root/geardeflist/geardef
Back
Namespace:
Filename:
Content: id (Type: string) , name (Type: string) , concealability (Type: byte) ?, rating (Type: byte) ?, mass (Type: float) ?, price (Type: int) , legality (Type: string) , availability (Type: string) , index (Type: float) , page (Type: srsref) , category (Type: gearcategory) , ecu (Type: float) ?, grouping (Type: string) ?, plural (Type: string) ?, units (Type: string) ?, customization (Type: datatype) ? notes (Type: string) ?
Description: The geardef tag defines a standard peice of gear
from a rulebook. This schema does not describe a specific useage of a peice of gear,
merely the generic attributes of the item. Note that several other schema (e.g.
cyberdef) extend this schema.
id defines the unique identifier of this gear.name defines the displayed name of this item.concealability defines the Concealability Rating of the item, if any. If
this tag is not present, the item cannot be concealed.rating defines the rating of the item, if any.mass defines the mass of the item, in kilograms. If this tag is not present, the item
is assumed to have zero mass for game purposes.price defines the standard price, in nuyen, of the item.legality defines the legality code for the item.availability defines the availability for the itemindex defines the street index for the item.page defines the page reference for the item, using the
Shadowrun Reference Standardcategory defines the larger category of items to which this gear belongs.ecu defines the number of equipment capacity units (ECU) this item uses, if any.grouping, if present, defines a grouping that contains this item. This
allows a more customizable, un-typed categoriziation and is used in combination with
the category tag. For example, the Houndstooth line of body armor contains
a number of peices, each with different stastics. Each of these items would have
a category of "armor:designer", but can be distinctly grouped together
by setting all of their grouping tags to "Houndstooth".plural defines the plural form of this item. If not specified, the
plural form is considered to by the value of the name tag followed
by an 's'.units defines an optional descriptor for items that are sold in specific
sets, increments or measures (e.g. "dozen", "round", "MP", "liter", "dose", "month" etc.). If
not specified, the unit is assumed to be sold individually.customization defines the type of customization this item requires upon
purchase, if any. For example, when buying a skillsoft, the skill name (a string) must
be specified. If not present, the item is not customized in this way.notes defines any comments about the item that may be relevant.As mentioned above, the geardef is extended by a number of specialized
tags. Many types of equipment, however, are described using the generic geardef
tag. The geardef is used directly with the following category
settings:
030000 - ammunition030100 - ammunition:bullet030200 - ammunition:projectile090000 - skillsoft120000 - biotech130100 - electronics:surveillance130200 - electronics:countersurveillance130300 - electronics:security130400 - electronics:countersecurity130500 - electronics:communications130600 - electronics:personal140000 - gear140100 - gear:lifestyle140200 - gear:music140300 - gear:trideo140400 - gear:simsense150103 - matrix:cyberdeck:additions150104 - matrix:cyberdeck:components160000 - magical160100 - magical:focus160200 - magical:fetishCode Fragment
<xs:elementtype name="geardef">
<xs:model>
<xs:sequence>
<xs:element type="xs:string" name="id"/>
<xs:element type="xs:string" name="name"/>
<xs:element type="xs:byte" name="concealability" occurs="?"/>
<xs:element type="xs:float" name="mass" occurs="?"/>
<xs:element type="xs:int" name="price"/>
<xs:element type="xs:string" name="legality"/>
<xs:element type="xs:string" name="availability"/>
<xs:element type="xs:float" name="index"/>
<xs:element type="srsref" name="page"/>
<xs:element type="gearcategory" name="category"/>
<xs:element type="xs:float" name="ecu" occurs="?"/>
<xs:element type="xs:string" name="grouping" occurs="?"/>
<xs:element type="xs:string" name="plural" occurs="?"/>
<xs:element type="xs:string" name="units" occurs="?"/>
<xs:element type="datatype" name="customization" occurs="?"/>
<xs:element type="xs:string" name="notes"/>
</xs:sequence>
</xs:model>
</xs:elementtype>