From 03f0996d0028aca1e2cc43cf78227459a939376b Mon Sep 17 00:00:00 2001
From: Rob <1572423+robweber@users.noreply.github.com>
Date: Mon, 26 Aug 2019 17:43:03 -0500
Subject: [PATCH] Created Sample Custom File (markdown)

---
 Sample-Custom-File.md | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 Sample-Custom-File.md

diff --git a/Sample-Custom-File.md b/Sample-Custom-File.md
new file mode 100644
index 0000000..66974e8
--- /dev/null
+++ b/Sample-Custom-File.md
@@ -0,0 +1,34 @@
+Both the Simple and [Advanced Editor](https://github.com/robweber/xbmcbackup/wiki/Advanced-Editor) read in the list of files to Backup via a custom_paths.json file. This file lists the directories to be included in each backup set. Each set can have included or excluded directories. Additionally included directories can be recursed true/false. An example file for the simple pre-sets is below:
+
+```
+{
+	"addons":{
+		"root":"special://home/addons",
+		"dirs":[
+			{
+				"type":"include",
+				"path":"special://home/addons",
+				"recurse":true
+			},
+			{
+				"type":"exclude",
+				"path":"special://home/addons/packages"
+			}
+		]
+	},
+	"addon_data":{
+			"root":"special://home/userdata/addon_data",
+			"dirs":[
+			{
+				"type":"include",
+				"path":"special://home/userdata/addon_data",
+				"recurse":true
+			}
+		]
+	}
+}
+```
+
+Each directory set will create a folder within the backup for it's files. These are done separately, even if sets are pulling from the same folder.
+
+Also during the backup the file selections are recorded in the backup validation file. These are used on restore to restore directories that actually were included in the backup.
\ No newline at end of file