groups.txt

In Mystic groups are dynamic, meaning a base can be a part of a group or not, and it can change based on current circumstances that you define. Its less confusing than it sounds! Group membership is defined by the ACS strings in the base editor:

If you want a base to show in a group, then you need to modify the base's access string (called ACS). So you'll see in each base:

List ACS
Read ACS
Post ACS
Sysop ACS

If you want to add it to group 1, then you'd add g1 to the ACS:

List ACS g1
Read ACS g1
Post ACS g1
Sysop ACS s255g1

If you wanted to add it to group 1 and 3 you'd add (g1|g3) to the ACS because | is a logical OR. You can keep building on it too if you wanted. Here is a overkill example of using the ACS system that goes a bit beyond just grouping:

s20(g1|g3|g6)e1a18fZw0

^^ This says the user must have security level 20, be in group 1,2 or 3, have ANSI graphics enabled, be 18+ years old, have User flag Z turned on, and it
has to be Sunday for the base to be accessible to that user.

It can get as easy or complex as you want, but most people will use relatively simple groupings...

On my BBS I have group 1 named "Global" so it has all message bases in it. I have group 3 as "FidoNet" which has only FidoNet. I put my FidoNet bases in group 1 (the global group) and group 3 (the FidoNet group) and I require the user has security level 20. It looks like this:

List ACS: s20(g1|g3)
Read ACS: s20(g1|g3)
Post ACS: s20(g1|g3)
Sysop ACS: s255(g1|g3)