Should I use 1 profile to store the players save slots in their data as separate tables, or should i make multiple profiles inside of another profiles data table and load each profile when needed. I know that there are like 3 other posts like this but none of them reached a direct answer. I have already asked (some of) this question here but i dont think it’ll get responses
1 Like
It will depend on what you are saving, and how ProfileStore supports it. I am not familiar enough with profile store to know if saving data under different datastore keys for a player is supported, or easy to implement
Saving save slots under their own keys is something I would strongly recommend for plot based games, or games in general that save a lot of data, to slots that are loaded when the player joins (after the player selects which slot to load). The main downside is that you need to do multiple datastore requests (which isn’t much of an issue if you load only one of the slots). Main upside is that each slot has 4mb of storage space, instead of sharing 4mb between every slot
However, if you are not saving a lot of data (it really takes a lot of data to use 4mb), then storing everything under the same key is a perfectly fine approach
Next consideration is the complexity of implementing it. Saving each slot to its own key adds a bit of complexity, but it’s not very complicated. However, with ProfileStore, I do not know
1 Like
if your save slots do not save large data, you can combine each player’s save slots into the same Profile for easy reading and writing
The code logic of the ProfileStore is to have a session lock for each Profile by default, each with its own Metadata
Also, if your game only allows single-slot play, You can set up a separate Profile for each slot directly
1 Like
i’m just trying to store inventories (tables), stats (more tables) and skill trees (even more tables), I don’t want to be rude and tell u to js read the docs, so imma js say that u can have multiple profiles, which have a table of player data, and u can have multiple profiles under 1 player or
Would you recommend separate profiles or separate tables in the profiles data folder, the game can only be played 1 save file (or slot) at a time and is an rpg not too dissimilar to YBA or TYPE://SOUL (I don’t rly like type soul tho)
1 Like
Depending on your needs, I think it is a reasonable choice to use a separate Profile to store save slot.
If you want to save memory, you can merge them into a Profile as I said
Oh as you said, inventories (tables), stats (more tables) and skill trees (even more tables) this can be merged in one slot.
Or Use a Store separation policy to establish separate Stores for each type and then store them separately
(It will depend on how you manage it Genre-based or player-based)
2 Likes
what is genre-based, how is it different to player-based?
1. GENRE-BASED
Each Store is responsible for one thing
Genre-based refers to separating inventories, stats, skill trees, etc. and creating a separate DataStore
2. PLAYER-BASED
Each Store is responsible for many players Object
so Player-based is just OOP
Each player Store is the data belonging to that player, and you only need to get it once to get all the information about the player
(ProfileStore likes the second way) ！！！！！
To make the first way , you need to write a DataStore module yourself
1 Like
thank you, i think i will do player based, with that diagram though, I think it would look its more like this
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.