Sorry, I got sidetracked and forgot to get back to this. I guess I need better examples. I guess one would be if maybe I want to have different groups within a raid do different things but they don't break down into actual "group1, group2, etc", like I want groups 1 and half of group 2 to handle 1 mob and the other half of group 2 and groups 3 and 4 to handle another mob, is there a way to define them all into just 2 groups. (I really wish I could now remember the specific example where this came up...)
I don't really have a good way of doing this, other than a relay group. The other option which I do for the rare time it ever comes up, is make an MCP button with a lot of assists in it to set everyone properly. Such as all g1/g2 assist MA1, then list out the 3 people from G2 you don't want and make them assist MA2. Here is a quick example..
Code:
!c -ass MA1 all -ass MA2 g3 -ass MA2 g4 -ass MA2 G2Toon1 -ass MA2 G2Toon2 -ass MA2 G2Toon3
In this example it does the following in 1 MCP command/button:
Everyone assists MA1 (a toons name - whoever you deem your main assist 1).
Group 3 assist MA2 (again a toons name)
Group 4 assist MA2
Then individually make half of group 2 assist MA2.
So in the end, we have all of g1, half of g2 assisting MA1, and the other half of g2, all of g3 and g4 assisting MA2.
To create this button... this link will explain exactly how to stack commands like this:
https://forums.ogregaming.com/viewtopic.php?f=13&t=328&sid=f78448251806964dd8e2febc4bb27b60
Another issue I often run into, which is actually a completely separate problem, is that I often will have a group grinding xp in one zone and be running a group through another zone and when I'm done with that zone I'll forget about the first group and issue a call to guild hall and accidentally send my grind group out of zone, which triggers their lockout timer. Any way around this one? Can I tell them, "Hey, ignore anything the other group tells you to do?" or "Ignore anyone who isn't in your current zone?"
If groups are on different computers, I would just disconnect the uplinks from each other (usually you use MCP -> Connect to connect them, use MCP -> Disconnect to disconnect them). Then they won't talk to each other.
If it's not that simple, then relay groups is the next best option because you can change them on the fly'ish.
If that isn't an option, then you could technically change all of your MCP buttons to: IGW:${Me.Name}, which stands for 'in group with:MyToonName'. The problem here is, if you then later want it to work on everyone, you'd have to re-modify all your buttons. So I would avoid this option at all costs.
And what exactly are relay groups, anyway? I've tried looking around the wiki and all over the ogre site and still haven't figured that out. This is meant as constructive criticism - I love OgreBot - but even though I have some background in programming, the documentation on the site still seems to assume too much insight into the inner workings of either ogre bot or isxeq2 sometimes. I'll see reference after reference to some thing and even after spending an afternoon looking all over the site I can't figure out exactly what that thing actually is. LOL. I actually learn about quite a lot of the features of ogrebot accidentally because something about them is mentioned peripherally in a discussion about something else.
Relay groups are actually part of Innerspace. Which is why you wouldn't find very much information about them on Ogre wiki. Here is a link:
https://www.lavishsoft.com/wiki/index.php/ISUplink:Relay_(Command)