Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Enabling autosave and reloading it later in Sugarcube
Hi,
I'm fairly new to Twine, and I'd like to create a game that autosaves. Ideally it would remember the last place the user was at, and return to that point when the game is reloaded. If that's not possible, then plan B would be for the user to click the Save button to save the last spot they were at, then reload it at a different point.
I've been looking at SugarCube as that seems to have the most robust save mechanism, but it's actually a little too robust for me as I don't need all the save slots. The game will persist when refreshed in the same browser window, but not when loaded into a new browser window. I should say that I am *not* a programmer so I'm having a really tough time figuring out where to make changes in the code. I've taken out the extra slots and changed the sessionStorage to localStorage, but beyond that I'm out of my depths. If anyone can assist me, I'd greatly appreciate it.
I'm fairly new to Twine, and I'd like to create a game that autosaves. Ideally it would remember the last place the user was at, and return to that point when the game is reloaded. If that's not possible, then plan B would be for the user to click the Save button to save the last spot they were at, then reload it at a different point.
I've been looking at SugarCube as that seems to have the most robust save mechanism, but it's actually a little too robust for me as I don't need all the save slots. The game will persist when refreshed in the same browser window, but not when loaded into a new browser window. I should say that I am *not* a programmer so I'm having a really tough time figuring out where to make changes in the code. I've taken out the extra slots and changed the sessionStorage to localStorage, but beyond that I'm out of my depths. If anyone can assist me, I'd greatly appreciate it.
Comments
First: Please, stop what you're doing to the code. Especially, stop screwing around with the storage engines, changing those have ramifications that you likely do not understand and will not find pleasant when you get bitten by them.
Second: SugarCube is fairly configurable. In all likelihood, your stated requirements can be met without editing the header at all. In fact, I'm attaching an example TWS for your perusal that should do what you've said you need. Let me know if you have any questions about, or problems with, it.