Update 25.10.29 : news/update-25-10-29
trophy 1550Apr 2021
195 posts
trophy 2160Sep 2021
15 posts
trophy 2013Sep 2021
221 posts
trophy 315Jul 2023
40 posts
trophy 0Jul 2024
18 posts
I would suggest you be sure to have Stream-based APIs for Storage so it integrates well with other .NET APIs and third-party libraries .
You should also have async/coroutine/whatever methods for reading/writing storage, since it looks like the ones you shared are synchronous. If they are called on the game loop thread (I assume any game scripts you write run there by default) with large files, you could get frame drops. Adding async variants will make the calls more complex (you start calling on one frame but finish on another) but developers can use this to minimize stutter.
You should also have async/coroutine/whatever methods for reading/writing storage, since it looks like the ones you shared are synchronous. If they are called on the game loop thread (I assume any game scripts you write run there by default) with large files, you could get frame drops. Adding async variants will make the calls more complex (you start calling on one frame but finish on another) but developers can use this to minimize stutter.
trophy 1305Apr 2021
368 posts
trophy 755Aug 2022
58 posts
Happy to see Dark Descent getting a shout out.
trophy 0Nov 2025
1 post
trophy 230Dec 2022
13 posts
people
Log in to reply
You can't reply if you're not logged in. That would be crazy.