TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 9d451087   
   REPLY: 6480.mystic@1:103/705 24d24b66   
   TZUTC: -0400   
    AG> i suppose i could also automate the creation of msg_editor.c80x24.ini   
    AG> through ms g_editor.c80x100.ini or whatever but :)   
      
   If you wanted to do dynamic per-user instead of creating supported screen   
   sizes what I would do is have a script that creates them if they don't already   
   exist (when the user calls in).  I realize that may not be ideal so I have a   
   few other ideas that I was experimenting with:   
      
   - Run MPL script on load and every redraw so you can define coordinates and   
   paint whatever you want using scripting.   
   - Some simple inline scripting when defining coordinates that looks something   
   like: {2+(WinSizeX/2)}   
      
   Mystic will select the largest it can use for each user and BBS terminals   
   usually have a specific screensize like 80x24 or 132x36 though, so for most   
   situations just supporting the common resolutions within your templates will   
   work pretty good for end users.  To do it dynamic will of course require some   
   sort of minor scripting though if I am going to continue to put all of the   
   visual power in the SysOp's hands.   
      
   --- Mystic BBS v1.12 A47 2021/04/01 (Windows/64)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 19/10 90/1 105/81 106/127 120/340 457 123/10 131 129/215   
   SEEN-BY: 129/305 153/757 154/10 30 40 50 700 203/0 220/80 90 221/0   
   SEEN-BY: 221/1 6 242 360 226/30 227/114 201 702 229/101 310 424 426   
   SEEN-BY: 229/452 550 664 700 981 1016 1017 230/0 240/5832 249/206   
   SEEN-BY: 249/307 317 400 280/464 5003 282/1038 292/854 317/3 320/219   
   SEEN-BY: 322/757 335/364 342/200 423/81 633/0 267 280 281 410 412   
   SEEN-BY: 633/414 416 509 640/1138 1321 1384 712/848 770/1 3634/12   
   SEEN-BY: 4500/1   
   PATH: 129/215 154/10 221/6 1 640/1384 633/280 229/426