The module is inherited from ModuleBase. So base parameters can be found there.
Module name
The name of the module you use as the meta of the module definition is 'Options' or 'OptionModule' if _force_search is set to true in the module definition.
Path/Name of a table that holds all the values for the multichoice option (BeardLib reads the string and finds the object with the name/path) Example: self.MyValues or MyGlobalClass.MyValues
save_value
Boolean
Determines if the value of the option should be saved or the index. This is useful if you have a variable amount of values which may have ones inserted in the middle or the end and the value should be retained.
<values> <value_node value/> ... </values>
This allows you to define the multichoice items in the xml. value_node automatically assigns the index depending on its location inside <values>
<option type="number" min max step show_value ...> ... </option>
Parameter
Type
Description
min
Number
The minimum value of the option in the menu
max
Number
The maximum value of the option in the menu
step
Number
The step value of the option in the menu
show_value
Boolean
Determines if the value should be shown on the option in the menu
<option type="colour" alpha scale_factor step min max ...> ... </option>
Parameter
Type
Description
alpha
Boolean
Determines if there should be an option for the alpha of the colour in the menu.
scale_factor
Number
What the values of the colour are scaled up to. E.g. 255 so that it is more intuitive for the user.
step
Number
The step of the options for the colour
min
Number
The minimum value of the options for the colour
max
Number
The maximum value of the options for the colour
<option type="vector" scale_factor step min max ...> ... </option>
scale_factor, step, min, max Same as in the colour option.
<option type="table"/>
The table option type is used to save tables into the options config, the menu will not create anything for this item, mostly this item is the same as the others just that default_value is a table like seen in here:
<option_group build_menu ...> ... </option_group>
Same parameters as defined in the main options docs. The option_group can hold sub_menus in the form of option_groups or option_sets and sub options. The option_group is used for grouping of similar options, this will create a sub menu in the parent node for the options.
Parameter
Type
Description
build_menu
Boolean
Determines if this sub menu should be built in the options menu
The option set is used to create a collection of options which have similar parameters. This is used in PD:TH Hud to create the options for Heist Specific colour grading, as it generates the set of options based on the values from the tweak_data.
Parameter
Type
Description
not_pre_generated
Boolean
Determines if the options are pre_generated. This should be used if you are saving options which are not fixed and you just want to store values. This is used in the BeardLib-Editor to save the prefabs for the map editor.
items_tbl
String
Path/Name of a table which contains data for the items which are part of the option_set. It should be setup like a table of sub tables which contains the item parameters for an option, these will overwrite any of the `item_parameters
that were defined.
populate_items
String
Path/name of a function which returns a table for the items. See: above detail.
<items> </items>
This can be used to define the items for the option set. See: 'items_tbl' definition above.
<item_parameters ...> ... </item_parameters>
Item parameters as defined in the docs for the 'option' node.
Resets the options. path is the path to the option group that should be reset (leave as an empty string to reset all), shallow determines if the reset should only happen in the current table and not in the sub options too, no_save determines if after resetting the options the function shouldn't save the changes
Save()
Saves the options
There are more functions but as they are mostly used in the class itself they are not defined here.