wesnoth-wiki-changes
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Wesnoth-wiki-changes] EventWML


From: wiki
Subject: [Wesnoth-wiki-changes] EventWML
Date: Tue, 30 Nov 2004 05:11 +0100

UserAgent: Mozilla/5.0 (compatible; Konqueror/3.3; Linux) (KHTML, like Gecko)
IP: 69.199.73.149
URI: http://wesnoth.slack.it/?EventWML
 - - - - -
Index: EventWML
===================================================================
RCS file: /home/wesnoth/cvsroot/wikiroot/EventWML,v
retrieving revision 1.14
diff -u -r1.14 EventWML
--- EventWML    17 Oct 2004 12:09:03 -0000      1.14
+++ EventWML    30 Nov 2004 04:11:24 -0000
@@ -12,7 +12,8 @@
   * 'start' this event triggers after the map is shown but before the scenario 
begins
   * 'new turn' this event triggers whenever the last player ends their turn.
 see also ||first_time_only=no||.
-When the last player ends their turn, before any events of this type trigger, 
the value of the WML variable ||turn_number||
+When the last player ends their turn, before any events of this type trigger, 
the value of the WML variable ||
+turn_number||
 is set to the number of the turn that is beginning.
   * 'side turn' this event triggers when any player ends their turn.
 When a player ends their turn, before any events of this type trigger, the 
value of the WML variable ||side_number||
@@ -46,6 +47,15 @@
 The village may have been previously neutral, or previously owned by another 
side;
 merely moving into your own villages does not constitute a capture.
 
+
+An [allow_undo] tag anywhere within a moveto event will cancel any lack of 
undo functionality the event would have
+caused. It is up to the scenario designer to avoid abusing this command by 
allowing undo on events that shouldn't be
+undoable. The results of doing this may be strange. This actually does have 
functionality beyond aesthetics like
+signs: suppose you have an event that performs some action depending on the 
condition of an 'if' statement. This event
+might be executed on every single move, but the body of the 'if' statement 
entered only in a few cases. Previously
+this would completely disable undo for the entire scenario, while now it can 
be made to only disable undo in the cases
+where the event mutates the scenario.
+
 //Primary_unit// can be referred to as ||unit||. //Secondary_unit// can be 
referred to as ||second_unit||. For
 example,
  [event]
@@ -86,3 +96,4 @@
 * InterfaceActionsWML
 * FilterWML
 * ReferenceWML
+






reply via email to

[Prev in Thread] Current Thread [Next in Thread]