(Using SugarCube v2.12.1, working on a team IF project)
The stock Settings API dialog couldn't handle the amount of content settings we needed without it turning into an ugly beast. We instead built a nice, user-friendly menu with CSS in a story passage named Settings. This works great, with one exception: navigation.
We want to use the UIBar API to handle the Settings button, but we don't want the Settings API to manage the menu. Instead, when the user clicks the Settings button, we just want it to go to the passage exactly like a regular story link would, keeping the 'return' functionality intact.
After toying with things, we figured out how to turn the settings button on without having Settings API objects, by bypassing the check:
However, actually putting in the detour is beyond our team's expertise. Can anyone suggest an approach?