Basically what I'm attempting to do, is use data stores to save all the blocks of the game to it. the MAIN problem is the size it would be. I want a max of 4 chunks per dimensions, each chunk is roughly 64 x 64 x 256 studs, with bricks in the 2 x 2 x 2 range, but can be cut into smaller .1 x .1 x .1 pieces. So would using data stores be practical?
The second question depends all on the first question. If you said yes then this question is along with the first. I am trying to use a rendering system that gets the blocks within a certain area, maybe 1 chunk in a square (circle?), and checks to see if they need rendered. This is due to me needing to cut down the lag ALOT, as in studio it drops to 40 FPS from 1 chunk, for 4 chunks, it was roughly 12 FPS. I have a good computer made for gaming and it can't handle this well, nevertheless phones. So is any of this possible right now, or should I just try something else?
~ Legobuildermaster

1 comment
I might be wrong, but I believe you can't save parts with data stores. You'd have to use data persistence instead, but that has a size limit.