rename and improve Action implementing page

enginmanap · Jan 11, 2019 · 4e43cf6 · 4e43cf6
1 parent 01c915f
commit 4e43cf6
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/docs/ExtendingByAPI/implementTrigger.rst → docs/ExtendingByAPI/implementAction.rst b/docs/ExtendingByAPI/implementTrigger.rst → docs/ExtendingByAPI/implementAction.rst
@@ -2,7 +2,11 @@
 How to Implement an Action
 ==========================
 
-Actions are generalized by the class TriggerInterface, under src/GamePlay of the engine. Each new action must implement this interface.
+Actions are generalized by the class TriggerInterface, under src/GamePlay of the engine. Each new action must implement this interface. These actions can be assigned to trigger volumes or GUI button.They can also be run on map load.
+
+Action constructors will get a populated LimonAPI instance for the world they are to be run in. Using this instance, API calls can be made to interact or change the world to game design.
+
+Actions never get persisted, but parameters to pass to actions are persisted with maps.
 
 TriggerInterface Class
 ______________________

diff --git a/docs/ExtendingByAPI/index.rst b/docs/ExtendingByAPI/index.rst
@@ -6,5 +6,5 @@ Extending Engine Capabilities
    :name: toc-extending-by-api
 
    APIUsage
-   implementTrigger
+   implementAction
    APIReference