1 Like
Isn’t the making multiple datastores for each value a beginner thing? It seems that this module just imitates a table with a bit of extras.
Nexus isn’t just about avoiding multiple DataStores it’s a professional-grade solution that handles atomic operations, priority-based saving, and automatic throttling prevention while maintaining data integrity at scale.
For example: While a basic script might save player stats with 10 separate SetAsync() calls (risking throttling), Nexus consolidates them into a single atomic operation with priority control like saving a player’s critical health data before their cosmetic changes.
What makes Nexus beginner-friendly isn’t just simplicity it automates complex parts (like session locking and batch saves) while exposing intuitive controls. New devs get production-grade safety without needing to understand the messy details, while veterans can tweak priorities and caching.
this wrapper is certainly unconventional,
what’s the use case that justifies using this over saving your data to a single datastore yourself?
I feel the “saving to multiple datastores” problem is one most beginners are already abstracting away using popular datastore libraries
And why couldn’t you just save everything as a table that would require only one SetAsync() call. For me it seems this just adds extra complexity. And storing each value with a separate call is bound to cause throttling and isn’t done nor recommended apart beginners which seems this system is targeted at.
How is this better than profilestore?
Why should i use this over profilestore?