hello,

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

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)

On 19 Apr 2021, g00r00 said the following...

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.

the behavior is the same for both, but during newscan only. (index reader seems to temporarily change the group so MG displays correctly.. standard reader can't read outside the current group at all except for new scans)

i thought it would work like this:

General Base -> g2 -> SomeNet -> !MG shows SomeNet while newscan is currently in General Base.

(i know.. i already see a caveat regarding my multi-grouped Netmail base.. duno how to handle that other than perhaps matching the message's netmail address to a group name or something)

i've seen other boards include the network name inside the base name.. maybe this is why :) unfortunately that would make the index reader look quite unpleasant i think.

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)

the behavior is the same for both, but during newscan only. (index
reader seems to temporarily change the group so MG displays correctly.. standard reader can't read outside the current group at all except for new scans)

I figured that might be the case - the index reader is there to confuse you! ;)

The index reader doesn't actually use the current user's group, it reads the group data and calculates a list of bases based on that group listing. Its a totally different beast in how its programmed.

The traditional readers work a little different they just "ignore" the group when scanning all groups as opposed to actually changing the users group. I don't think thats the ideal way to do it, and if I redid it in 2021 instead of 1995 I would have it switch groups. I am guessing Renegade used to "ignore" the group instead of switch and thats why I made Mystic work that way too?

There are some ways you can probably get it to work how you want.

If you divide your bases into groups by Network, then you can use the MN code which gives the Network description that is assigned to the message base and that will give you a result similar to what I think you want.

You could also do it with a small MPL script I think too and maybe I can whip up something for you. Or I may just try to see if I can make it join groups whichever seems easier and less probable to break existing setups. Let me know if the MN mci code would work for you and if not maybe we can come up with something for you.

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 19 Apr 2021, g00r00 said the following...

If you divide your bases into groups by Network, then you can use the MN code which gives the Network description that is assigned to the message base and that will give you a result similar to what I think you want.

this works indeed! i had disregarded it because of the wiki description:

MN - Network address of current message base

which to me meant 1:2/3. doesn't seem to be publically editable or i'd fix it right quick.

but, i have to introduce a different issue:

QWK networked bases show as "Local Address" :)

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)

this works indeed! i had disregarded it because of the wiki description:

MN - Network address of current message base

which to me meant 1:2/3. doesn't seem to be publically editable or i'd
fix it ri ght quick.

Thanks for pointing that out. I have updated it to read "network description".

but, i have to introduce a different issue:

QWK networked bases show as "Local Address" :)

Putting me to work again!

I have fixed this and I've just updated the "prealpha" A47 builds that includes this. Please let me know if you encounter any issues with it after you upgrade!

--- Mystic BBS v1.12 A47 2021/04/08 (Windows/64)
* Origin: Sector 7 | Mystic WHQ (1:129/215)

On 20 Apr 2021, g00r00 said the following...

Putting me to work again!
I have fixed this and I've just updated the "prealpha" A47 builds that includes
this. Please let me know if you encounter any issues with it after you upgrade!

you're too kind.. works a treat. thank you!

--- Mystic BBS v1.12 A47 2021/04/20 (Windows/32)
* Origin: cold fusion - cfbbs.net - grand rapids, mi (1:120/616)