Something I just noticed when I was messing with the message list header (ansimlst.ans) was that the MB code works as expected, displaying the name of the current echo I'm reading, but the MG code displays whatever group I
joined last, rather than the one the echo belongs to.

Is this by design or is there any way to display the name of the group that
the current echo actually belongs to?

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)

On 09/18/16, Captain Obvious said the following...

Something I just noticed when I was messing with the message list header (ansimlst.ans) was that the MB code works as expected, displaying the
name of the current echo I'm reading, but the MG code displays whatever group I joined last, rather than the one the echo belongs to.

Sounds like your confusing the two modes to get at Messages: Group & Area or Index. Group & Area show the last Group you joined, when in Index the last Group isn't always going to be the current group though the area will be.
I've noticed that but just think of it as a difference in the way the two possible display modes work. G00r00 may change that in the future, but it is the way it works now. Likely because Index Message reading is new.

--- Mystic BBS v1.12 A31 (Raspberry Pi)
* Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)

On 09/18/16, Captain Obvious said the following...

(ansimlst.ans) was that the MB code works as expected, displaying the
name of the current echo I'm reading, but the MG code displays whatever group I joined last, rather than the one the echo belongs to.

Found what I needed. It's amazing what happens when you rtfm. The code I
needed was MN.

-=>Richard Miles<=-
-=>Captain Obvious<=-
-=>bbs.shadowscope.com<=-

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Shadowscope BBS | bbs.shadowscope.com | Temple, GA (21:1/157)