Hello all,
I am working on a Python program to read the `script_docs` log files to a mediawiki table to update the trigger and effect documentations on the wikis. However, I have discovered some inconsistency in those documentation. In CK3 for example:
Sometime is there a short notes before the example:
Sometimes after:
sometimes it is not there at all.
Sometimes the code example is missing:
Those inconsistencies make parser writing very difficult.
Would it be possible in the future to structure the documentation better?
I am working on a Python program to read the `script_docs` log files to a mediawiki table to update the trigger and effect documentations on the wikis. However, I have discovered some inconsistency in those documentation. In CK3 for example:
Sometime is there a short notes before the example:
Code:
every_in_de_facto_hierarchy - Iterate through the title itself, all de facto vassals, and below. The continue trigger specifies whether to recursively iterate through the vassal's vassal
This is unrelated to the limit; if the limit is met it is added to the list, but its vassals will get checked even if the limit isn't met as long as the 'continue' trigger is
..._de_jure_vassal_and_below = { continue = { conditions } }
every_in_de_facto_hierarchy = { limit = { <triggers> } <effects> }
Supported Scopes: landed title
Supported Targets: landed titleSometimes after:
Code:
add_to_global_variable_list - Adds the event target to a variable list
add_to_variable_list = { name = X target = Y }
Where X is the name of the variable
Where Y is an event target
Supported Scopes: nonesometimes it is not there at all.
Code:
ordered_primary_war_enemy - Iterate through all primary war enemies
ordered_primary_war_enemy = {
limit = { <triggers> }
order_by = script_value
position = int
min = int
max = script_value
check_range_bounds = no # If you don't want an error logged if the list is smaller than the min/max
<effects> }
Supported Scopes: character
Supported Targets: characterSometimes the code example is missing:
Code:
replace_court_position - Replaces the target character holding target court position within scoped character's court with target character
recipient = character scope - target character to receive the title
holder = character scope - target character to revoke the target court position of in favour of recipient
court_position = court position type - court position type to assign the receiver
Supported Scopes: characterThose inconsistencies make parser writing very difficult.
Would it be possible in the future to structure the documentation better?
