Basically that. Because on IRC servers that do not give you a fixed value for $network, then it uses whatever you name it. So like if I call a group of servers "IRC1" then IRC1 is the value of $network. However, if it gives the value, say "irchat" then no matter what I call the group, it will be set to "irchat". However, if I use multiple connections to the same IRC server, and I name one "IRC1" and "IRC2", even though they are on the same network, and even if that server provides a value for $network, then I can still know which group was used to connect (as an example, $groupname). So for multi-network capable scripting, I could do something like:
IF $groupname == irc1 { /nick name1 }
IF $groupname == irc2 { /nick name2 }
Could be connected to the exact same server, but along the concept of a $scid / $scon, would have its own group name label for that connection. Perhaps something like $scon(group)
And for logging, the be able to have optionally seperate based on group-name instead of network (or in addition to it).
As far as logging overall, perhaps an 'advanced' option, where a person could build together a string of their own (much like in highlight, you can use $me for matching). That would let someone decide if they want to save logs into directories based on year/month/etc, or using their own variables (identifiers).
Example:
Instead of "L:\IRC\logs\SomeIRC\#room.20030123.log" where SomeIRC is $groupname and #room.20030123.log is obviously the room with the date in it, I could instead of the directory to L:\IRC\logs (still the same) but then for further breakdown, I could have "$network\$groupname\$year\$month\$chan.$date.log" so I would have "L:\IRC\logs\SomeIRC\IRC1\2003\01\#room.23.log" for the filename. Just so you have an idea to how complex a person could make it if they wanted to.