TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 557d89c1   
   REPLY: 1:317/3 4369a467   
   TZUTC: -0500   
    BP>  g0> If you have a display file that is not saved at unlimited line length   
    BP>  g0> then youwill have this issue, so that is my guess as to why you are   
    BP>  g0> seeing this.  Linesare counted by linefeeds saved in the actual file,   
    BP>  g0> if you don't save theANSI with unlimited line length (ie ANSImation,   
    BP>  g0> etc) then it will notaccurately pause during display.   
    BP>    
    BP> Can the pause prompt still be changed with the RP## control code?   
    BP> That might be an option.    
      
   You can do that but I don't think it would fix anything.  If you want the   
   screen to pause in a scrolling ANSI it just needs to be saved with unlimited   
   line length (0 in Mystic's ANSI editor) so each line in the actual ANSI file   
   is one line as displayed.  If the cursor is moving around via location codes   
   or auto wrapping, then the line count won't be accurate.   
      
   I could probably improve on this in the future, its just worked this way for   
   20+ years.   
      
   I think most people turn pausing off for scrolling ANSIs and/or use baud rate   
   emulation and in the few cases where the pause is desired it just has to be   
   saved a certain way.   
      
   I'll make a note of it in the TODO to look at changing the logic.   
      
   --- Mystic BBS v1.12 A47 2020/11/06 (Windows/64)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 120/10 340 123/131 124/5016 129/215 305   
   SEEN-BY: 154/10 30 40 50 700 203/0 220/80 221/0 6 226/30 227/114 201   
   SEEN-BY: 227/702 229/101 275 310 424 426 452 550 664 981 1016 240/1120   
   SEEN-BY: 240/5411 5824 5832 5853 6309 249/206 317 400 280/464 5003   
   SEEN-BY: 292/854 8125 317/3 320/219 322/757 342/200 396/45 633/280   
   SEEN-BY: 770/1 2452/250 2454/119 3634/12   
   PATH: 129/215 154/10 280/464 240/5832 229/426