"Tibalt's Fortress" location's boss section breaks exit/fav buttons

[Vhati]

Describe the bug On Android in the "Tibalt's Fortress" location of Shandalar, entering the penultimate section (with Tibalt at the bookshelf: tibalt_f4.tmx) breaks the "exit to map" button. The button presses & releases & makes a click sound, nothing more. In earlier sections, it worked, but returning to them doesn't un-break the button. After defeating Tibalt and climbing the ladder to the roof, the button still doesn't work.

The favorite location button also does not work there (checkmark on the button doesn't toggle). Hamburger, deckbuilder, inventory, and quest buttons do work.

Maybe related to this line? I'm not familiar with Forge code.

<property name="preventEscape" type="bool" value="true"/>

Not sure what the intent for that boolean was here. Tibalt just stands still, and there are two exits you can walk to (portal and stairs).

To Reproduce

1. Visit the "Tibalt's Fortress" location.
2. Fight your way to the Tibalt boss section, or take the shortcut portal to the boss section if you've been there before.
3. Tap the "exit to map" button".
4. Nothing happens.

Workaround: Take the portal back to the first section and walk out to the map. The button will work again upon returning to the fortress (until you reach the boss section, which breaks it again).

The way this bug lingers is reminiscent of how other multi-section locations, like the Aerie (aerie_4.tmx), introduce a ubiquitous starting card in later sections, which stays in effect when backtracking to earlier sections.

Operating System 2.0.07-snapshot-10.13 on Android 15.

[Vhati]

Another affected location: "Frostbitten Cavern" also breaks exit/fav.

Both the outdoor section (frostbitten_cavern_0.tmx) and cave section (frostbitten_cavern_1.tmx).

Both sections have preventEscape set to true.

Again, escape isn't actually prevented. One can still reach the map by walking out. It's just an inconvenience for no clear reason.

[github-actions[bot]]

This issue has not been updated in a while and has now been marked as stale. Stale messages will be auto closed.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.