tmf:assigngear

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
tmf:assigngear [2020/07/04 19:24] – [Switching faction configs] snipperstmf:assigngear [2025/08/03 14:24] (current) – external edit 127.0.0.1
Line 49: Line 49:
 </code> </code>
  
-   For example:+For example:
  
 <code cpp> <code cpp>
Line 55: Line 55:
 </code> </code>
  
-   Here we have an array property called linkedItems that consists of 3 elements "ItemMap", "ItemCompass" and "ItemWatch".+Here we have an array property called linkedItems that consists of 3 elements "ItemMap", "ItemCompass" and "ItemWatch".
  
 **Class Inheritance** **Class Inheritance**
Line 67: Line 67:
 </code> </code>
  
-   Class g is still the same as r except the displayName has now been changed. This is useful for making variations of a given loadout; for example, often the only difference between a Grenadier and a Rifleman (g and r, respectively) is the primaryWeapon and the addition of launcher grenades:+Class g is still the same as r except the displayName has now been changed. This is useful for making variations of a given loadout; for example, often the only difference between a Grenadier and a Rifleman (g and r, respectively) is the primaryWeapon and the addition of launcher grenades:
  
 <code cpp> <code cpp>
Line 142: Line 142:
 </code> </code>
  
-   It's recommended to paste the Virtual Arsenal export into an empty text file besides the config; From there, you can find the classnames of the items you wish to use and paste them into the appropriate arrays in the faction config.+It's recommended to paste the Virtual Arsenal export into an empty text file besides the config; From there, you can find the classnames of the items you wish to use and paste them into the appropriate arrays in the faction config.
  
  
  • tmf/assigngear.1593890679.txt.gz
  • Last modified: 2025/08/04 06:49
  • (external edit)