Download
(58Kb)
Download
Updated: 07-31-17 10:41 AM
Pictures
File Info
Compatibility:
Tomb of Sargeras (7.2.0)
Updated:07-31-17 10:41 AM
Created:unknown
Downloads:19,534
Favorites:69
MD5:

Group O Matic  Popular! (More than 5000 hits)

Version: 4.0.0
by: Akryn, llcorell

Group O Matic makes it easier for the raid leader to set up the group arrangement. It can save and restore what groups people are in.

It also has an Auto button, which can push everyone to the top, or group melee together, or split the group into the odd/even group numbers, or other things. What the Auto button does is set by the "auto-arrange template" menu.

You can exclude the groups at the end of the raid from being changed, so that you can use those groups for bench/standby players (click More > Settings > Exclude groups).

The addon will show up when you open the raid UI.

=======================================

This addon also has some manual /commands:

/rgs 1 2 will swap the entire group 1 with the entire group 2.
/rgm 1 2 will push everyone from group 1 into group 2, if possible.

=======================================

Things the Auto button can be set to do (click More and pick from the auto-arrange template menu):

1. Group melee/tanks, healers, and range with similar players.
2. Push everyone to the top of the group list.
3. Split the group into two halves, attempting to balance tanks, healers and melee DPS.
4. Group players by what map location they are at.

4.0.0 (30/07/2017)
-Fixed Bug with addon calling protected function
-Added Demon Hunters into the Melee class
by: Akryn, llcorell

3.0.8 (12-3-2015):
-Fixed minor bugs.

3.0.7 (11-7-2015):
-Fixed /rgs not working.

3.0.6 (11-6-2015):
-Fixed a couple of bugs.

3.0.5 (11-3-2015):
-Added template to group classes together.
-Handle players switching roles (i.e. changing from tank to DPS) better.
-Added some buttons.

3.0.4 (10-23-2015):
-Added templates to split the raid into 2, and re-enabled the battlegrounds "group by map location" template.

3.0.2 (10-5-2015):
-Re-enabled custom templates and a few other features.
-Added 'healers first' template.

3.0.1 (10-3-2015):
-Re-enabled role scan and made the auto-arrange attempt to group melee/range/healers, rather than just push people randomly to the top groups.

3.0.0 (8-29-2015):
-Hey, an update!

2.7.0 (10-16-2010):
-Updates for WoW 4.0 API.
-Updated talents.
-Reduced memory footprint a bit when the GUI is loaded.
-Various minor bug fixes.

2.6.7 (4-2-2010):
-The talent scanner now confirms that UnitClass has returned a valid result when scanning players.
-Fix for a bug that caused talents to display as 100% known rather than 50% while in a 2-person raid with someone whose talents were unknown.
-Other minor bug fixes.

2.6.6 (2-9-2010):
-Fix for the player not being counted by ("talents: x% known") notices -- which I broke a few versions ago and didn't notice until now >.>

2.6.5 (2-8-2010):
-Works around a Bliz bug causing the "talent interpreter outdated" warnings.

2.6.4 (1-18-10):
-Small bug fix from 2.6.3.

2.6.3 (1-18-10):
-The table of cached roles is now stored more efficiently, resulting in a pretty good reduction of RAM usage if you have a large roles cache. If syncing is on, it will compress that copy as well on the first UI un/re-load.
-Changed the enUS/default names for restore methods so that they make sense without having to read the documentation.
-Fix for a potential nil error (but so unlikely that I doubt it ever actually happened).
-Doesn't load the GUI functions if the GUI itself was not loaded -- i.e. groupomatic.xml was removed from the TOC.
-Several minor bug fixes.

2.6.2 (1-16-10):
-Fix for the main GUI frame not handling viewports correctly when releasing from a drag.
-Minor bug fixes.

2.6.1 (12-28-09):
-Minor GUI bug fix.
-Fix for "attempt to index nil" error which was probably quite common but never happened for me :\
-Allows changing the output chatframe. No GUI for this yet. Ask me if you want to use it before then.

