Include official scripts in release archive

Makefile

@@ -172,6 +172,7 @@ release:
 	#@-cp $(OUTPUT).3dsx $(RELEASE)/$(TARGET)
 	#@-cp $(OUTPUT).smdh $(RELEASE)/$(TARGET)
 	@cp $(CURDIR)/README.md $(RELEASE)
+	@cp -R $(CURDIR)/resources/gm9 $(RELEASE)/gm9
 	@-7z a $(RELEASE)/$(TARGET)-`date +'%Y%m%d-%H%M%S'`.zip $(RELEASE)/*
 
 #---------------------------------------------------------------------------------

README.md

@@ -14,7 +14,7 @@ __As always, be smart, keep backups, just to be safe__.
 These short instructions apply to all users who have ARM9loaderhax or SigHax and [Luma3DS](https://github.com/AuroraWright/Luma3DS) installed (Luma3DS set up with standard paths), which will be the majority of all GodMode9 users. Here's how to set it up quickly:
 * *[A9LH only]* Rename `GodMode9.bin`(from the release archive) to `X_GodMode9.bin`(change `X`to the button of your choice) and put it into `sd:/luma/payloads/`
 * *[SigHax only]* Rename `GodMode9.firm`(from the release archive) to `X_GodMode9.firm`(change `X`to the button of your choice) and put it into `sd:/luma/payloads/`
-* Get good versions of `aeskeydb.bin`, `seeddb.bin` and `encTitlekeys.bin` from somewhere (don't ask me!) and put these three files into `sd:/gm9/support` (optional but recommended for full functionality).
+* Copy the `gm9` folder from the release archive to your SD card. Then, get good versions of `aeskeydb.bin`, `seeddb.bin` and `encTitlekeys.bin` from somewhere (don't ask me!) and put these three files into `sd:/gm9/support` (optional but recommended for full functionality).
 * Helpful hint #1: Go [here](https://3ds.guide/godmode9-usage) for step by steps on doing some common tasks in GodMode9. Especially users coming from Decrypt9WIP or Hourglass9 may find this to be helpful.
 * Helpful hint #2: __Never unlock the red write permission level unless you know exactly what you're doing__. You will notice that prompt when it comes up, it features a completely red screen. It is recommended you stay on the yellow permission level or below at all times to be completely safe. Also read more on the write permissions system below.
 

resources/gm9/scripts/Backup EmuNAND.gm9

@@ -0,0 +1,11 @@
+# EmuNAND backup GM9 script
+# This will create a backup named [SERIAL]_nandmin_???.bin
+# author: d0k3
+
+set ERRORMSG      "EmuNAND backup failed"
+set SUCCESSMSGMSG "EmuNAND backup success"
+
+ask "Create a EmuNAND backup in $[GM9OUT]?"
+findnot $[GM9OUT]/$[SERIAL]_emunand_???.bin OUTPATH
+cp E:/nand_minsize.bin $[OUTPATH]
+echo "Backup created succesfully:\n$[OUTPATH]"

resources/gm9/scripts/Backup SysNAND.gm9

@@ -0,0 +1,10 @@
+# SysNAND backup GM9 script
+# This will create a backup named [SERIAL]_nandmin_???.bin
+# author: d0k3
+
+set ERRORMSG "SysNAND backup failed"
+
+ask "Create a SysNAND backup in $[GM9OUT]?"
+findnot $[GM9OUT]/$[SERIAL]_sysnand_???.bin OUTPATH
+cp S:/nand_minsize.bin $[OUTPATH]
+echo "Backup created succesfully:\n$[OUTPATH]"