Skip to content
This repository has been archived by the owner on Jun 23, 2023. It is now read-only.

UMAPINFO: Inconsistent behavior when endgame and nextsecret are present in a map #496

Closed
JadingTsunami opened this issue Apr 15, 2022 · 2 comments · Fixed by #497
Closed

Comments

@JadingTsunami
Copy link
Collaborator

In the example map, the blue skull switch is a secret exit and the stone switch is a normal exit.

  1. Choose the secret exit, and the map will restart
  2. Choose the normal exit, and the map will end
  3. If you have used the normal exit at least once, start a new game and choose the secret exit, and the game will proceed to map02
  4. Remove "intertextsecret" from UMAPINFO and the map will end when either the normal or secret exit is chosen.

Recommend to honor "nextsecret" if present, regardless of "endgame" flags.

secret.zip

@NightFright2k19
Copy link

NightFright2k19 commented Apr 18, 2022

Does this mean it will be possible to end a game when leaving a map through regular exit, but continue through the secret exit?

Would this work, then?

MAP MAP15
{
nextsecret = "MAP31"
endpic = "CREDIT"
}
=> Should not end game when going through secret exit (I think it wouldn't even be necessary to define nextsecret if it doesn't deviate from standard behavior).

@rfomin
Copy link
Contributor

rfomin commented Apr 18, 2022

Would this work, then?

Yes, it will work if this PR is merged.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants