768
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: + + + Line 104:
Line 107: + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
|Description
|Description
|The contents of the tooltip that will appear when hovering over the software type in the dropdown menu in the design document window.
|The contents of the tooltip that will appear when hovering over the software type in the dropdown menu in the design document window.
|-
|Unlock
|Which year this software type will unlock, e.g. <Unlock>1995</Unlock>
|-
|-
|Random
|Random
== Features ==
== Features ==
Features are defined in the Feature tag of Software types. Optinally a base.xml file can be placed in the "SoftwareTypes" folder with feature definitions, which will then be added to all software. If the root tag of the base.xml file contains the attribute Override = "TRUE", it will remove any base features already defined, this would remove the built-in QA feature for example.
Features are defined in the Feature tag of Software types. Optinally a base.xml file can be placed in the "SoftwareTypes" folder with feature definitions, which will then be added to all software. If the root tag of the base.xml file contains the attribute Override = "TRUE", it will remove any base features already defined, this would remove the built-in QA feature for example.
=== Tags ===
{|
|Feature
|This is the root tag, which all tags should be a child to. If this tag has the attribute Forced = "TRUE", then this will be implemented by default and the player won't be able to un-tick it, unless it is superseded by another feature. If this tag has the From = "FeatureName" tag, the feature, "FeatureName", will supersede this feature and you can't build entire dependency trees like this.
|-
|Name
|The name of the feature as it will appear in feature panel in the design document window
|-
|Category
|An optional tag that controls which specialization a product belongs to. If it is omitted the feature will belong to the base skill level of a field, usually desibred as "General" in Software Inc. which is controlled by the employees main skill in a role. Otherwise the meployees specialization skill will control how well, if at all, they work with this feature. This can be 2D, 3D, Network, etc.
|-
|Description
|The contents of the tooltip that will appear when hovering over the feature in the design document window.
|-
|DevTime
|How many months it takes to develop this feature
|-
|Innovation, Usability, Stability
|These three tags are normalized, so you can put in any number, 3, 4 and 5 would result in 3/12, 4/12 and 5/12. Innovation controls how long the product will stay interesting to customers. Usability controls how well customers will like the product and in extension, your company. Stability controls bugs and how much skill your employees will gain from working on the feature.
|-
|CodeArt
|The coding to art balancing of the feature. 1 will mean this feature only requires programmers whereas 0 will mean it only requires artists.
|-
|Dependencies
|What features this feature depends on to be available, this can be features in the current product, features in other products or features in supported operating system. Note that opretaing system feature dependencies are taken as an intersection, so if a features relies on 3D in an operating system, ALL chosen operating systems must support 3D. A dependency should be defined as <Dependency Software="Operating System">3D</Dependency>
|}