Updated dependency page to match new syntax (needs proof reading) (#66)

Co-authored-by: mat <[email protected]>

Author: Hbg1010

mods/dependencies.md

@@ -29,17 +29,17 @@ Dependencies can be added to your mod by simply adding it to the `dependencies`
     "name": "My example mod",
     "developer": "Me",
     "version": "v1.0.0",
-    "dependencies": [
-        {
-            "id": "someone-elses.mod",
+    "dependencies": {
+        "someones-mod": ">=v1.0.5",
+        "someone-elses.mod": {
             "version": ">=v1.2.5",
             "importance": "required"
         }
-    ]
+    }
 }
 ```
 
-Dependencies have two required properties: the ID of the dependency and the version depended on. Additionally, the dependency may have an [importance](#importance), which specifies if the dependency is required or not.
+Dependencies can be specified by using an object that maps from a mod id to a version, or more information if needed. The dependency may have an [importance](#importance), which specifies if the dependency is required or not. If this is not specified, the dependency is marked as required.
 
 The `version` field of a dependency may be written as `>=version`, `=version`, or `<=version`. The comparisons work as expected, with the addition that if the major versions are different, the comparison is always false. This means that if you depend on version `>=1.2.5` of a mod, version `v1.8.0` will be considered acceptable but `v2.0.0` will not. For this reason, [if you make a mod that is depended upon, you should follow strict semver](https://semver.org).
 
@@ -51,12 +51,9 @@ The mod `hjfod.gmd-api` contains utilities for working with [.GMD files](https:/
 
 ```json
 {
-    "dependencies": [
-        {
-            "id": "hjfod.gmd-api",
-            "version": ">=v1.0.0"
-        }
-    ]
+    "dependencies": {
+        "hjfod.gmd-api": ">=v1.0.0"
+    }
 }
 ```