Subj : Re: Theme/prompt fallbacks and their variables in theme.ini
To   : Bj”rn Wiberg
From : g00r00
Date : Sun Jul 04 2021 09:31 am

 BW> The values of the Prompt, Text, Menu and Script variables (at least as
 BW> displayed by the Theme/Prompt Editor) seem to override any values of the
 BW> Def_Prompt, Def_Text, Def_Menu and Def_Script variables.

Prompt, Text, Menu, Script all define a theme to inherit from if any of those items are missing from the current theme you're editing.

Def_Prompt, Def_Text, Def_Menu and Def_Script define whether or not to inherit from whatever theme you configured in System Configuration as your default theme if items are missing from the current theme or the theme you've selected for inheritance.

So if you have "my_new_theme" and you want to inherit any missing menus from "another_theme" then you would set Inherit Menu=another_theme so any menu that cannot be found in my_new_theme will now try to load from "another_theme".

Then if "another_theme" doesn't have the menu, if you have def_menu=true then Mystic will look to see what you have configured as the default theme and then look in that theme for the menu.

If you edit in the theme/prompt editor and not the ini it might be more clear as to how it works as there are descriptions that explain what it is doing.  The prompts editor will also tell you exactly where it sources a prompt from (theme, inherited theme, default theme, or system prompts) when you use that too.

For scripts, templates, text, and menus the load logic is this:
Theme then Inherited Theme then Default Theme (if enabled) then Nothing

For prompts its:
Theme then Inherited Theme then Default Theme (if enabled) then System Prompts

.... Don't sweat the petty things and don't pet the sweaty things

--- Mystic BBS v1.12 A47 2021/07/03 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.