Hello! I'm working on a project right now that has a very large open world, editable by players.
In the "blocks" example that comes with the extension, it has pretty much exactly the system I would plan to implement to save the world, however, it's not able to store very many blocks without reaching the size limit.
I was curious if there's an efficient way to combine BDBs and sort of stitch them together, sort of like a chunking system, making a far larger world, with layers and everything. Thank you for the time!
Also, one last question, it wasn't clear to me whether or not the player BDBs were included as the 8 BDBs allowed for a game, or if they are additional BDBs that are not limited to the 8 allowed. Thanks again!
Replies (2)
Last message on 28 Jan 2020
Size43
(Administrator)
on
17 Jan 2020, 18:14:46
I could certainly see this working. You could divide the world into chunks of some size, and then load only the chunks that the player can see. If you want a bigger world but still of fixed size you could simply use some_offset + (chunk_x + chunk_y * width) as the BDB index.
I imagine that the "simple" way of just dividing your world into smaller squares/rectangles and saving those into the BDBs would already get you pretty close to being optimally efficient.
I've given your games some more BDBs so that you can properly experiment with this.
[quote]Also, one last question, it wasn't clear to me whether or not the player BDBs were included as the 8 BDBs allowed for a game, or if they are additional BDBs that are not limited to the 8 allowed. Thanks again![/quote]
The player BDBs are not included in the 8 BDBs limit. That said, please don't create thousands of accounts to cheat the BDB limit.
Forgeio
(Topicstarter)
on
28 Jan 2020, 04:56:30
Thank you very much for the insight, I'll try to do something like what you described.
Also, thank you for the BDBs! I wasn't planning on cheating the system, I was just curious if more places would be taken up if I used the player's personal BDBs for storing inventories haha