TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 d5967e8b   
   REPLY: 1:317/3 b4169213   
   TZUTC: -0500   
    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 r   
   nning/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)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 457 616 123/10 131 124/5016   
   SEEN-BY: 129/215 305 153/757 154/10 30 40 50 700 203/0 220/80 90 221/0   
   SEEN-BY: 221/1 6 226/18 30 227/114 201 229/310 424 426 428 452 550   
   SEEN-BY: 229/664 700 240/5832 249/206 307 317 400 261/38 280/464 5003   
   SEEN-BY: 282/1038 292/140 854 8125 301/1 317/3 322/757 335/364 341/234   
   SEEN-BY: 342/200 396/45 633/280 770/1 2452/250 3634/12   
   PATH: 129/215 154/10 280/464 292/854 229/426