of course! this is the error i get when, after turning "autoname saves" off in settings, i try to save whichever page i happen to be on:
1 year ago(+1)
Thank you! Okay, that's what I thought it was. I did find this happening on one other game using my template, but not on three others, so I have a feeling it might be Internet-related but I'm still not positive.
This is probably super annoying so I'm sorry, but would you mind copy/pasting your JS file just so I can check it out? Either the whole thing if you want, or just the part starting with //autosaves and ending in //end name saves? Just so I can rule it out completely (I'm way more comfortable with twinescript than javascript so I'm really just spitballing here lol)
don't apologize—you're taking time out to help me on this issue, so thank you <3 here's the autosave + name save JS (if you need more, then i can send you the full file as well):
// autosaves - tag passage 'autosave' to trigger saving
config.saves.autosave = true;
config.saves.isAllowed = function () {
if (tags().includes('noreturn')) {
return false;
}
return true;
};
// end autosaves
// name saves - allows players to change name of save file
Config.saves.onSave = function (save, details) {
if (settings.autoname) {
save.title = State.getVar("$chapter");
} else if (details.type == "autosave") {
save.title = "Autosave";
} else {
save.title = prompt("Enter Save Name:", save.title);
}
}
// end name saves
1 year ago (+1)
Okay! I may have figured it out!! What version of Twine are you using? I just downloaded an older version of Twine and tried my template out and got the error, yay! (Yay as far as hopefully having figured it out haha, boo about it not working on certain versions of Twine lol)
It looks like it's only working for version 2.3.12 and up. I'm thinking that's because Sugarcube was updated to 2.34.1 in that version, so I'm not sure if it's due to Twine being outdated or Sugarcube technically. But I just downloaded the newest version of Twine (2.3.16) and it's back to working so I'm crossing my fingers that you're perhaps running a version older than 2.3.12??
1 year ago(+1)
so sorry for the delayed response! yes, i'm using 2.3.11 LOL, so i guess that's why the error is showing up... time i updated :| thank you SO MUCH for the help <3