Category: Raid Mods
Addon Information
Works with 3.2
Download Latest Version.
To add favorites please register for a free account. If you already have one you need to login. How do I install this? (FAQ)
Author:
Version:
2.5.9
Date:
10-02-2009 10:13 PM
Size:
66.02 Kb
Downloads:
10,349
Favorites:
69
MD5:
Pictures
Click to enlarge
Auto-Arrange button
Click to enlarge
"More"
Click to enlarge
EZ Template Editor
Group O Matic   Popular! (More than 5000 hits)
(If you use GOM, you might be interested in http://www.wowinterface.com/download...idStarter.html, --currently beta -- which will auto-invite the people in a saved raid and then restore that raid.)

NOTE, Usability in combat: Addons cannot modify the raid arrangement in any way while their client is in "combat lockdown." However, if your raid is able to keep a 26th/11th member (of any level) out of the instance, see the optional files tab here for a plug-in that allows you to route GOM's server requests through that person (meaning only they need to be OOC).

Group O Matic is a tool for raid leaders. It does the following:

*Gives you the ability to save and restore raid member positions
*Gives you an auto-arrange command, which tries to find the best group arrangement based on class/spec, and then automatically arranges the raid to match it.
*Adds slash commands to swap raid members' groups (for macros to move people on the fly)
*Auto-arrange template for AB/EotS which will move people at the same node into the same group.

If you want to configure GOM while not in a raid, use /gom active

-------------------------------------------
GOM has more settings than you would normally find in an addon of this type, but it also works "out of the box." That is, it will work as well as/better than any other raid config addon without changing anything, and will give you a simple save/restore/auto window when you open the raid UI.
If you do want to manipulate the way the auto-arrange and restore functions work then read on for some basic documentation. If you have more specific questions just post them in the comments here.
-------------------------------------------

* Macro Commands:
/rs Name1 Name2
(Swaps two people)

/rgs Group#1 Group#2
(Swaps two groups with each other)

/rm Name Group#
(Moves Name into Group#)

/rm Name @Group#
(Moves Name into Group# even if Group# is already full, in which case it swaps a random person into Name's old group)

/rm Name1 Name2
(Moves Name1 into the same group as Name2)

/rm Name1 @Name2
(Moves Name1 into the same group as Name2 even if Name2's group is already full, in which case it swaps a random person into Name1's old group)

Names can be replaced with !p, !t or !f for player, target or focus, i.e...
/rs !p !t would swap you with your target.
/rm !p @!f would move you into the same group as your focus, even if that group is full.

-------------------------------------------

*Raid Save and Restore:
Restore will try to get the current raid as close as possible to the saved raid. By default, if there are people missing they will be ignored, and if there are extra people they will be auto-arranged -- these settings can be changed in the "Manage Saves / Restore Options" pane.

*Raid Restore Options:
As mentioned above, there are several restore modes that you can choose from. The options are in the form Part1-Part2 where Part1 is what to do with missing players, and Part2 is what to do with new players...

Part1 can be:
--Dumb: Players from the saved raid who are absent from the current raid are ignored.
--Smart: Players from the saved raid who are absent from the current raid are compared to new players who aren't in the saved raid. Any new players that have the same roles as the absent players are filled into their spots.
--Armchair: Same as "Smart" but substitutions are based on class rather than roles.

Part2 can be:
--Merge: New players (who aren't substituted for a missing player) are auto-arranged based on the currently selected template.
--Separate: New players (who aren't substituted for a missing player) are pushed into the lower groups for manual arrangement.

-------------------------------------------

*Auto Arrange:
Automatically sets up the raid, taking into consideration class and talent spec, based on either one of the built-in rulesets or a user-created template. Anyone whose talents are unknown will have defaults filled in by class.

*Talent scanning/caching:
GOM saves a list of the roles of players whose talents it has scanned. Scanning happens when you click auto-arrange, or slowly over time (while not in combat) if you have checked "Continuous Scan" -- Addons can only scan talents of players within ~40 yards, so it's best to just leave "Continuous Scan" on all the time, so that your database of roles is current (assuming that you are using features that take talents into account).
Also, GOM will only cache players' talents who are in their primary spec. It will still read and use secondary talents if it has directly confirmed that a player is using them during the current raid. But, if it hasn't scanned a player during the current raid, it will assume that they are using their primary talents. You can change this behavior, so that it will assume they are using the last spec it saw them using, with /gom secondarytalents

*Auto Arrange Templates:
GOM supports user-created templates to modify how the auto-arranger behaves. If you want to create one, see the EZ Templates tab (or for advanced templates, templates.lua).

*AB/EotS template:
Note that using the auto-arrange with this template will probably only be useful to you if you're in an AB/EotS game that is in-progress. It scans all raid members' current sub-zone ("mine", "stables", etc) and groups people at the same place together. Remember that GOM can't work while *you* the raid leader are in combat, but it doesn't matter if other people are, and you can macro /gom auto and hit it when you have a few seconds OOC.

-------------------------------------------

*Group Exclusions:
You can exclude any/all groups from being saved/restored/arranged. Excluded groups will not be modified at all by the addon (the exception is the AB/EotS template, which intentionally ignores this setting).

*Dead/Lowbie/Offline player handling:
GOM can optionally be configured (in the Extras menu) to push dead, offline and/or lowbie (below the level of your choice) players into the lower groups. This works for auto-arranges normally. For raid restores, it only applies to players who would otherwise be "merged" (i.e. players that are not in the save, but are in the current raid). If you have a lowbie player that you accidentally saved into a raid, remember that you can edit them out in the "raid options" Extras menu. You can also exclude groups from being saved, if you want.

*MVPs:
You can create a list of MVPs which the auto-arrange will look at first when arranging groups. Class and spec are valued over MVP status, but among players with the same class and spec, MVPs will be placed in the top groups first.

*Throttling:
You can change how many requests GOM sends to the server at a time while moving groups around. Setting this to a lower number can resolve issues that happen to some people due to high latency connections or other addons. The default setting almost always works fine; but if you're having problems while using GOM, this is something you can do to troubleshoot it.
  Change Log - Group O Matic
2.5.9 (10-2-09):
-Added a button to clear cached talent and "sync" data.
-/gom cancel will no longer output text if it didn't cancel anything.
-GOM will now compensate if groupomatic.xml doesn't load -- The point being, if you don't want the GUI you can just delete that file or remove it from the ToC.

2.5.8 (9-7-09):
-Added some fade-in effects to the GUI, because I like it that way. If you don't, you can do /gom fading to toggle it.
-Changed the wording of some text.
-Other minor tweaks.

2.5.7 (9-5-09):
-Hackish fix for ridiculous Blizzard bug in message()

2.5.6 (8-4-09):
-Updated for WoW 3.2
-Various minor changes/fixes.

2.5.5 (7-15-09):
-Fixed a minor, harmless bug that I introduced in 2.5.4. GG testing. >.>

2.5.4 (7-14-09):
-Re-enabled the ability to toggle on debugging output (/gom debug)
-The "bad template syntax," etc. errors (anything that would be output because of a badly written 3rd party template) that were being output as debugging text are now output properly as "error" text.
-A couple of other things that should be output even if "Silence Console Output" is checked are now considered errors and therefore will ignore that checkbox.
-Added some smart debugging output in the case of a talent scan failing. This system is vulnerable to latency and addon conflicts.

2.5.3 (7-13-09):
-Fixed a fatal error that occured when the first auto-arrange or raid restore done after loading GOM was started while GOM was in the middle of a "Continuous Scan" which had been delayed for some reason (latency, addon conflict, etc.)

2.5.2 (6-22-09):
-Misc. minor fixes/changes.
-Fixed a (harmless) bug that was generating a Lua error on new characters...oops.

2.5.1 (6-5-09):
-Improved memory management substantially.
-Added about 2/3 of the "BUFFER" roles back in that I removed in some of the earlier 2.x versions.
-Played around with the default PvE template a bit.
--If you like/dislike the way this changes how auto-arranges act, let me know.

2.5 (5-30-09):
-Added options to push dead/lowbie/offline players to the lower groups...see the wowi description page (towards the bottom) for more info.
-Tweaked a couple things so that auto-arranges/restores go faster in certain (rare) situations where they were going pretty slow.
-If GOM is being run for the first time on a character, "Continuous Scan" will now default to being on.
-Changed some text around.

2.4 (5-8-09):
-Fixed the 3.1 incompatability that was causing neverending raid arranges.

2.3.1 (5-1-09):
-Reduced the time between raid moves back down to the original 0.3 seconds.
-Added some smarter code to try to deal with the infinite looping problem.

2.3 (4-30-09):
-Increased the time between raid moves to compensate for what seems to be a really stupid design change in GetRaidRosterInfo. >:0
--Hopefully that will fix the infinite looping problem.
-Updated the talent scanner for 3.1.
-The scanner will read and use but NOT cache the talents of players who are using their secondary spec, unless you tell it to (see note on the wowi page)
-Minor text updates, etc.

2.2 (2-24-09):
(Only updates the /rm command, you don't need this if you don't use /rm)

- /rm can now take an @ in front of its second argument, which forces it to move the player to that group even if the group is full. It will pick a random member to swap to name1's group in this case.
--i.e. /rm Jim @1 will move Jim to group 1 even if it is full, and if it is full will move someone from g1 to Jim's group.

- /rm can now take a name (or !p !t or !f, same as the other <name> arguments) as its second argument. If you pass a name (or wildcard) to the second argument, it will move name1 into the same group as that person. If the group is full, it will do nothing UNLESS you put an @ in front of the entire argument in which case it will swap name1 with a random person from name2's group (other than name2 of course)
-- i.e. /rm !p @!t will move you into the same group as your target, even if that group is full

2.1.3 (2-10-08)
-Updated the talent interpreter (lol).
-Optimized some frame creation code/memory management.

2.1.2 (11-2-08):
-Possible bugfix for GOM ignoring the "Show GUI" toggle if the UI is loaded while the player is in a raid.

2.1.1 (10-25-08):
-GOM now has a pretty good chance of not tainting the portrait focus menu-items each time it loads
--i.e. UIDropDownMenu_Initialize recoding so that it isn't called until well after the UI loads
--but, it still can sometimes...like if you try to do a restore/save really soon after load
--it's really blizzard's fault which is why so many addons do this post-3.0
-Also...fixed a typo in the error text for bad argument syntax to the decursewhich scripted template command (which no one will *ever* see let alone care about a typo in it...but meh)

2.1 (10-17-08):
-Various bug fixes
-GOM now keeps a list of players' classes independant of its list of specs, this list is updated regardless of the "scan" settings and stores the class of everyone that you join a raid with...this list is used for the following two changes:
-Added class info to the saved raid edit screen
-Added "Armchair-xxx" restore modes, which act like "Smart-xxx" except that they match by class rather than spec if the exact player isn't in the current raid

2.0 (10-14-08):
**General:
-Updated for WoW 3.0
-GOM's buttons are blue now ^-^
-Removed all use of the addon channel (ping/update checks/syncing talents with other raid members running GOM) which probably no one used, and which used a small amount of CPU time even when idle.

**Slash Commands:
-/rs and /rm can now take !t !p or !f (target/player/focus) instead of a name.
--i.e. /raidswap !t !p would swap you with your target

**Auto-Arrange:
-Removed both built-in PvE Auto Arrange Templates
-Added a new "Default PvE" template (WIP, but raid arrangement is a much simpler problem in WoW 3.x)
-The "Continuous Scan" option will no longer prevent you from starting a restore/auto-arrange while it is scanning
-EZ Template class/spec menus can now be localized
--enUS/default localization means that those menus are more natural now in English as well("Spell DPS buffer" as opposed to "SPELL_BUFFER", etc.)
-Cached player roles/specs from version 1.x will be deleted, due to the number of changes from WoW 2.x

**Scripted templates:
-Anchors for templates: go, etc. are now able to take an anchor name in place of a line number
-Added "anchor anchorName" command for templates
-Updated special talents, added MANA_BATTERY for surv hunters w/ hunting party, etc.
-Several *_BUFFER roles have been removed because those talents/abilities now affect the whole raid
-Deathknight talent interpretation added
-When trying to find a matching player for a request by an auto-arrange template, GOM will now prioritize players with a different ROLE than an optional prefSpec (but who aren't applicable to be limited by a limits line) over players who are limited by an optional limits line -- before, these two conditions had equal weight
  Optional Files - Group O Matic
File Name
Version
Size
Author
Date
Type
0.1 B6
3kB
10-04-2009 02:59 PM
Addon
1.0
2kB
10-04-2008 12:46 PM
Addon
  Archived Versions - Group O Matic
File Name
Version
Size
Author
Date
2.5.8
65kB
Akryn
09-07-2009 02:40 PM
2.5.7
65kB
Akryn
09-05-2009 04:32 PM
2.5.7
65kB
Akryn
09-05-2009 02:47 PM
2.5.6
65kB
Akryn
08-04-2009 06:49 PM
2.5.5
64kB
Akryn
07-15-2009 08:48 PM
2.5.4
64kB
Akryn
07-14-2009 08:10 PM
2.5.3
63kB
Akryn
07-13-2009 07:18 PM
2.5.2
63kB
Akryn
06-22-2009 11:10 PM
2.5.1
63kB
Akryn
06-05-2009 11:17 PM
2.5
60kB
Akryn
05-30-2009 01:44 PM
2.4
54kB
Akryn
05-08-2009 09:17 PM
2.3.1(v2 -- deb
55kB
Akryn
05-05-2009 07:54 PM
2.3.1
54kB
Akryn
05-01-2009 09:05 PM
2.3.0
54kB
Akryn
04-30-2009 09:56 PM
2.2.0
54kB
Akryn
02-25-2009 12:51 AM
2.1.3
53kB
Akryn
02-10-2009 11:53 PM
2.1.2
53kB
Akryn
11-02-2008 07:44 PM
  Comments - Group O Matic
Post A Reply Comment Options
Old 05-11-2009, 04:40 PM  
Fionn
A Defias Bandit

Forum posts: 2
File comments: 16
Uploads: 0
its working fine thx a lot! )
Fionn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-08-2009, 09:21 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
Bit earlier than I thought. I believe 2.4 should work with WoW 3.1. Unless there's something *else* wrong with it. :P

Throttle settings all the way up to 20 should work fine; although if it breaks, setting it to 1 is always a good troubleshooting step.

Last edited by Akryn : 05-08-2009 at 09:23 PM.
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-06-2009, 11:07 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
Thanks, should be able to fix it now hopefully; although I was kind of hoping that wasn't the problem. It'll probably be the weekend or later before I release a fix; GOM has a lot of code that assumes the raid IDs will stay the same for each person

Last edited by Akryn : 05-06-2009 at 11:08 PM.
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-06-2009, 02:06 PM  
Dridzt
A Frostmaul Preserver
Interface Author - Click to view interfaces

Forum posts: 279
File comments: 409
Uploads: 37
Code:
GOM DEBUG: !!!!!!!!This is fatal, just /gom cancel. Raid index of at least one (non-add/dropped) raid member changed mid-run.
That's from 2.3.1v2 so you got your answer I guess
Dridzt is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-05-2009, 07:57 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
OK I just cleaned up the debugging output so it should only output useful things, turned it on all the time (/gom debug is still there but ignored in this version), added a check to see if the raid IDs changed, and uploaded it as 2.3.1v2. If that comes back saying the raid IDs changed, then that's the problem and I'll fix it.
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-05-2009, 02:05 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
Interesting. It worked for me so there must be something different about the live servers (I don't have an active account at the moment, I don't *really* mind paying $15 to fix an addon but I'd rather not if I don't have to ).

I do have a new thought now though. I wonder if the raid IDs are changing in the middle of the arrange? GOM would behave exactly like it is doing if that's the case, but it would take a pretty major rewrite of the arrangement code to fix. Could someone check on a Bliz server?

Code:
/run message(GetRaidRosterInfo(3))
That should give a name...swap that person with someone else, maybe mess around with the groups some more just in case it takes more than one move, and then run the command again to see if it gives the same name?

Quote:
Originally posted by Dridzt
Sorry for late reply,
I actually tested 2.3.1 the same day but forgot to post back here.

I set throttle to 1 like you suggested in #3.
The perpetual sorts are still happening (problem not solved).

I didn't try with debug on so no further info sorry (will try next time).

Last edited by Akryn : 05-05-2009 at 07:32 PM.
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-05-2009, 04:46 AM  
Dridzt
A Frostmaul Preserver
Interface Author - Click to view interfaces

Forum posts: 279
File comments: 409
Uploads: 37
Sorry for late reply,
I actually tested 2.3.1 the same day but forgot to post back here.

I set throttle to 1 like you suggested in #3.
The perpetual sorts are still happening (problem not solved).

I didn't try with debug on so no further info sorry (will try next time).
Dridzt is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-01-2009, 09:04 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
FYI, the Lua line I gave you actually sets a different throttle that you can't configure anywhere in-game, but it doesn't look like that's the problem anwyay, so nevermind.

Anyway, three things to try that might help...possibly...

1. Try 2.3.1, which has some new code in it that might compensate better for the problem, but is still not tested in a real raid (only with gomtest's simulated raids which work fine no matter how many people are in them :\ )

2. /gom debug (make sure it says "true"), and try again...maybe it will output something useful...?

3. If it still doesn't work with the normal settings, try setting the throttle all the way down to 1 (not in Lua, in the Extras>Throttle setting). If that still breaks then the problem is completely different from what I think it is, and it'll have to wait until I can test in a real raid, probably.

Last edited by Akryn : 05-01-2009 at 09:07 PM.
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-01-2009, 07:23 PM  
Dridzt
A Frostmaul Preserver
Interface Author - Click to view interfaces

Forum posts: 279
File comments: 409
Uploads: 37
Same experience as Fionn.

Talents are scanned properly in 2.3 but the perpetual sorts are still happening.
Dridzt is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-01-2009, 08:16 AM  
Fionn
A Defias Bandit

Forum posts: 2
File comments: 16
Uploads: 0
I ninja invited the guild (17 was online) and tested a bit:

if i insert at the very end of templates lua the in ver 2.3 GrOM.ArrangementFrameUpdateThrottle = 2 then i get:

[14:11:33]ErrBlock: Interface\AddOns\groupomatic\groupomatic.lua:802: attempt to index global 'GOMatic_TalentRequestFrame' (a nil value)

Without the new line it hangs still in a neverending loop in the auto and also in the restore save options, but there is no error (throttle speed was 2). I hope it helps.

Last edited by Fionn : 05-01-2009 at 08:21 AM.
Fionn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 05-01-2009, 07:43 AM  
Fionn
A Defias Bandit

Forum posts: 2
File comments: 16
Uploads: 0
gonna test 2.3 today on raid.
Fionn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 04-30-2009, 10:01 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
Actually, I'll just release 2.3 as it is now. I haven't tested it much yet, but it can't be worse than 2.2 is ATM. If this version fixes the infinite sorting, please let me know.

The advice below is still true, if it's still getting stuck arranging, and you feel like messing with Lua, you can try adding that line. You could also try reducing the throttle setting in "More>Extras>Arrangement Throttle"
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 04-30-2009, 07:33 PM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
OK, that definitely is a change in GetRaidRosterInfo or possibly SwapRaidSubgroup behavior then. I can't really do any testing until the weekend. If anyone wants to help before then (and possibly get it working), could you try putting this line in at the very end of templates.lua...

GrOM.ArrangementFrameUpdateThrottle = 2

Last edited by Akryn : 04-30-2009 at 10:08 PM.
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 04-30-2009, 11:11 AM  
Fionn
A Defias Bandit

Forum posts: 2
File comments: 16
Uploads: 0
Quote:
Originally posted by Akryn
By the way, can anyone confirm that the never-ending sort bug only happens for auto-arranges and not restores? I'll try to get that solved at the same time, but I haven't run into it myself so if anyone can figure out a way to reproduce it that would be helpful.
If you have more then ~15 players in the raid and do an auto sort or even a restore save there will be a neverending loop.
I would be happy if you could fix this one, else i have to write one on my own, and i dont have the energy to do that

Last edited by Fionn : 04-30-2009 at 11:13 AM.
Fionn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Old 04-30-2009, 12:24 AM  
Akryn
An Onyxian Warder
Interface Author - Click to view interfaces

Forum posts: 361
File comments: 58
Uploads: 7
If it's still useful I'll update it. I'll probably have something out by the end of this weekend. Sorry it's been slow.

By the way, can anyone confirm that the never-ending sort bug only happens for auto-arranges and not restores? I'll try to get that solved at the same time, but I haven't run into it myself so if anyone can figure out a way to reproduce it that would be helpful.

Quote:
Originally posted by Dridzt
I'm not sure I understand the "not think anyone will use it" part

[derail]
Assuming you mean that with dual specs role distribution has changed all that dramatically,
I can assure you that for my guild and many that I know it hasn't changed that much.

Focusing on a spec is still the preferred way to progress for us.
Secondary spec is a convenience and used occasionally instead of swapping,
but essentially has taken its place along-side our main/alt handling.

Progress content, raid zones that are still challenging (not on farm) raid composition
is formed based on member's declared Primary Spec and our rotation and loot allocation methods reflect that.
[/derail]

Bottomline:
GOM's sort functions based on talent are still useful to "us" and I'm guessing many more.
We just need it to learn 3.1 and scan the active talents of our raiders
Akryn is offline Report comment to moderator   Edit/Delete Message Reply With Quote
Post A Reply



Category Jump:




The Network:
EQInterface | EQ2Interface | LoTROInterface | MMOInterface | War.MMOUI | WoWInterface | VGInterface | Allakhazam | Thottbot | Wowhead | Zam


©2009 MMOUI / ZAM Network
vBulletin - Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.