Proposal: unify story formats into a single modular format

[AP2020C]

Is your feature request related to a problem? Please describe.

No response

Describe the solution you'd like.

Twine currently offers four main story formats (Harlowe, SugarCube, Chapbook, Snowman), each with different syntax, macros, and logic. I'm sure there's a reason for this, but for many users—especially those new to Twine—it causes confusion.

I have a proposal: would it be possible to unify the formats into a single modular format, where advanced features (such as macros, saves, JavaScript, inventories, etc.) can be enabled or disabled according to the needs of the project?

Advantages of a single format:

• Reduced learning curve: less confusion between incompatible syntaxes.
• Greater consistency between projects and tutorials.
• Ease of conversion between simple and complex stories.
• Possibility of gradual growth: a user can start with basic functions and activate advanced ones as they gain skills.

Regarding script syntax, I find it inconvenient to have to use <<>> for each line. I would prefer to open and close the code block and write scripts inside it.

Practical example:

A user could start with a simple story, without macros or variables, and then activate an “advanced” module to manage multiple characters, inventories, saves, etc., without having to change the format or rewrite the syntax.
Well, not “activate” but simply use. If something is needed, use it; otherwise, don't use it.

Thank you for your attention!

Describe alternatives you've considered.

Other programs

Additional context on this suggestion.

No response

Presubmission checklist

• I am interested in working on code that would implement this feature request. (This is not required to submit a suggestion.)
• I have done a search and believe that an issue does not already exist for this idea in the GitHub repository.
• I have read and agree to abide by this project's Code of Conduct.

[klembot]

I don't think this is likely, because each of the story formats has different design approaches and intended audiences, and a version that would serve all those purposes would be very difficult to achieve agreement on. If it did occur, it would be outside the scope of this project. Although Twine has a default format, it otherwise leaves the direction of story format development to the larger community; if there was a superformat, as it were, it wouldn't require any code changes in Twine to use.