I was thinking more about the TEMP path cleanup that was proposed.

Why not just make it a path assignment like data, themes, etc -- and default
it to Mystic's home directory for those who do not want to re-write their
door scripts?

And for new installs, make it /mystic/temp?

That way you can provide a gentle migration for those who don't want to
change yet ... and still provide the directory cleanup for those who want it.

-roovis

--- Mystic BBS v1.12 A46 2020/03/07 (Linux/64)
* Origin: w0pr.win (21:4/165)

Why not just make it a path assignment like data, themes, etc -- and default it to Mystic's home directory for those who do not want to re-write their door scripts?

The restructure looks like this:

<temp>\1\
<temp>\mutil\
<temp>\2\

So its not quite compatible with the existing:

\temp1\
\temp2\
\temputil\

I suppose I could change that restructure to be like this:

\temp\temp1
\temp\temp2
\temp\temputil

And then something like that could work, but that sort of bothers me having those "double" temp directories

--- Mystic BBS v1.12 A46 2020/03/10 (Windows/64)
* Origin: Sector 7 (21:1/108)

\temp\temp1
\temp\temp2
\temp\temputil

And then something like that could work, but that sort of bothers me having those "double" temp directories

What about \temp\node1 ?

I'll still probably symlink to \temp1 regardless (so as not to break my doorgames hehe).

--- Mystic BBS v1.12 A45 2020/02/18 (Linux/64)
* Origin: monterey bbs (21:1/168)

What about \temp\node1 ?

I'll still probably symlink to \temp1 regardless (so as not to break my doorgames hehe).

For now I am just going to not change it. :)

But symlinks would be a great way for me to be able to change it without breaking people's setup. But it requires everyone then to create the links
(or maybe the upgrade could do it).

--- Mystic BBS v1.12 A46 2020/03/10 (Windows/64)
* Origin: Sector 7 (21:1/108)