also having this error pop up, and from what I can tell, it has to do with something in the way settings is coded, because it pops up again when I hit "reset to defaults" (plus no actual settings options show up above that, though I'm not 100% sure if there are supposed to be any). wish I knew more about coding to fix it, but that's the best I've got, unfortunately :(
EDIT: okay, so apparently the issue lies in the fact that the first "config" line in the template's Javascript section is lowercase - it needs to be capitalized (i.e. "Config") to match the other lines (which are all commented out by default). however, when I did that, it pulled another error after that, and I'm not sure how to fix that one. but that code just controls the ability to trigger an autosave in a certain part of the story, so if you're not attached to that feature/don't require it, you can just comment it out, and the template should otherwise work fine to my knowledge.
second and last edit (lol): I couldn't help myself and just kept digging. apparently this was caused by a Sugarcube update, so the original code was deprecated. so if you still want autosaves, I would remove the original line (config.saves.autosave = "autosave") and replace it with the code below (found someone talking about this issue elsewhere, and someone else linked a section in the Sugarcube Documentation that gives helpful code for this):
Config.saves.maxAutoSaves = 1;
Config.saves.isAllowed = function (saveType) {
if (saveType === Save.Type.Auto) {
return tags().includes("autosave");
}
return true;
};
after this, the template appears to work just fine. the code creates an autosave limit of 1 (you can increase that, but it's recommended to stick to a low number) and makes it so autosaves only occur on passages tagged with "autosave" (you can change that tag if you want). hopefully that works all right (like I said, limited coding knowledge, so I'm just taking from the documentation).