Subj : Re: 'conflicted' files
To   : Black Panther
From : g00r00
Date : Sun Nov 28 2021 10:12 am

 BP> 132x37) After noticing the issue with the 'conflicted' files, I did see

 BP> This is running a slightly older pre-alpha version of Mystic,
 BP> (2021/08/29) so maybe I really need to update... ;) I'm wondering if it
 BP> might be related to the issue that someone else had with being dropped
 BP> to a command prompt when running locally...

You should update but I think they are probably unrelated.  In the case of the 'conflicted' filenaming, there is nothing in Mystic that does any sort of 'conflicted' file renaming so is coming from your OS or other software via editors or during replication, etc.  To make sure my brain isn't completely spacing out I searched the source code for the word 'conflict' but the only mention of it is the 'File Conflicts' setting for BINKP servers.

Can you provide more specifics about which files are being renamed to filename[conflicted].ext?  If you are trying to edit MPL while running/compiling it, maybe the OS is doing it or the editor you are using to edit the source file is doing it when it is not able to save?

.... Evil triumphs when good people do nothing. - Einstein

--- Mystic BBS v1.12 A47 2021/11/24 (Windows/64)
 * Origin: Sector 7 * Mystic WHQ (1:129/215)

.