Checkpoints in a stat screen?

[ChanceOfFire]

Loading a checkpoint from the stats screen:

It is officially supported by CoG, but someone did report a bug with it a while back, so it is probably not entirely stable. (As of this writing, I was still able to reproduce the bug on the omnibus.)

Restoring checkpoints from the stats screen

Interesting. This appears to be a bug and may be something we need to report to @dfabulich . At least one published HG (Saturnine) allows you to restore checkpoints from the stats screen. I just tried to reproduce this bug on Saturnine on the omnibus, and it seems that the bug is present there as well. People do this because CoG/HG explicitly told us that the system supports it. Check whether *save_checkpoint has happened yet Run some code after restoring from a checkpoint Exclude some …

---

Saving a checkpoint from the stats screen:

I don’t think this feature is officially supported by CoG, and I’m not sure what would happen if you tried to code a checkpoint save in the stats screen. Another HG author did raise this question, but I don’t think anyone was able to answer.

New in ChoiceScript: HTML Exports, Checkpoints, and Achievements

For what it’s worth… I suppose you could use excluded variables to keep track of checkpoint usage. Assign one excluded permanent variable to each checkpoint, and change its value when the checkpoint is utilized. But I haven’t tried this. This would definitely be useful. It would essentially be a save anywhere system, and would only be require writers to code one set of menus for saves to be carried out anywhere. I don’t think it’s possible to do this without the *script command. Closest I …