Skip to content

Expect Ink to fail with error when there is no END, but inky fails silently. #534

Open

Description

@jakesee

Inky version: 0.15.1
ink version: 1.2.0
inkjs version: 2.2.3

Steps to reproduce:

Step 1: Start with this simple start knot

-> start
=== start ===
We have started
-> END

Step 2: Add a gather

-> start
=== start ===
We have started
- -> start
-> END

Step 3: Remove the END

-> start
=== start ===
We have started
- -> start

Issue: Somewhere between step 2 and 3, user expects infinite loop warning, but Inky fails silently. Subsequent changes to the Ink yields undefined Inky error state. Seem Inky becomes confused.

Activity

  1. joningold commented on Jun 30, 2025

    @joningold
    Member

    inky does not contain any infinite loop checking. you have to avoid making them.

    Should one arise, the player will stop rendering output and inky may start to chug, but compilation still continues, so you can break the loop either by deleting the cause of it, or inserting a compiler error. The most efficient way to do that is to type a single ~ on a blank line: this will fail compilation, break the loop, and inky will become fully responsive again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions