SugarCube disabling saving with an alert. about twine-cookbook HOT 7 CLOSED

I agree that Harlowe (and Snowman) doesn't have an equivalent to that setting, or a Save UI for that matter, however there is currently a "Saving Games" recipe showing how to implement a primitive Save/Load UI using links.

I believe we implement a new recipe showing "passage tag based save limiting functionality" (similar to this issues) using the Harlowe (and maybe the Snowman) example(s) of "Saving Games", while using this Issue as a bases of the SugarCube implementation.

from twine-cookbook.

SugarCube already does this by calling UI.alert() with the contents of the localized string l10nStrings.savesDisallowed. If it's not showing up, then that's an issue for its tracker, not a recipe for the cookbook.

EDIT: It's entirely possible that I broke it at some point when fiddling with the Dialog API.

Also. Please do go ahead and create an issue. Due to health issues, my computer time is still woefully limited at this point and it's time for me to turn back into a pumpkin.

from twine-cookbook.

It's possible that I started using this code prior to that implementation? Or it was broken when I started using SC, abut who knows how long ago that was now. I don't know that I've checked it without that code, variations of it are part of my boilerplate, so to speak. I'll double check it, though, and open an issue at your repo if it doesn't behave as expected.

Thanks for the info. I suspect that I just never checked outside of whatever version I was running when I needed this code.

from twine-cookbook.

@ChapelR: I won't re-open this issue, but I am going to add a note to write an entry on disabling the default save functionality in SugarCube. We aren't covering that currently, and I'd like to make sure we have something on that. Thanks for submitting this and sparking the idea for another entry!

from twine-cookbook.

from twine-cookbook.

@tmedwards
This suggested recipe did two things, and If I understand the previous comments correctly you are stating that point 2 should automatically occur:

1. Conditionally disabled saving based on the tags assigned to the current Passage.
2. Displayed an alert to let the end-user know they can't save while isAllowed is false.

Isn't the functionality of point 1 still a valid reason for implementing this suggestion (excluding the notification part) as a recipe? Or am I misunderstanding something?

from twine-cookbook.

Frankly, using passage tags is probably the most obvious (and common) way to use Config.saves.isAllowed—I know I've given the example before. I'm not sure it's either uncommon or unique enough to require a cookbook entry. Certainly, it never occurred to me at the time.

I suppose a case could be made that Config.saves.isAllowed itself could use an entry, however, it's SugarCube specific enough that, again, I'm unsure it deserves an entry. I mean, there's no real analog in any of the other story formats. Are we doing single story format recipes now?

Regardless. I'm not against it if the consensus is that Config.saves.isAllowed would make for a good candidate for an entry. It's entirely possible I cast too broad a net.

from twine-cookbook.