New in ChoiceScript: HTML Exports, Checkpoints, and Achievements

[ChanceOfFire]

For what it’s worth…

@Jerieth

Is there anyway to check if the checkpoint exists before I try to load it? For example, let’s say I have 10 chapters in my game, but chapter 8 is optional, and you only see chapter 9 if you took a particular route. Is there a way to check what checkpoints exist and display them as a choice if it does exist? (like selectable_if or just a *if statement within a (*choice) (I know there is choice_saved_checkpoint, but can we check status of other checkpoints?)

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.

@Jerieth

Is there anyway for users to save a checkpoint while looking at the choicescript_stats screen? This would be really useful, but I understand it may be difficult or not work. I just saw you can restore, I just wanted to know if save works as well.

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.

@Jerieth

Anyway to check the date/time of when the *save_checkpoint was made? Or perhaps an easy way to add this to a variable, so maybe users can see Chapter 2 (7/5/2024 11:0 AM) for example.

I don’t think it’s possible to do this without the *script command. Closest I can think of is asking the player to input the date and time when saving.