Update to EaglercraftX 1.8 u30

EaglercraftX_1.8_Desktop_Runtime/resources/plugin_version.json

@@ -1 +1 @@
-{"pluginName":"EaglercraftXBungee","pluginVersion":"1.1.0","pluginButton":"Download \"EaglerXBungee-1.1.0.jar\"","pluginFilename":"EaglerXBungee.zip"}
+{"pluginName":"EaglercraftXBungee","pluginVersion":"1.2.0","pluginButton":"Download \"EaglerXBungee-1.2.0.jar\"","pluginFilename":"EaglerXBungee.zip"}

EaglercraftX_1.8_README.md

@@ -153,6 +153,37 @@ The default eaglercraftXOpts values is this:
 - `enableSignatureBadge:` show a badge on the title screen indicating if digital signature is valid
 - `checkRelaysForUpdates:` proprietary feature used in offline downloads
 - `allowVoiceClient:` can be used to disable the voice chat feature
+- `allowFNAWSkins:` can be used to disable the high poly FNAW skins
+- `localStorageNamespace:` can be used to change the prefix of the local storage keys (Default: `"_eaglercraftX"`)
+- `hooks:` can be used to define JavaScript callbacks for certain events
+    * `localStorageSaved:` JavaScript callback to save local storage keys
+    * `localStorageLoaded:` JavaScript callback to load local storage keys
+
+### Using Hooks
+
+You may want to implement some custom logic for loading/saving certain local storage keys. The eaglercraftXOpts hooks section can be used to override the client's local storage load and save functions. Currently, local storage keys are used to save game settings, the user's profile, custom servers, and shared world relays. Worlds and resource packs do not use local storage keys because modern browsers limit local storage keys to only 5 megabytes per domain which is too small for saving entire worlds and resource packs. Worlds and resource packs are saved using [IndexedDB](https://developer.mozilla.org/en-US/docs/Web/API/IndexedDB_API).
+
+    window.eaglercraftXOpts = {
+        ...
+        ...
+        ...
+        hooks: {
+            localStorageSaved: function(key, data) {
+                // 'key' is local storage key name as a string
+                // 'data' is base64-encoded byte array as a string
+                // function returns nothing
+            },
+            localStorageLoaded: function(key) {
+                // 'key' is local storage key name as a string
+                // function returns a base64-encoded byte array as a string
+                // function returns null if the key does not exist
+            }
+        }
+    }
+
+Be aware that the client will still save the key to the browser's local storage anyway even if you define a custom save handler, and will just attempt to load the key from the browser's local storage normally if you return null, these are meant to be used like event handlers for creating backups of keys instead of completely replacing the local storage save and load functions.
+
+On a normal client you will only ever need to handle local storage keys called `_eaglercraftX.p` (profile), `_eaglercraftX.g` (game settings), `_eaglercraftX.s` (server list), `_eaglercraftX.r` (shared world relays), feel free to just ignore any other keys. It is guaranteed that the data the client stores will always be valid base64, so it is best practice to decode it to raw binary first if possible to reduce it's size before saving it to something like a MySQL database in your backend if you are trying to implement some kind of profile syncing system for your website. The keys already have GZIP compression applied to them by default so don't bother trying to compress them yourself a second time because it won't reduce their size.
 
 ## Developing a Client