Subj : Re: Badareas.lst location
To : Digital Man
From : Gamgee
Date : Thu Sep 25 2025 04:21 pm
-=> Digital Man wrote to Gamgee <=-
DM> Re: Re: Badareas.lst location
DM> By: Gamgee to Digital Man on Thu Sep 25 2025 01:51 pm
> DM> Yes in theory, SCFG could read the sbbsecho.ini file to find whatever
> DM> path/filename the sysop chose to name that file. However, a sysop can
> DM> create/use multiple sbbsecho configuration files (they don't have to be
> DM> ctrl/sbbsecho.ini), so SCFG wouldn't magically know how to find any
> DM> other non-default SBBSecho config files.
> That seems a pretty niche use-case - I'd guess that VERY few sysops are
> using multiple sbbsecho.ini files. If somebody *was*, then yes I could
> see how they might need to type in a new value in the input dialog to
> import that badareas.lst into SCFG. But for the other 99% ...? To be
> fair - I see ZERO reason to change it from the default location anyway.
DM> If a sysop had multiple sbbsecho config files and they all used the
DM> default badareas.lst file path (which seems unlikely), then the sysop
DM> would not need to type in a new value if/when importing that
DM> badareas.lst file into SCFG. I only mentioned the sbbsecho.ini file
DM> issue because it means that desired/expected behavior is that the bad
DM> area file path is pulled from that file automatically, but there's
DM> really no way for SCFG to know what sbbsecho config file path/filename
DM> that SBBSecho is *actually* using.
Okay, understood, thanks.
> I guess my question then is - does the location specified in
> sbbsecho.ini for the badareas.lst file actually make that file get
> created/updated in the location specified?
DM> Yes.
Roger that.
> Or will it always go to ../data ?
DM> No, the path/filename set in sbbsecho.ini is what SBBSecho (or at least
DM> the instance that runs with that config file) will update/write when
DM> messages for bad area-tags are received.
Very good, thank you for the explanation/clarification.
