I'm trying to figure out how to best assemble content for my nodelist.

At present there's all the info under 'data' and want to move to enable some 'net's to submit updates under 'files'

But at this stage those net submissions are not all coming from nets and will be a mix of me and some nets

How best to set things up when the soon to be external submissions are net 3 and net 4 but I am generating net 1, 2, and 5?

I can keep my net 1 and 2 info under 'data' then set net 3 and 4 under files but can't then pickup with another data entry..

I'm guessing I need to create static submission files for the nets I manage
and move most if not all of those nets to submissions I have to manually copy into the inbound dir for makenl to pick up and process... then I end up with just a files entry with

net1 z21n1
net2 z21n2
net3 z21n3
net4 z21n4
net5 z21n5

It just feels like a pain to do this for the bits I maintain all so I keep
the assembled nodelist in correct order. I did try a test that kept my net
1,2 and 5 info under data and then net 3 and 4 under files but it ended up in that order in the final test nodelist... and that I'm fairly sure is not good :)

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

On 10 Feb 2021 at 05:43p, Nicholas Boel pondered and said...

This is why I haven't done the same thing with Agoranet yet. It really wouldn't be that difficult copy/pasting segments into separate net
files, but I just get grumpy and every time I think about doing it I
find something more fun to do. ;)

Thanks for confirming I am not the only one to feel this way :) Hahahh

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)