Players often find themselves playing a scratch game, and they work so hard in the game to get to a certain point in the game where they just get bored of it and exit from the game and thinking they can come back later to play it again from the exact point they left off. But Scratch has no save systems, nothing that allows a player to save their game and allow them to get back on that project with the same data they left with.
Solution: Data persistence.
Data persistence is great for many games, players will work hard for something with the knowledge that they can leave at a save point with all their items/place they're on.
I know it may be a little difficult to put onto scratch, but it would be well worth it for the communities' projects.
Offline
jvvg wrote:
In Scratch 2.0, they are implementing cloud variables, and I think that this can be accomplished with that.
Yes, but that would take some work.
Offline
ImagineIt wrote:
jvvg wrote:
In Scratch 2.0, they are implementing cloud variables, and I think that this can be accomplished with that.
Yes, but that would take some work.
Not really, store in separate lists the settings when the user left and the user ID (which would be easier with multi-dimensional lists...), then just access the data through the user ID block
Offline