I use the nodelist_handler.js in my tickit.ini for nodelists received within archives and it works great.

However, suppose I am now receiving a nodelist that is *not* within an archive, and is just the plain, uncompressed nodelist itself. It seems the handler script isn't designed for that unless I'm overlooking something really obvious (which is likely).

Do I need to write my own handler script to simply copy and replace the old nodelist file with the incoming one?

<codeŸenix>

---
þ Synchronet þ -=[ conchaos.synchro.net | ConstructiveChaos BBS ]=-
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Thu, 19 May 2022 09:43:49 -0400
"Codefenix" <codefenix@VERT/CONCHAOS> wrote:

I use the nodelist_handler.js in my tickit.ini for nodelists received
within archives and it works great.

However, suppose I am now receiving a nodelist that is *not* within
an archive, and is just the plain, uncompressed nodelist itself. It
seems the handler script isn't designed for that unless I'm
overlooking something really obvious (which is likely).

Do I need to write my own handler script to simply copy and replace
the old nodelist file with the incoming one?

Just leave out the match portion of the HanderArg


[SN_NODELIST]
Dir=SPOOKNETNODELIST
Handler=tickit/nodelist_handler.js
HandlerArg={"domain":"spooknet", "nlmatch":"spooknet.*"}
Forcereplace = true
--
End Of The Line BBS - Plano, TX
telnet endofthelinebbs.com 23
---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Re: How to handle unarchived nodelists
By: Nelgin to Codefenix on Thu May 19 2022 10:55 am

Just leave out the match portion of the HanderArg

Ah, ok. Thank you. I didn't realize the match setting could be omitted. I'll try that and see how it goes.

<codeŸenix>

---
þ Synchronet þ -=[ conchaos.synchro.net | ConstructiveChaos BBS ]=-
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)