-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow link destination to be defined in rule instead of LEVELS section #81
Labels
enhancement
Improvement to existing capability
Comments
Nice idea. I actually started out going in this direction, but switched tracks to avoid having a rule for each possible level. Having both looks (a) useful and (b) easy.😁 |
Would
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm suggesting an optional argument to the
link
rules commandlate [ Player links ] -> link
is the current implementation, and triggers the link, sending you to the level defined in the LEVELS section
late [ Player links ] -> link levelname
would trigger the link, sending you to the level called
levelname
even if the current level doesn't have any links defined in the LEVELS sectionUse case: I made a game with PuzzleScript Next with lots of levels, many of which are quite hard. The ideal structure for this game would be a hub world which lets you play them in any order, but doing this in the LEVELS section would mean having 20 unique objects, which feels a bit unwieldy. Doing it in a rule would potentially be a bit simpler, i.e. I could put the level entrances in a line and do something like this:
The text was updated successfully, but these errors were encountered: