Commit 9ac7335f authored by Rob Swindell's avatar Rob Swindell 💬
Browse files

Detect/display menu files, even if only a .ans version exists

I'm so tired of this 30 year old frequently asked question.

If a sysop really wants their Synchronet BBS to only work correctly for ANSI users, I suppose that should be their prerogative.

I always felt that by not detecting/displaying menu files when the minimum set of files was not present, I was helping sysops to identify an issue with their system (which would not work correctly for non-ANSI users). *And* I always felt that having a single menu/display file that correctly supported both ANSI and non-ANSI users was a nice convenience (who really wants to maintain multiple versions of their menu files?). But I'm so tired of answering this question, I just give up.

Hopefully this doesn't break anything for anyone. <shrug>
parent e3ba2427
Pipeline #2928 passed with stage
in 9 minutes and 46 seconds
......@@ -290,10 +290,11 @@ bool sbbs_t::menu_exists(const char *code, const char* ext, char* path)
return fexistcase(path) ? true : false;
/* Either <menu>.asc or <menu>.msg is required */
/* Either <menu>.asc or <menu>.msg or <menu>.ans is required */
if(ext == NULL)
return menu_exists(code, "asc", path)
|| menu_exists(code, "msg", path);
|| menu_exists(code, "msg", path)
|| menu_exists(code, "ans", path);
char prefix[MAX_PATH];
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment