DataStoreStage

This item only works when running on the server. Server

Provides a data storage facility with an ability to get sub-stores. So you can write directly to this store, overwriting all children, or you can have more partial control at children level. This minimizes accidently overwriting. The big cost here is that we may leave keys that can't be removed.

Layers in priority order:

1. Save data
2. Substores
3. Base layer

Functions

new

</>

DataStoreStage.new(

loadName: string,

loadParent: DataStoreStage?

) → DataStoreStage

Constructs a new DataStoreStage to load from. Prefer to use DataStore because this doesn't have any way to retrieve this.

See DataStore, GameDataStoreService, and PlayerDataStoreService.

-- Data store inherits from DataStoreStage
local dataStore = serviceBag:GetService(PlayerDataStoreService):PromiseDataStore(player):Yield()

Store

</>

DataStoreStage:Store(

key: string | number,

value: any

) → ()

Stores the value, firing off events and queuing the item for save.

dataStore:Store("money", 25)

Load

</>

DataStoreStage:Load(

key: string | number,

defaultValue: T?

) → Promise<T>

Loads the data at the key and returns a promise with that value

dataStore:Load():Then(function(data)
	print(data)
end)

LoadAll

</>

DataStoreStage:LoadAll(defaultValue: any) → Promise<any>

Promises the full content for the datastore

dataStore:LoadAll():Then(function(data)
	print(data)
end)

GetSubStore

</>

DataStoreStage:GetSubStore(key: string | number) → DataStoreStage

Gets a sub-datastore that will write at the given key. This will have the same helper methods as any other data store object.

local dataStore = DataStore.new()

local saveslot = dataStore:GetSubStore("saveslot0")
saveslot:Store("Money", 0)

Delete

</>

DataStoreStage:Delete(key: string | number) → ()

Explicitely deletes data at the key

Wipe

</>

DataStoreStage:Wipe() → ()

Queues up a wipe of all values. This will completely set the data to nil.

Observe

</>

DataStoreStage:Observe(

key: string | number | nil,

defaultValue: T?

) → Observable<T>

Observes the current value for the stage itself

If no key is passed than it will observe the whole view snapshot

AddSavingCallback

</>

DataStoreStage:AddSavingCallback(

callback: function--

May return a promise

) → function--

Call to remove

Adds a callback to be called before save. This may return a promise.

RemoveSavingCallback

</>

DataStoreStage:RemoveSavingCallback(callback: function) → ()

Removes a saving callback from the data store stage

GetTopLevelDataStoredSignal

</>

DataStoreStage:GetTopLevelDataStoredSignal() → Signal

Gets an event that will fire off whenever something is stored at this level

GetFullPath

</>

DataStoreStage:GetFullPath() → string

Retrieves the full path of this datastore stage for diagnostic purposes.

PromiseKeyList

</>

DataStoreStage:PromiseKeyList() → Promise<{string}>

Promises a list of keys in the data store stage

PromiseKeySet

</>

DataStoreStage:PromiseKeySet() → Promise<{[string]: true}>

Promises a set of keys in the data store stage

MergeDiffSnapshot

</>

DataStoreStage:MergeDiffSnapshot(diffSnapshot: any) → ()

This will always prioritize our own view of the world over incoming data.

tip

This is a helper method that helps load diff data into the data store.

MarkDataAsSaved

</>

DataStoreStage:MarkDataAsSaved(parentWriter: DataStoreWriter) → ()

Updates the base data to the saved / written data.

This will always prioritize our own view of the world over incoming data.

PromiseViewUpToDate

</>

DataStoreStage:PromiseViewUpToDate() → Promise

Helper method that when invokes ensures the data view.

tip

This is a helper method. You probably want DataStore.LoadAll instead.

Overwrite

</>

DataStoreStage:Overwrite(data: any) → ()

Ovewrites the full stage with the data specified.

tip

Use this method carefully as it can lead to data loss in ways that a specific :Store() call on the right stage would do better.

OverwriteMerge

</>

DataStoreStage:OverwriteMerge(data: any) → ()

Ovewrites the full stage with the data specified. However, it will merge the data to help prevent data-loss.

tip

Use this method carefully as it can lead to data loss in ways that a specific :Store() call on the right stage would do better.

StoreOnValueChange

</>

DataStoreStage:StoreOnValueChange(

name: string | number,

valueObj: Instance--

ValueBase object to store on

) → MaidTask--

Cleanup to remove this writer and free the key.

Whenever the ValueObject changes, stores the resulting value in that entry.

HasWritableData

</>

DataStoreStage:HasWritableData() → boolean

If these is data not yet written then this will return true

GetNewWriter

</>

DataStoreStage:GetNewWriter() → DataStoreWriter

Constructs a writer which provides a snapshot of the current data state to write.

tip

This is automatically invoked during saving and is public so DataStore can invoke it.

PromiseInvokeSavingCallbacks

</>

DataStoreStage:PromiseInvokeSavingCallbacks() → Promise

Invokes all saving callbacks

tip

This is automatically invoked before saving and is public so DataStore can invoke it.