Documentation: minor updates (#320)

* documentation: add links to other guides in adding games.md

* documentation: add webworld to api.md

* documentation: point people to docs folder and discord for help with adding games

* tutorial: go a bit more in depth on downloading a template yaml

* Make Ijwu happy

* point to baseclasses.py in api.md and reformat links a bit

docs/adding games.md

@@ -6,6 +6,11 @@ There are two key steps to incorporating a game into Archipelago:
 - Game Modification 
 - Archipelago Server Integration
 
+Refer to the following documents as well:
+- [network protocol.md](https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/network%20protocol.md) for network communication between client and server.
+- [api.md](https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/api.md) for documentation on server side code and creating a world package.
+
+
 # Game Modification  
 One half of the work required to integrate a game into Archipelago is the development of the game client. This is 
 typically done through a modding API or other modification process, described further down.
@@ -239,7 +244,11 @@ checks, what options to offer for the player’s yaml file, and the code to init
 
 Here’s an example of what your world module can look like:  
   
-![Example world module directory open in Window's Explorer](./img/archipelago-world-directory-example.png)  
+![Example world module directory open in Window's Explorer](./img/archipelago-world-directory-example.png)
+
+The minimum requirements for a new archipelago world are the package itself (the world folder containing a file named `__init__.py`),
+which must define a `World` class object for the game with a game name, create an equal number of items and locations with rules,
+a win condition, and at least one `Region` object.
   
 Let's give a quick breakdown of what the contents for these files look like.
 This is just one example of an Archipelago world - the way things are done below is not an immutable property of Archipelago.  

docs/api.md

@@ -7,8 +7,8 @@ required to send and receive items between the game and server.
 Client implementation is out of scope of this document. Please refer to an
 existing game that provides a similar API to yours.
 Refer to the following documents as well:
-    * [network protocol.md](https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/network%20protocol.md)
-    * [adding games.md](https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/adding%20games.md)
+- [network protocol.md](https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/network%20protocol.md)
+- [adding games.md](https://github.com/ArchipelagoMW/Archipelago/blob/main/docs/adding%20games.md)
 
 Archipelago will be abbreviated as "AP" from now on.
 
@@ -43,12 +43,23 @@ class MyGameWorld(World):
 
 ## Definitions
 
+This section will cover various classes and objects you can use for your world.
+While some of the attributes and methods are mentioned here not all of them are,
+but you can find them in `BaseClasses.py`.
+
 ### World Class
 
 A `World` class is the class with all the specifics of a certain game to be
 included. It will be instantiated for each player that rolls a seed for that
 game.
 
+### WebWorld Class
+
+A `WebWorld` class contains specific attributes and methods that can be modified
+for your world specifically on the webhost. At the moment this comprises of `settings_page`
+which can be changed to a link instead of an AP generated settings page; such is the case
+for Final Fantasy.
+
 ### MultiWorld Object
 
 The `MultiWorld` object references the whole multiworld (all items and locations