The selection of the optional rules is stored within the file optionalrules.xml. This config file is located within the config folder of the ECE. It can be edited by an text/xml editor or via the ECE ( version >= 0.44 ). If you replace this file by a version from someone else, while the ECE is not running and start it afterwards, you will have ECE with the optional rule selection of him/here.
The following optional rules are supported:
By this option you have a basic control about the attributes values of a character and its side effects. The following three controls exists:
Here you can define how many attribute buy points can be used during character creation. The default is 25 attribute buy points.
If set to "yes" (default) to many spent attribute buy points will not lead to a negative max karma value. If set to "no" the to many spent attributes buy points will reduce the characters maximum karma limit.
This defined how often a attributes can be increased during the characters lifetime. The default value is 3.
Here you can define how many start ranks a character will receive during the character creation
Usually:
Here you can define which attribute will modify the racial movement rate. Currently racial movement rate modifier are implemented which are based on:
Here you can define if the attribute increase will cost legend points or not.
Here you can define if the freely learned spell will cost legend points or not. The spells ability set by the discipline circle will never cost legend points.
Here you can define if the karma points will cost legend points or not.
Here you can define if all modifier of thread items will be added or if only the maximum of each modifier will count.
Here you can define if the all discipline talent will be automatically increase to met the circle increase requirement, but be care full this can result in to many spent legend points.
Here you can define if the default skills will be displayed where possible.
Here you can define if a questor need to spend legend points for his questor talent.
Here you can define if the editor will replace all spent legend point entries of the experience table. The earned legend point with in the experience table stay unchanged. The spent legend point will be removed and replaced by the editor calculated legend points. If you are fully trust the legend point calculation of the editor you can enable this optional rule. If you want to manage your legendpoint earning and spending your self, disable this optional rule.
Here you can define if the editor will auto insert legend points into the experience table. But note, that this rule will only insert not delete entries from the experience table. E.g., if you increase and reduce steps form talents you will get multiple entries and you have to decide which is the right one and which can be deleted. You still in response for your legend point entries.
This rule will have no effect, if the optional rule KEEPLEGENDPOINTSYNC is enabled.
If a date should be printed this defines the format of the date and time http://download.oracle.com/javase/6/docs/api/java/text/SimpleDateFormat.html
This rule can be added multiple times and will define which talents can be used more than ones and how many at maximum.
This rule you can define if a specific talent will be added automatically and will not cost an optional talent slot
Here you can specify specific character generation rule depending on the origin (eg. Barsaive, Cathay, Thera, ...) of the character.