Difference between revisions of "ModificationWML"
From The Battle for Wesnoth Wiki
(Delete common keys and tags documented in AddonsWML) |
(→The [modification] toplevel tag) |
||
Line 6: | Line 6: | ||
The following keys/tags are recognized for '''[modification]''', in addition to all the common [[AddonsWML|addon module keys and tags]]: | 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''. | + | * '''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. | * '''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. |
Revision as of 19:17, 18 January 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.
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 are no additional keys or tags supported in [resource].