2.6.0 (12-8-09):
-toc increase to 30300
-Fixed a bug which caused starting an auto-arrange or raid restore via slash command to sometimes not work if "continuous scan" was active.
-Added extras pane for automatic actions as the raid is formed:
--Optionally automatically auto-arrange when the number of players hits 10 and/or 25 and/or 40 members for the first time during the current raid.
--Optionally automatically move raid members to match a saved raid as they are added.
--Note: You can use these options and GOM Raid Starter at the same time; if they conflict, GOM's setting will win out over GOM_RS.

2.5.10 (12-3-09):
-Updated for WoW 3.3. Should work for both, but I'll release a version with updated .toc once I confirm it works after 3.3 goes live.
-Added MEAT_SHIELD (enUS = "Occasional party-damage reducer") role. This is a specialized role for characters that have taken talents which temporarily or intermittently reduce party-only damage. It does not necessarily imply "TANK" and is not the same as "TANK_BUFFER" which is for permanent damage reduction or healing-received buffers.
-Since Pallies' Divine Sacrifice is party-only now, characters with that talent are now given the role MEAT_SHIELD
-Warriors with Imp. Spell Reflection are now also given the MEAT_SHIELD role.
-Druids with Imp. LotP are now also given the MEAT_SHIELD role.
-Exposed GrOM.SetStartover("name") for GOM_RS.
-Other minor changes.

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 (0)


Post A Reply Comment Options
Unread 07-13-09, 05:00 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Oh interesting bug. Thanks for finding it. I'm surprised no one has done that sequence of actions before you (or at least no one who mentioned it). I'll post a fix in a few minutes.

How many raid members were within 40 yards of you when it went up to 20%?
Report comment to moderator  
Reply With Quote
Unread 07-13-09, 01:11 PM  
Jiminimonka
A Defias Bandit

