Changes

{|class="wikitable"

{|class="wikitable"

|Name

|Name

|The name of the feature as it will appear in feature panel in the design document window

|The name of the feature as it will appear in feature panel in the design document window

|-

|-

|Category

|Spec

|A tag that controls which specialization a product belongs to. The employees' specialization skill will control how well, if at all, they work with this feature. This can be 2D, 3D, Network, etc. You can add new specializations to the game using this tag by simply writing whatever you want.

|Which specialization this feature maps to. This can be 2D, 3D, Network, etc. You can add new specializations to the game using this record by simply writing whatever you want.

|You can use this optional tag if you want the art part of a feature to belong to a different category than the code part. This is not relevant if your CodeArt ratio (details below) is equal to 0 or 1.

|-

|-

|Description

|Description

|-

|-

|Unlock

|Unlock

|Which year this feature will unlock, e.g. <Unlock>1995</Unlock>. Specializations will unlock, when the first feature which uses it unlocks.

|Which year this feature will unlock, e.g. '''Unlock 1995'''. Specializations will unlock, when the first feature which uses it unlocks.

|-

|-

|DevTime

|DevTime

|How many months it takes to develop this feature

|How many months it takes to develop this feature

|-

|-

|Innovation, Usability, Stability

|Submarkets

|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.

|A list of 3 values determining the submarket ratio, i.e. how this feature satisfies the submarkets. These three values are normalized, so you can put in any number. 3, 4 and 5 would result in 3/12, 4/12 and 5/12.

|-

|-

|CodeArt

|CodeArt

|How many mbps this feature will need per active user. It is scaled with time using the formula 1+log10(year-1969). MMO uses 0.002, which would be around 5 gbps at any given time for a 1 million user game in 2010, which might change in the future.

|How many mbps this feature will need per active user. It is scaled with time using the formula 1+log10(year-1969). MMO uses 0.002, which would be around 5 gbps at any given time for a 1 million user game in 2010, which might change in the future.

|-

|-

|Dependency

|Optional

|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 operating 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 &lt;Dependency Software="Operating System"&gt;3D&lt;/Dependency&gt;. You can have multiple of these tags per feature

|If you want the player to be able to toggle this feature off, just add the record '''Optional True''', otherwise you can omit this record.

|Optional record that limits the feature to a certain software category of its parent software type. You can specify a year with each category you list, e.g. '''[ [Computer; 1995]; [ Console; 2000 ] ]''', however if you just want the feature to only be available for some categories, you can write them out in a list like so: '''[ Computer; Console]''', which is equivalent to unlocking at year 0. Having this record will override it in all its subfeatures.

|This is the list of SubFeatures that belongs to this SpecFeature.

|-

|-

|}

|}