AG> during new message scan, i've noticed that !MB correctly follows the
 AG> current mes sage base while reading (shows correctly in ansimrd header)
 AG> but !MG seems to sti ck to the user's current group regardless. is there
 AG> a trick to get that to updat e correctly?

A group can be anything in Mystic: doors, menus, files, and anything can be a member of many different groups.  There isn't one group that a message base belongs to that could be displayed (which is what I think you're looking for).

The MG code shows the current group so it sounds like its working like it should.

Are you reading through the ANSI reader/index reader, or standard reader?  Maybe I can take a look and see if there is something I can do to make this work they way you want.

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/64)