@quenty/datastore 13.14.0 → 13.15.0

package/CHANGELOG.md

@@ -3,6 +3,14 @@
 All notable changes to this project will be documented in this file.
 See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
 
+# [13.15.0](https://github.com/Quenty/NevermoreEngine/compare/@quenty/datastore@13.14.0...@quenty/datastore@13.15.0) (2024-11-12)
+
+**Note:** Version bump only for package @quenty/datastore
+
+
+
+
+
 # [13.14.0](https://github.com/Quenty/NevermoreEngine/compare/@quenty/datastore@13.13.2...@quenty/datastore@13.14.0) (2024-11-06)
 
 

package/README.md

@@ -18,6 +18,13 @@ This system is a reliable datastore system designed with promises and asyncronio
 ## Executive overiew
 This datastore prevents data loss by being explicit about what we're writing to, and only modifying the data that exists there instead of modifying the whole structure.
 
+## Comparison to other solutions
+
+* Not specifically locked to players
+* Native substore support for decoupled code
+* Very performant and battle tested
+* Native Rx and Promise implementation
+
 ## How syncing works
 Sometimes datastores (like a global game data store) need to be synced live instead of upon server or player start. This is if we expect multiple servers to write to the same datastore at once we can use thie sync method to 
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quenty/datastore",
-  "version": "13.14.0",
+  "version": "13.15.0",
   "description": "Quenty's Datastore implementation for Roblox",
   "keywords": [
     "Roblox",
@@ -42,5 +42,5 @@
   "publishConfig": {
     "access": "public"
   },
-  "gitHead": "00e6f71716216dd6ecbc8505ad898a1ab7f72756"
+  "gitHead": "9c3afd151641bac32d4bcc66e1e5eb218d095b41"
 }