Add docs regarding the API version increment.

Author: EliteMasterEric

src/01-fundamentals/01-01-the-metadata-file.md

@@ -19,7 +19,7 @@ Inside this file, we will put the information the game needs in order to learn a
   "optionalDependencies": {
     "modB": "1.3.2"
   },
-  "api_version": "0.6.2",
+  "api_version": "0.6.3",
   "mod_version": "1.0.0",
   "license": "Apache-2.0"
 }
@@ -37,7 +37,7 @@ Inside this file, we will put the information the game needs in order to learn a
   - The mod list will be reordered such that dependencies load first.
 - `optionalDependencies`: A map of mod IDs which are optional dependencies, along with their version numbers.
   - These mods do not necessarily need to be installed for this mod to load, but they will still force the mod list to be reordered so that the dependencies load before this mod.
-- `api_version`: A version number used to determine if mods are compatible with your copy of Funkin'. Change this to the version number for Friday Night Funkin' that you want to support, preferably the latest one (`0.6.2` at time of writing.).
+- `api_version`: A version number used to determine if mods are compatible with your copy of Funkin'. Change this to the version number for Friday Night Funkin' that you want to support, preferably the latest one (`0.6.3` at time of writing.).
 - `mod_version`: A version number specifically for your mod. Choose any version or leave it at `1.0.0`.
 - `license`: The license your mod is distributed under. [Pick one from here](https://opensource.org/licenses) or just leave it as `Apache-2.0`.
 

src/09-migration/09-02-0.5.0-to-0.6.0.md renamed to src/09-migration/09-02-0.5.0-to-0.6.3.md

@@ -1,6 +1,11 @@
-# Migrating from v0.5.0 to v0.6.0
+# Migrating from v0.5.0 to v0.6.3
 
-Migration from v0.5.0 to v0.6.0 requires only minor changes to mods, and won't break most mods.
+Migration from v0.5.0 to v0.6.3 requires some changes to mods.
+
+# Update the API Version
+
+Eric accidentally forgot to increment the API version for the game when updating to v0.6.0, and this got fixed with v0.6.3.
+This means that mods won't load unless the `api_version` value in the `_polymod_meta.json` file is at least v0.6.3. This allows mod creators to perform testing and ensure their mods are compatible before releasing an update on their distribution platforms of choice. Most mods (especially ones with minimal scripting) will need no changes to work as expected, but developers should probably do some playtesting to be sure.
 
 # Migrate from hxCodec to hxvlc
 
@@ -57,6 +62,6 @@ if (Std.isOfType(currentState, OptionsState)) {
 
 # Sticker Changes
 
-v0.6.0 rewrote how stickers get used by the game (and v0.6.3 rewrote it again but better this time). Any existing mods that provided stickers will break.
+v0.6.0 rewrote how stickers get used by the game (and v0.6.3 rewrote it again but better this time). Any existing mods that provided stickers will probably break.
 
 New or updating mods looking to add, remove, or replace stickers should consult the [custom Sticker Packs documentation](../07-custom-sticker-packs/07-00-custom-sticker-packs.md)

src/SUMMARY.md

@@ -41,7 +41,7 @@
 
 - [Migration](09-migration/09-00-migrating-mods-to-newer-versions.md)
     - [v0.1.0 to v0.5.0](09-migration/09-01-0.1.0-to-0.5.0.md)
-    - [v0.5.0 to v0.6.0](09-migration/09-02-0.5.0-to-0.6.0.md)
+    - [v0.5.0 to v0.6.3](09-migration/09-02-0.5.0-to-0.6.3.md)
 
 - [Appending And Merging Files](10-appending-and-merging-files/10-00-appending-and-merging-files.md)
     - [Appending Files](10-appending-and-merging-files/10-01-appending-files.md)