REPLY: 1:106/1 c3207bf7   
   MSGID: 1:154/10 64b7f2ac   
   CHRS: UTF-8 4   
   TZUTC: -0500   
   TID: hpt/lnx 1.9.0-cur 2021-05-15   
   Hello ogg,   
      
   On Sun Jul 16 2023 18:27:34, you wrote to Kerr Avon:   
      
    og> I ran nodespy and none of the 4 nodes were in use so no kill ghost   
    og> node option was available.   
      
    og> Additional info, when I run the /W (who's online), I see that I'm on   
    og> node 2 with nobody on the others.  I'm thinking of downgrading to A48   
    og> and seeing if the issue goes away.   
      
    og> I'll keep trying!   
      
   FYI, I just tested this on my Mystic install, and I'm currently sitting on the   
   node screen seeing myself logged into node 1. I'm currently using: Mystic BBS   
   v1.12 A49 Linux/64 Compiled 2023/03/14 06:42:21.   
      
   Then I noticed you were using a newer version, so I upgraded to the latest:   
   Mystic BBS v1.12 A49 Linux/64 Compiled 2023/04/30 11:57:00, and I get the same   
   results. However, I see you're using the Windows 64bit version, so that's the   
   only clear difference I see.   
      
   Before any questions, I telnetted over, and noticed your bot checker; after   
   you hit escape twice, it says: "Detecting terminal emulation: |!botcheck1_2 TE   
   detected." = I'm guessing there's a couple typos there, as it seems you're   
   trying to run something called "botcheck1_2", but using the wrong pipe code or   
   missing something there, and you need a pipe before TE in order for that   
   second pipe code to actually work. Just with that one line, I'm going to take   
   a wild stab at you may have a typo somewhere that's causing this. :)   
      
   Bear with me, I haven't run Mystic on Windows in over a decade..   
      
   How are you running the server (ie: what command line are you using)?   
      
   Do you have any events (see event editor) setup to run on node 1? If so, you   
   may want to try changing those to your highest node number.. and don't forget   
   to restart the mystic server after any changes.   
      
   Do you have a local login ("mystic -l" or something similar) running in the   
   background? Could take a look at your task manager and see if anything odd is   
   running besides one instance of the mystic server itself.   
      
   Regards,   
   Nick   
      
   ... "Take my advice, I don't use it anyway."   
   --- GoldED+/LNX 1.1.5-b20230205   
    * Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 120/616 123/10 131   
   SEEN-BY: 124/5016 129/215 305 153/757 7715 154/10 30 40 50 700 203/0   
   SEEN-BY: 218/700 840 220/90 221/0 1 6 242 360 226/18 30 70 227/114   
   SEEN-BY: 227/201 229/110 112 113 206 275 307 310 317 400 426 428 452   
   SEEN-BY: 229/470 550 664 700 230/0 240/1120 5832 266/512 280/464 5003   
   SEEN-BY: 282/1038 291/111 292/854 8125 301/1 317/3 320/219 322/757   
   SEEN-BY: 335/364 341/66 234 342/200 396/45 423/81 120 460/58 633/280   
   SEEN-BY: 712/848 770/1 2320/105 3634/12 5020/400 5058/104 5075/35   
   PATH: 154/10 280/464 221/1 6 229/664 426