Rarity Impacts the availability of this wing in loot drops. See also: CampaignPlugin.pickFleetInflater(). Instead, it just picks a couple of the available fighters for each autofit category.Ĭom.fs. is a good place to look for the details if you want specific behavior with regard to rarity etc, writing a custom one is probably the way to go. there's no "Talon, but worse" and "Talon, but better" etc progression for each kind of fighter, so that didn't work very well. For fighters, this isn't the case - there aren't enough fighters, i.e. Tier According to Alex For weapons, higher tier means a lower chance of being available. The hist1t, hist2t, and hist3t tag means the historian can tell the player about the location of a blueprint with this weapon. no_sell: Prevents markets from selling the wing.no_drop: Prevents from being salvaged or recovered (for built-in wings).rd_force_extra_craft (defunct): Allow Reserve Deployment to deploy extra wings when used (this used to be placed on bombers when the system did not allow bombers).rd_no_extra_craft: prevents Reserve Deployment from deploying extra extra wings when used.independent_of_carrier - combat won't end when only these are left on the field.attack_at_an_angle - aim to pass near target instead of directly over it, based on weapon range.match_leader_facing - wing members will not face towards target but will match wing leader.wingmen_no_swarm - wing members will keep their position in the wing on reaching target.leader_no_swarm - leader will start a new attack run on reaching target.rapid_reform - lagging wing members catch up more quickly.Tags help with how the fighter operate AI-wise: rare_bp (will appear as a standalone blueprint).base_bp (known to all factions, including player at start of game).Tags also help control which factions know a weapon and which blueprint packages it appears in. There are tags that categorize the wings into 3 categories, this is just for UI display: drone: This is used for autofit purposes if the variant has a drone wing, it will prefer to use wings with this drone tag.auto_fighter: Allows ships with Automated Ship to equip these wings. These are the tags that classify that the wings regarding automated ships. The vanilla groupings, where x is replaced with a number, are: Autofit would prefer higher numbers in the same grouping first and upgrade if possible. Primarily used by the autofit system to locate similar replacement weapons by providing a tiered grouping. For example the broadsword variant file broadsword_Fighter.variant contains element variantId with value "broadsword_Fighter". Must match the variantId element within a. String variant Internal variant ID for this fighter. For example the id of the broadsword fighter in ship_data.csv is "broadsword" so the id in the wing_data.csv is "broadsword_wing". Must match the id field in the ship_data.csv entry with an appended "_wing". Elements id Internal ID used to reference this fighter.
0 Comments
Leave a Reply. |