PlayerState: ProfileStore + Replica, Without the Headache

[lopjoss]

It did give a warning message saying the operation failed because the tables cannot be cyclic, also I added you on discord.

[bellaouzo (bellafat)]

V1.165:
Pushed a GetLeaderboard(statName, limit) function to the client

[LordRenniej (DevRennie)]

Can you push the latest version to wally?

[bellaouzo (bellafat)]

Haven’t pushed to wally in a couple updates I think. I will when I get home

[LordRenniej (DevRennie)]

Thank you and great library : )

[bellaouzo (bellafat)]

Thanks.

Sorry, forgot to update it yesterday. I’ll set an alarm to do it tonight.

[bellaouzo (bellafat)]

Just pushed the latest update to it

playerstate = “bellaouzo/playerstate@1.16.5”

[bellaouzo (bellafat)]

V1.17 pushed with a new ViewedUser feature/config

[loganboxjf (WHYLOL)]

Umm I use wally, and I think the intellisense can’t detect ur module. There is no init.luau in your package. Is this normal?

[ericplane (Eric)]

Are you able to push this update to wally? It still says the latest version available is 1.16.5.

[Flintg7]

awesome module! Any chance of buffers serialization?

[ShadowFox2 (November)]

This implementation really reminds me of SpaceTimeDB, which is awesome because I love using it

The only thing really keeping me from fully commiting to PlayerState is I wish it could handle ephemeral state, or rather state whose values do not need to be saved to the datastore at the end of its lifecycle, i.e session-once values like isChopping or isSprinting for example

Maybe the same way you define leaderstats in DefaultData you could define a section that simply does not get flushed to ProfileStore.. just a thought!

Excited to see this project being regularly maintained!

[bellaouzo (bellafat)]

Yeah I’ll push 1.17 to Wally soon (next day or so). Thanks

[bellaouzo (bellafat)]

I’ll look into adding it in an upcoming update

[bellaouzo (bellafat)]

This is a good idea. I’ll look into adding it very soon. Thanks for the love and feedback!

[bellaouzo (bellafat)]

I honestly do not use wally myself so I am not 100 percent sure, but seems like others are able to use it I think. I would need to see what it looks like on your end. You’d need to require the PlayerStateServer or PlayerStateClient if possible

[Null_OS]

I recently fell upon this post and it has some features I think you should add

@5dpj

Transactions

Transfer coins between two players atomically. If either update fails, the other is rolled back.

local result = Store:Transact({
    {
        Key = tostring(playerA.UserId),
        Transform = function(data)
            if data.Coins < 100 then return nil end -- abort if not enough
            data.Coins -= 100
            return data
        end,
    },
    {
        Key = tostring(playerB.UserId),
        Transform = function(data)
            data.Coins += 100
            return data
        end,
    },
})

if not result.Ok then
    warn("Transaction failed")
end

and

@5dpj

Inbox (gifting between players)

Send a gift from one player to another. Works cross-server — the recipient’s server drains it as soon as it arrives.

-- Enable inbox + handle incoming gifts
local PlayerData = Nexus.CreatePlayerStore({
    Name = "PlayerData",
    Schema = Schema,
    Inbox = true,
    ProcessGift = function(data, gift)
        data.Coins += gift.Payload.Coins
        return data
    end,
})

-- Send a gift (e.g. from a shop or trade system)
local result = PlayerData:SendGift(
    fromPlayer,
    toPlayer.UserId,
    { Coins = 50 }
)

if result.Passed then
    print("Gift sent! ID: " .. result.Value)
end

[ErrorCezar]

I love how it lets you store invalid stuff and nearly kill your roblox studio when you stop play testing

Other from that, peak module, would use again

Edit: my bad for the reply, no clue why it did that- ((its becaue im dumb))

[ErrorCezar]

Also no automatic cleanup onOnChanged events which is quite a shame

[bellaouzo (bellafat)]

@ErrorCezar

I love how it lets you store invalid stuff and nearly kill your roblox studio when you stop play testing

Other from that, peak module, would use again

DataStore UTF-8 validation is between your data and Roblox. PlayerState isn’t a DataStore gatekeeper. If you’re storing non–UTF-8 data, that’s on your code. The module forwards what you put in. I will go ahead and add some sort of validation for it in an update though.