| Line 398: |
Line 398: |
| | | | |
| | Hardware based add-ons are peripherals and function differently than software add-ons in that other companies can make them for each other's hardware and a single customer can buy the same peripheral several times. | | Hardware based add-ons are peripherals and function differently than software add-ons in that other companies can make them for each other's hardware and a single customer can buy the same peripheral several times. |
| | + | |
| | + | ==== Values ==== |
| | + | {|class="wikitable" |
| | + | |Name |
| | + | |This is the name of the add-on |
| | + | |- |
| | + | |Description |
| | + | |Currently not shown anywhere |
| | + | |- |
| | + | |Unlock |
| | + | |Which year this software category will unlock, e.g. <Unlock>1995</Unlock> |
| | + | |- |
| | + | |Categories |
| | + | |Optional list of software categories that supports this add-on |
| | + | |- |
| | + | |OptimalDevTime |
| | + | |This optimal amount of time it takes to develop, to maximize interest, works the same as for software types |
| | + | |- |
| | + | |Retention |
| | + | |How long products keep their interest after release and how long people will use the product in months. |
| | + | |- |
| | + | |Forced |
| | + | |Whether you have to develop this add-on when develop the main product, e.g. joysticks for consoles. Only valid for peripheral add-ons |
| | + | |- |
| | + | |PerUser |
| | + | |How many times a single customer can buy this product. Only valid for peripheral add-ons |
| | + | |- |
| | + | |IdealPrice |
| | + | |How much products of this type should ideally cost at 100% quality and interest. This is ignored if the software type already defines it. |
| | + | |- |
| | + | |BaseFeature |
| | + | |Optional feature that is always selected, which makes it so this add-on can be developed without needing to pick any features at all. Also forces a baseline development timeline. |
| | + | |- |
| | + | |Features |
| | + | |A list of features, as with the main software type. Each feature also additionally has an optional MaxFactor number that works like a multiplier for the player, e.g. setting it to 3, means the player can multiply this features effect from 1 to 3. If MaxFactor is used, you can also use AmountScript to write a SIPL script that formats the number, e.g. "x + ' bunnies'", will write "3 bunnies" if the player picks 3 as the factor. "LocalizePlural('Employee', x)" will use the plural enabled localization key based on the factor. and Switch(x, clampBool, localizeBool, 'one', 'two', 'three') will pick one of the strings based on the factor value. Finally features can optionally define DependsOn, which is a feature in the main product that needs to be present to use this feature in an add-on. |
| | + | |- |
| | + | |Manufacturing |
| | + | |The manufacturing process for peripheral add-ons |
| | + | |- |
| | + | |NameGenerator |
| | + | |The [[Data Modding#Name generators|name generator]] to use for simulated companies or for when the player clicks the name button in the design document. |
| | + | |- |
| | + | |} |
| | | | |
| | === Hardware === | | === Hardware === |