Update 25.10.29 : news/update-25-10-29
trophy 1575Apr 2021
217 posts
trophy 2401Sep 2021
16 posts
trophy 1988Sep 2021
248 posts
trophy 325Jul 2023
50 posts
trophy 0Jul 2024
20 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 1375Apr 2021
383 posts
trophy 755Aug 2022
59 posts
Happy to see Dark Descent getting a shout out.
trophy 0Nov 2025
1 post
trophy 235Dec 2022
14 posts
people
Log in to reply
You can't reply if you're not logged in. That would be crazy.