Difference between revisions of "ModificationWML"
From The Battle for Wesnoth Wiki
(→The [modification] toplevel tag) |
m (spelling) |
||
(8 intermediate revisions by 5 users not shown) | |||
Line 2: | Line 2: | ||
== The [modification] toplevel tag == | == The [modification] toplevel tag == | ||
− | This tag describes an SP or MP modification. A modification is, practically speaking, a bunch of events which get included into the scenario if the modification is enabled. | + | This [[AddonsWML|addon module]] tag describes an SP or MP modification. A modification is, practically speaking, a bunch of events which get included into the scenario if the modification is enabled. |
− | The following keys/tags are recognized for '''[modification]''': | + | The following keys/tags are recognized for '''[modification]''', in addition to all the common [[AddonsWML|addon module keys and tags]]: |
− | + | * '''type''': where the modification will be available for playing. Possible values are ''sp'', ''mp'', and ''hybrid''. hybrid equals mp + sp. N.B. If omitted it defaults to hybrid. Availability in SP also depends on whether or not modification tag is inside a multiplayer define. There is a bug where one can use modifications (not having type=mp) inside such a define by loading multiplayer and returning and then selecting campaign from the main screen. | |
− | |||
− | * '''type''': where the modification will be available for playing. Possible values are ''sp'', ''mp'', and ''hybrid''. | ||
− | |||
* '''allow_scenario''': a list of scenario ids. Only the scenarios with matching ids will be allowed to be played with this modification. | * '''allow_scenario''': a list of scenario ids. Only the scenarios with matching ids will be allowed to be played with this modification. | ||
* '''disallow_scenario''': a list of scenario ids. Only the scenarios with matching ids will not be allowed to be played with this modification. Cannot be used in parallel with allow_scenario. | * '''disallow_scenario''': a list of scenario ids. Only the scenarios with matching ids will not be allowed to be played with this modification. Cannot be used in parallel with allow_scenario. | ||
Line 19: | Line 16: | ||
* '''ignore_incompatible_era''': same as ignore_incompatible_scenario, but for eras. | * '''ignore_incompatible_era''': same as ignore_incompatible_scenario, but for eras. | ||
* '''ignore_incompatible_modification''': same as ignore_incompatible_scenario, but for modifications. | * '''ignore_incompatible_modification''': same as ignore_incompatible_scenario, but for modifications. | ||
− | * '''require_modification''': a boolean value; if set to yes, all players have to have this modification installed to join the game. Default no | + | * '''require_modification''': a boolean value; if set to yes, all players have to have this modification installed to join the game. Default no in older versions and yes since 1.18. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== The [resource] toplevel tag == | == The [resource] toplevel tag == | ||
Line 37: | Line 22: | ||
{{DevFeature1.13|2}} | {{DevFeature1.13|2}} | ||
− | The '''[resource]''' toplevel tag | + | The '''[resource]''' toplevel tag is another type of [[AddonsWML|addon module tag]] which is similar to '''[modification]''' but is invisible to the player. It can only be loaded on developer request, by the '''[load_resource]''' tag. It supports most of the common [[AddonsWML|addon module keys and tags]]. Besides that, there is the '''require_resource''' key which defaults to yes. |
Latest revision as of 22:40, 26 July 2024
The [modification] toplevel tag
This addon module tag describes an SP or MP modification. A modification is, practically speaking, a bunch of events which get included into the scenario if the modification is enabled.
The following keys/tags are recognized for [modification], in addition to all the common addon module keys and tags:
- type: where the modification will be available for playing. Possible values are sp, mp, and hybrid. hybrid equals mp + sp. N.B. If omitted it defaults to hybrid. Availability in SP also depends on whether or not modification tag is inside a multiplayer define. There is a bug where one can use modifications (not having type=mp) inside such a define by loading multiplayer and returning and then selecting campaign from the main screen.
- allow_scenario: a list of scenario ids. Only the scenarios with matching ids will be allowed to be played with this modification.
- disallow_scenario: a list of scenario ids. Only the scenarios with matching ids will not be allowed to be played with this modification. Cannot be used in parallel with allow_scenario.
- allow_era: same as allow_scenario, but for eras.
- disallow_era: same as disallow_scenario, but for eras. Can't be used with allow_era.
- allow_modification: same as allow_scenario, but for modifications.
- disallow_modification: same as disallow_scenario, but for modifications. Can't be used with allow_modification.
- ignore_incompatible_scenario: a list of scenario ids. The scenarios with matching ids will be considered compatible with this modification regardless their dependencies.
- ignore_incompatible_era: same as ignore_incompatible_scenario, but for eras.
- ignore_incompatible_modification: same as ignore_incompatible_scenario, but for modifications.
- require_modification: a boolean value; if set to yes, all players have to have this modification installed to join the game. Default no in older versions and yes since 1.18.
The [resource] toplevel tag
(Version 1.13.2 and later only)
The [resource] toplevel tag is another type of addon module tag which is similar to [modification] but is invisible to the player. It can only be loaded on developer request, by the [load_resource] tag. It supports most of the common addon module keys and tags. Besides that, there is the require_resource key which defaults to yes.
This page was last edited on 26 July 2024, at 22:40.