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.