Changes between Version 34 and Version 35 of content/LevelHowTo

Timestamp:

Feb 23, 2012, 6:03:16 PM (13 years ago)

Author:

jo

Comment:

—

content/LevelHowTo

@@ -240 +240 @@
     <StaticEntity position="<?lua print(y) ?>,0,<?lua print(z) ?>" scale="<?lua print(math.random() * 10 + 5) ?>" collisionType="static" >
 <?lua end ?>
-
-
 }}}
 
 
 == Triggers && Events ==
-Example: ../data/levels/events.oxw 
-
+Example: ../data/levels/events.oxw
+
+So far your level design is static. Everything is placed in the level, when it is loaded (except the spawned objects) and doesn't change its behaviour once loaded. Via the trigger/event system you can make the level react on what the player does.
+A trigger is like a button. When you activate it, something happens.
+{{{
+#!xml
+<DistanceTrigger name="flying1" position="800,700,600" target="Pawn" distance=10 stayActive="true" delay=6/>
+
+<SimpleNotification message="Let's fly to the blinking light.">
+    <events>
+       <trigger>
+           <EventListener event="flying1" />
+        </trigger>
+    </events>
+</SimpleNotification>
+}}}
+DistanceTriggers are artivated, when the target (e.g. a pawn, a spaceship, ...) is close enough to the distance trigger (defined via "distance"). The stayActive attribute keeps the switch activated once triggered. The name attribute is needed in order to catch the event, when the trigger was activated. The SimpleNotification is sent to the player when the trigger is activated. Note that the trigger is activated with a delay of 6 seconds.
 
 == Quests ==