The Battle for Wesnoth Wiki - User contributions [en]

User:Ayin/Multiplayer campaigns

2006-10-26T22:27:05Z

Dirus:

== Status of multiplayer campaigns development ==

Multiplayer campaigns are currently more or less supported by the engine. Multiplayer scenarios, like single-user scenarios, may specify the <tt>next_scenario</tt> flag. The <tt>side_id</tt> flag is used to ensure continuity between scenarios.

The following points, however, are missing to have an actual {{"|multiplayer campaigns}} support:

* Add some GUI for campaigns. Currently, campaigns which span over multiple scenarios are possible... But all scenarios will be displayed in the normal {{"|scenario selection}} box of the lobby.
see "allow_new_game" in [[ScenarioWML]]

* Add some way to hide opponents. Currently, all present sides are available in MP games: this is impossible for a MP scenario designer to specify AI-only sides (NPC sides) which cannot be taken by players.
* Either:
** Have some way to specify that a side cannot be taken by an AI
** ...or teach the AI to use recall lists (think: player adding a AI-ally instead of a human one).

I'm not sure what you're looking for here, it sounds like two issues. 1 you can see the AI, and 2 you don't want players on the same team as the AI.

[[SideWML]] has something for both of those. The ill named "allow_player" has been around since May and it lets you hide a side. And you can use "side_lock" to prevent the creator from changing the team of a particular side before a game starts.

That said, it would be nice for the AI to know how to use recall lists.

User:Ayin/Multiplayer campaigns

2006-10-25T06:32:44Z

Dirus: informing user

SideWML

2006-10-03T03:06:16Z

Dirus: /* the [side] tag */

{{WML Tags}}
== the [side] tag ==

The [side] tag is used to describe a side in a particular scenario.

The following keys are recognized:

* ''side'' a digit. The leader of this side is placed on the tile represented by this digit (see [[BuildingMaps]]). When defining sides, they must be defined in order since the side number is checked against the number of sides seen so far.

* ''controller'' how moves for this side should be inputted.
** 'ai' the Wesnoth AI makes this side's moves. This is the default setting.
** 'human' a player controls this side's moves.
** 'null' the side doesn't get a turn to move and doesn't have a leader generated from the contents of the [side] tag. (It still can get units from [unit] tags in the [side] tag.)

* ''no_leader'' if "no" (default), then keys describing a unit which will begin on the side's keep will be described in the remainder of the '''[side]''' tag, See [[SingleUnitWML]]. Note that if the keys ''x'', ''y'' are included, the leader will begin there regardless of keep location. If this side has a recall list from a previous level, then the recall list will be searched for a leader (using canrecruit) and if one is found it will be used instead of the one described in the '''[side]''' tag.

* ''type'' the unit type of the side's leader. This must be present if ''no_leader'' is not set to "yes." ''Description'', ''type'', ''x'', ''y'', ''profile'', and ''hitpoints'' are examples of keys from [[SingleUnitWML]] that will describe the leader if placed within the [side] tag.

* ''description'' (translatable) the name of the side's leader. It is used in standard unit filter ([[FilterWML]]) and it is not affected by a player renaming a unit.

* ''unrenamable'' if "no" (default), the player can rename the unit. Renaming the unit alters the ''user_description'' key, so the ''description'' key can still be used for filtering. It is generally a good idea to set this to yes in campaigns since dialog will usually refer to the leader by name. It is technically possible to read ''user_description'' into a variable every time you want to call the leader by name, but this is a hassle.

* ''recruit'' a list of unit types. At the beginning of the scenario, the side gains recruitment of these units.

* ''gold'' the starting gold for this side. Default 100. (If gold is carried over from a previous scenario, this value is the minimum starting gold.)

* ''income'' the base income for this side, default 0. This is added to ''base_income'', '''[game_config]''' to determine the side's base income. (see [[GameConfigWML]]).

* ''fog'' if 'yes', this side cannot see any tiles it is not within vision of, except at the start.

* ''shroud'' if 'yes', this side cannot see any tiles it has not moved within sight of.

* ''shroud_data'' describes the area which this team has de-shrouded.

* ''persistent'' whether the side exists in any other scenarios. If '1'(yes), then ''save_id''(see below) becomes active for this side. Default '0'(no); when '''controller=human''', this is always '1'.

* ''save_id'' default ''description'' if available, 'Unknown' otherwise. The ID of the side with respect to the previous and next scenarios. Used to carry over the side's recall list (including the side's leader), recruitment list, and starting gold from scenario to scenario. Also used for the side's displayed name in the victory gold-calculation dialog.

* ''team_name'' a non translatable string representing the teams description. Sides with the same team_name are allied. Default ''side''.

* ''user_team_name'' a translatable string representing the teams description. This has no effect on alliances. Default ''team_name''.

* ''colour'' if you want side 4 to be the same colour as side 2 normally is, put colour=2.
** The default list of numbers and corresponding colors can be found in data/team_colors.cfg.

* ''flag'' a custom flag animation to use instead of the default one to mark captured villages.
** Example animation that has three frames and loops every 750ms: ''flag=misc/myflag-1.png:250,misc/myflag-2.png:250,misc/myflag-3.png:250''

* ''village_gold'' the amount of gold given to this side per village it controls per turn. Default specified in ''village_gold'', '''[game_config]''' ([[GameConfigWML]]).

* ''share_maps'' whether sides allied with this side see all terrains that this side sees, if they are on shroud.

* ''share_view'' whether sides allied with this side see the units that this side sees, if they are on FoW (fog).

* ''name'', ''id'', ''leader'' not used; see [[EraWML]].

* ''music'' music to play for this player. Default specified in [scenario] (see [[ScenarioWML]]).

* '''[ai]''' if '''controller=ai''', gives parameters to the AI. See [[AiWML]].

* '''[village]''' describes a village the side begins in control of.
** ''x'', ''y'' the location of the village.

* '''[unit]''' describes a unit which begins on the side. See [[SingleUnitWML]]. If the side has a recall list and the unit is not given a location, it will start on the recall list. Note that the ''side'' attribute under '''[unit]''' will be ignored, as the side will come from the ''side'' attribute of '''[side]'''.

The following keys are multiplayer only:

* ''allow_player'' if false then this side will not be allowed to be modified and will be hidden during game creation.

* ''team_lock'' if true then this side's team is not allowed to be modified.

* ''colour_lock'' if true then this side's color is not allowed to be modified.

* ''gold_lock'' if true then this side's gold is not allowed to be modified.

* ''income_lock'' if true then this side's income is not allowed to be modified.

== See Also ==
* [[EraWML]]
* [[ScenarioWML]]
* [[ReferenceWML]]

[[Category: WML Reference]]