diff --git a/docs/Documentation/Fsm.html b/docs/Documentation/Fsm.html index 569d760c2..c2c28e4d1 100644 --- a/docs/Documentation/Fsm.html +++ b/docs/Documentation/Fsm.html @@ -89,7 +89,7 @@ It is a fantastic development, this module.

  • An Event describes an action, that can be triggered both internally as externally in the FSM. An Event can be triggered Embedded or Delayed over time.
    • -

    Test Image

    +

    Test Image

    An FSM transitions in 4 moments when an Event is being handled.
    Each moment can be catched by handling methods defined by the mission designer,
    @@ -103,7 +103,7 @@ These methods define the flow of the FSM process; because in those methods the F

    * The OnLeave and OnBefore transition methods may return false to cancel the transition.*

    -

    Test Image

    +

    Test Image

    The FSM creates for each Event two Event trigger methods.
    There are two modes how Events can be triggered, which is embedded and delayed:

    @@ -113,7 +113,7 @@ There are two modes how Events can be triggered, which is embeddedThe method FSM:__Event( seconds ) triggers an Event that will be processed delayed over time, waiting x seconds. -

    Test Image

    +

    Test Image

    1.1) Define the FSM Rules

    diff --git a/docs/Documentation/Spawn.html b/docs/Documentation/Spawn.html index 504721dca..23caec6d9 100644 --- a/docs/Documentation/Spawn.html +++ b/docs/Documentation/Spawn.html @@ -2489,7 +2489,7 @@ Spawn_BE_KA50 = SPAWN:New( 'BE KA-50@RAMP-Ground Defense' ):Schedule( 600, 0.5 ) -

    Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.

    +

    When the first Spawn executes, all the Groups need to be made visible before start.