Forum posts: 3
File comments: 24
Uploads: 0
Originally posted by Akryn
And it is...that might be it. I'll look into it more when I get some time. If you feel like it, try disabling that mod and see if GOM works then?
I turned of RaidBuffStatus - talent scan got to 20% - then when I clicked Auto - I got this error:
Code:
[2009/07/13 19:59:20-3280-x1]: groupomatic-2.5.2\groupomatic.lua:951: attempt to index global 'GOMatic_ArrangementFrame' (a nil value)
groupomatic-2.5.2\groupomatic.lua:760: in function <Interface\AddOns\groupomatic\groupomatic.lua:758>
groupomatic-2.5.2\groupomatic.lua:1079: in function `AutoClick'
<string>:"*:OnClick":1: in function <[string "*:OnClick"]:1>
Report comment to moderator  
Reply With Quote
Unread 07-13-09, 06:08 AM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Originally posted by Akryn
Unless it's scanning talents, GOM wouldn't care about it.
And it is...that might be it. I'll look into it more when I get some time. If you feel like it, try disabling that mod and see if GOM works then?
Report comment to moderator  
Reply With Quote
Unread 07-13-09, 05:52 AM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Unless it's scanning talents, GOM wouldn't care about it.

No the command wouldn't change the behavior. Because of the way the talent inspection API works, if you have two addons trying to scan the whole raid at once with neither one backing off, you'd just end up with neither one working. GOM's continuous scan is pretty continuous though; if won't give up until it's been about a minute and then tries again after a few more minutes.

The command does let you know within 30-40 seconds whether it's working, though.

Unless you have another addon that deals with raid specs I'll continue to assume this is a bug. I'll download that addon and see if it causes problems, though.
Report comment to moderator  
Reply With Quote
Unread 07-13-09, 02:31 AM  
Jiminimonka
A Defias Bandit

Forum posts: 3
File comments: 24
Uploads: 0
Originally posted by Akryn
Also, do you have any other addons that scan raid talents? GOM backs off if it sees another addon doing a raid scan; and if it goes on long enough it just gives up. That might be what is happening. Although to cause GOM to only get one person's data over 2 hours it would have to be something that scanned pretty much constantly.
I use RaidBuffStatus - which I think scans the raid to check for buffs, flasks etc. Would use that command line "/run GrOM.AutoScanNow()" override the GOM default to stop scanning if another addon is scanning already?
Report comment to moderator  
Reply With Quote
Unread 07-12-09, 05:03 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Also, do you have any other addons that scan raid talents? GOM backs off if it sees another addon doing a raid scan; and if it goes on long enough it just gives up. That might be what is happening. Although to cause GOM to only get one person's data over 2 hours it would have to be something that scanned pretty much constantly.
Last edited by Akryn : 07-12-09 at 05:05 PM.
Report comment to moderator  
Reply With Quote
Unread 07-12-09, 04:56 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Originally posted by Jiminimonka
Yes, latest version, continuous scan turned on. At the end of the raid it was showing 10%, but we had only 18 by that time so not sure if that was due to the missing people increasing the ratio.
4% is 1:25 (just you).
10% is 2:18 so it successfully scanned someone.

Sounds like a bug I haven't seen before. I'll look into it.

Is anyone else seeing this? Has it ever worked for you, or did you just start using it?

You shouldn't ever have to do this but -- if you have a bunch of raid members near you and Continuous Scan turned on, you can force it to do a full scan of the raid with /run GrOM.AutoScanNow()
Report comment to moderator  
Reply With Quote
Unread 07-12-09, 04:29 PM  
Jiminimonka
A Defias Bandit

Forum posts: 3
File comments: 24
Uploads: 0
Originally posted by Akryn
Thanks for the report.

Are you using the latest version? Do you have "Continuous Scan" turned on?
Yes, latest version, continuous scan turned on. At the end of the raid it was showing 10%, but we had only 18 by that time so not sure if that was due to the missing people increasing the ratio.
Report comment to moderator  
Reply With Quote
Unread 07-12-09, 02:51 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Originally posted by Jiminimonka
GOM is showing total talents scanned as 4% even after 2 hours of raiding.
Thanks for the report.

Are you using the latest version? Do you have "Continuous Scan" turned on?
Report comment to moderator  
Reply With Quote
Unread 07-12-09, 02:45 PM  
Jiminimonka
A Defias Bandit

Forum posts: 3
File comments: 24
Uploads: 0
GOM is showing total talents scanned as 4% even after 2 hours of raiding.
Report comment to moderator  
Reply With Quote
Unread 07-06-09, 09:13 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
GOM_RS

Some of you might be interested in http://www.wowinterface.com/download...idStarter.html, which does simple auto-invite + restore of a saved raid.

If you feel like helping me beta-test it, and you come across any problems, please post a comment.
Report comment to moderator  
Reply With Quote
Unread 05-30-09, 02:41 PM  
Dridzt
A Pyroguard Emberseer
 
Dridzt's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1360
File comments: 829
Uploads: 56
MMO-Champion's RaidComp online tool
can give you an idea about what goes on in a raid-leader's head when planning out composition and groups.
Report comment to moderator  
Reply With Quote
Unread 05-18-09, 06:18 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
The default template is purely my own opinion of how best to set up a raid, formed based on my experiences as a raid leader in 40-, and later 25-, man instances. The current incarnation of that template is based on a template I wrote while in TK. It's been updated since then, but there's always room for improvement which is one reason that GOM supports user-created templates.

I've never seen a good guide to raid arrangement, though. Probably there aren't any because everyone has different opinions about how best to set up a raid. Of course, in 3.x it doesn't matter nearly as much as it used to.

Originally posted by loctrinh01
This addon has made me realized that in a 25-man raid, I have no clue as to what class and spec should be together in a group. When I get it to auto-arrange, it's like magic. But how did you obtain the information so that it knows which classes are best for each group? As in, something that I can read to learn how to set up groups manually.
Report comment to moderator  
Reply With Quote
Unread 05-18-09, 03:40 AM  
loctrinh01
A Kobold Labourer

Forum posts: 0
File comments: 39
Uploads: 0
This addon has made me realized that in a 25-man raid, I have no clue as to what class and spec should be together in a group. When I get it to auto-arrange, it's like magic. But how did you obtain the information so that it knows which classes are best for each group? As in, something that I can read to learn how to set up groups manually.
Report comment to moderator  
Reply With Quote
Unread 05-13-09, 04:53 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Glad to hear it's working.

As should be obvious now, I probably won't notice that this is broken if it breaks again, unless it breaks for me too; but I should be reachable by PM or comments here. Same with feature requests.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: