[snip]
- Feb 17 21:13:44 EXEC AutoHatch
+ Feb 17 21:13:44 Process: Auto Hatch
+ Feb 17 21:13:44 Auto hatch in Base #5: MYSTIC_SPELLCHECK_V2.ZIP
+ Feb 17 21:13:44 Auto hatch in Base #5: XQ-FSX.ZIP
+ Feb 17 21:13:44 Auto hatch in Base #9: GDYNSRC.ZIP
+ Feb 17 21:13:44 Auto hatch in Base #9: GDYNWIN.ZIP
+ Feb 17 21:13:44 Results: Hatched 4 file(s) in 0.00s
[snip]

I used this as a test .ini

[snip]

file=fsx_mutl | MYSTIC_SPELLCHECK_V2.ZIP | MYSTIC_SPELLCHECK_V2.ZIP
file=5 | XQ-FSX.ZIP | XQ-FSX.ZIP
file=FSX_DOOR | GDYNSRC.ZIP | GDYNSRC.ZIP
file=9 | GDYNWIN.ZIP | GDYNWIN.ZIP

[snip]

All seems fine. I had to run the FileToss stanza also to get them
actually hatched. Do you think that should be necessary or rather should
that process just run as part of the AutoHatch stanza? I'm not sure
which is best/better?

Also wanted to check on a couple of things?

Does case matter of any thing specified in the .ini file? I'm picking it's
a no.

How many files can be added and hatched in a single AutoHatch? I can't recall what the limit is/was?

Best, Paul

--- E:avon@bbs.nz ------ W:bbs.nz ---
--- K:keybase.io/avon --------------

--- Mystic BBS v1.12 A43 2019/02/15 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

All seems fine. I had to run the FileToss stanza also to get them
actually hatched. Do you think that should be necessary or rather should that process just run as part of the AutoHatch stanza? I'm not sure
which is best/better?

That is intentional, it just queues them up to toss the next time FileToss is executed, which is in line with how the hatch function inside of the BBS
works as well.

I think what I might do is have AutoHatch create the file.out semaphore,
which it is not doing, but I wasn't planning to have it run FileToss directly.

--- Mystic BBS v1.12 A43 2019/02/15 (Linux/64)
* Origin: Sector 7 (21:1/108)