Subj : .tic handling
To   : All
From : deepthaw
Date : Tue Nov 17 2020 09:56:54

Hi all,

Thanks to some top minds on here I realized I was an idiot and was using a packet password when none was needed, and after a night full of finally realizing synchronet's binkit was still running and that's why binkd wasn't working and... well, my networks work now.

Having some issues with incoming .tic file handling however. Here's the error from my log:

"level":50,"error":"Invalid: No local area for \"Area\" of FSX_MUTL","reason":"No local area for \"Area\" of FSX_MUTL

Here's the config from my conf.hjson (irrelevant stuff trimmed out):

storageTags: {
		    weekly_nodelists_fsx_net_etc__fsx_node: FSX_NODE
            weekly_infopacks_fsx_net_etc__fsx_info: FSX_INFO
            mystic_bbs_software__fsx_myst: FSX_MYST
            mystic_bbs_utils_mods_etc__fsx_mutl: FSX_MUTL
            bbs_software_current_legacy__fsx_soft: FSX_SOFT
}

(then within areas)

			mystic_bbs_utils_mods_etc: {
                name: Mystic BBS Utils, Mods etc.
                desc: Mystic BBS Utils, Mods etc.
                storageTags: [
                    mystic_bbs_utils_mods_etc__fsx_mutl
                ]
            }

(finally ...)

ticAreas {
		
	FSX_MUTL: {
			areaTag: mystic_bbs_utils_mods_etc
			storageTag: mystic_bbs_utils_mods_etc__fsx_mutl
			hashTags: fsxnet,mystic,mods
        }
}

the filebase isn't catastrophically misconfigured since I was able to upload about 9,000 files into it and all of my areas for tic files are browseable, if empty. I imagine it's something simple like all my mistakes so far, but I'm just overlooking it.

--- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.0)
 * Origin: cortex (21:2/128)

.