Webworld docs: move gameinfo documentation to their world folders and copy them for webhost use. (#455)

worlds/generic/docs/triggers_en.md

@@ -0,0 +1,129 @@
+# Archipelago Triggers Guide
+
+This guide details the use of the Archipelago YAML trigger system. This guide is intended for a more advanced user with
+more in-depth knowledge of Archipelago YAML options as well as experience editing YAML files. This guide should take
+about 5 minutes to read.
+
+## What are triggers?
+
+Triggers allow you to customize your game settings by allowing you to define one or many options which only occur under
+specific conditions. These are essentially "if, then" statements for options in your game. A good example of what you
+can do with triggers is the custom mercenary mode YAML that was created using entirely triggers and plando.
+
+Mercenary mode
+YAML: [Mercenary Mode YAML on GitHub](https://github.com/alwaysintreble/Archipelago-yaml-dump/blob/main/Snippets/Mercenary%20Mode%20Snippet.yaml)
+
+For more information on plando you can reference the general plando guide or the Link to the Past plando guide.
+
+General plando guide: [Archipelago Plando Guide](/tutorial/Archipelago/plando/en)
+
+Link to the Past plando guide: [LttP Plando Guide](/tutorial/zelda3/plando/en)
+
+## Trigger use
+
+Triggers may be defined in either the root or in the relevant game sections. Generally, The best place to do this is the
+bottom of the yaml for clear organization.
+
+- Triggers comprise the trigger section and then each trigger must have an `option_category`, `option_name`, and
+  `option_result` from which it will react to and then an `options` section for the definition of what will happen.
+- `option_category` is the defining section from which the option is defined in.
+    - Example: `A Link to the Past`
+    - This is the root category the option is located in. If the option you're triggering off of is in root then you
+      would use `null`, otherwise this is the game for which you want this option trigger to activate.
+- `option_name` is the option setting from which the triggered choice is going to react to.
+    - Example: `shop_item_slots`
+    - This can be any option from any category defined in the yaml file in either root or a game section.
+- `option_result` is the result of this option setting from which you would like to react.
+    - Example: `15`
+    - Each trigger must be used for exactly one option result. If you would like the same thing to occur with multiple
+      results you would need multiple triggers for this.
+- `options` is where you define what will happen when this is detected. This can be something as simple as ensuring
+  another option also gets selected or placing an item in a certain location. It is possible to have multiple things
+  happen in this section.
+    - Example:
+  ```yaml
+  A Link to the Past:
+    start_inventory: 
+      Rupees (300): 2
+  ```
+
+This format must be:
+
+  ```yaml
+  root option:
+    option to change:
+      desired result
+  ```
+
+### Examples
+
+The above examples all together will end up looking like this:
+
+  ```yaml
+  triggers:
+    - option_category: A Link to the Past
+      option_name: shop_item_slots
+      option_result: 15
+      options:
+        A Link to the Past:
+          start_inventory:
+            Rupees(300): 2
+  ```
+
+For this example if the generator happens to roll 15 shuffled in shop item slots for your game you'll be granted 600
+rupees at the beginning. These can also be used to change other options.
+
+For example:
+
+  ```yaml
+  triggers:
+    - option_category: Timespinner
+      option_name: SpecificKeycards
+      option_result: true
+      options:
+        Timespinner:
+          Inverted: true
+  ```
+
+In this example if your world happens to roll SpecificKeycards then your game will also start in inverted.
+
+It is also possible to use imaginary names in options to trigger specific settings. You can use these made up names in
+either your main options or to trigger from another trigger. Currently, this is the only way to trigger on "setting 1
+AND setting 2".
+
+For example:
+
+  ```yaml
+  triggers:
+    - option_category: Secret of Evermore
+      option_name: doggomizer
+        option_result: pupdunk
+        options:
+          Secret of Evermore:
+            difficulty:
+              normal: 50
+              pupdunk_hard: 25
+              pupdunk_mystery: 25
+            exp_modifier:
+              150: 50
+              200: 50
+      - option_category: Secret of Evermore
+        option_name: difficulty
+        option_result: pupdunk_hard
+        options:
+          Secret of Evermore:
+            fix_wings_glitch: false
+            difficulty: hard
+      - option_category: Secret of Evermore
+        option_name: difficulty
+        option_result: pupdunk_mystery
+        options:
+          Secret of Evermore:
+            fix_wings_glitch: false
+            difficulty: mystery
+  ```
+
+In this example (thanks to @Black-Sliver) if the `pupdunk` option is rolled then the difficulty values will be rolled
+again using the new options `normal`, `pupdunk_hard`, and `pupdunk_mystery`, and the exp modifier will be rerolled using
+new weights for 150 and 200. This allows for two more triggers that will only be used for the new `pupdunk_hard`
+and `pupdunk_mystery` options so that they will only be triggered on "pupdunk AND hard/mystery".