You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the tracker for similar issues (including closed ones)
I have provided a detailed example for how this feature should work
I have provided a use case for this feature, e.g. short description/share link of a game you're making and how you'd use the feature in that game, other things you've tried, edge cases, etc. (if applicable)
Feature: I would like a way to mark a level within a section as not requiring completion for that section to be considered completed (and therefore get a check mark against it on the level select screen).
Example: On a particular level, the player can perform an action which causes a goto to run which skips a level. Currently it seems to be the case that including a branching path of this kind means that necessarily the player is not considered to have completed the section the goto took them out from. This makes sense, but it would be nice if there was a way around it.
I propose adding a new keyword optional, which is included on a line of its own in the levels section and means that the next level in the file need not be completed for the section containing it to be considered complete. (However, I'm just as happy with any other solution.)
@david-pfx - I have not, but only because I don't understand how that would help. I thought "win" was used to win the current level? The use-case here is that I want to have a level be never visited without it blocking section completion.
Feature: I would like a way to mark a level within a section as not requiring completion for that section to be considered completed (and therefore get a check mark against it on the level select screen).
Example: On a particular level, the player can perform an action which causes a goto to run which skips a level. Currently it seems to be the case that including a branching path of this kind means that necessarily the player is not considered to have completed the section the goto took them out from. This makes sense, but it would be nice if there was a way around it.
I propose adding a new keyword
optional
, which is included on a line of its own in the levels section and means that the next level in the file need not be completed for the section containing it to be considered complete. (However, I'm just as happy with any other solution.)Use case: This arises in my Thinky Puzzle Game Jam 4 game, which is here: https://auroriax.github.io/PuzzleScript/editor.html?hack=7e747dfbac5b0365fc0d87e89d05b1e3
The text was updated successfully, but these errors were encountered: