Download
(68 Kb)
Download
Updated: 10-16-10 06:20 PM
Pictures
File Info
Updated:10-16-10 06:20 PM
Created:unknown
Downloads:16,686
Favorites:70
MD5:
Group O Matic  Popular! (More than 5000 hits)
Version: *untested*_2.7.0
by: Akryn [More]
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

If you want to use GOM as a simple raid inviter, see: GOM_RS
-------------------------------------------
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:
--Players from the saved raid who are absent from the current raid are ignored.
--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.
--Same as above but substitutions are based on class rather than roles.

Part2 can be:
--New players (who aren't substituted for a missing player) are auto-arranged based on the currently selected template.
--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 "restore options" Extras menu. You can also exclude groups from being saved, if you want.

*Automatic setup during invites:
In the Extras menu, there are options to automatically trigger an auto-arrange the first time the raid reaches a certain size (the numbers are configurable but most people will probably want to leave them at 10-25-40). You can also set the addon to automatically move people to the appropriate groups as they are invited, based on a saved raid. Note that these features will work alongside GOM_RS, but if they both try to do something at once, the built-in features will get priority.

*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.
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)


Archived Files (27)
File Name
Version
Size
Author
Date
2.6.7
71kB
Akryn
04-02-10 10:12 PM
2.6.6
71kB
Akryn
02-09-10 08:58 PM
2.6.5
71kB
Akryn
02-08-10 09:26 PM
2.6.4
70kB
Akryn
01-18-10 10:58 PM
2.6.3
70kB
Akryn
01-18-10 12:08 PM
2.6.2
70kB
Akryn
01-16-10 03:21 PM
2.6.1
69kB
Akryn
12-28-09 10:56 AM
2.6.0
69kB
Akryn
12-08-09 07:01 PM
2.5.10
67kB
Akryn
12-03-09 02:15 PM
2.5.9
66kB
Akryn
10-02-09 08:13 PM
2.5.8
65kB
Akryn
09-07-09 12:40 PM
2.5.7
65kB
Akryn
09-05-09 02:32 PM
2.5.7
65kB
Akryn
09-05-09 12:47 PM
2.5.6
65kB
Akryn
08-04-09 04:49 PM
2.5.5
64kB
Akryn
07-15-09 06:48 PM
2.5.4
64kB
Akryn
07-14-09 06:10 PM
2.5.3
63kB
Akryn
07-13-09 05:18 PM
2.5.2
63kB
Akryn
06-22-09 09:10 PM
2.5.1
63kB
Akryn
06-05-09 09:17 PM
2.5
60kB
Akryn
05-30-09 11:44 AM
2.4
54kB
Akryn
05-08-09 07:17 PM
2.3.1(v2 -- deb
55kB
Akryn
05-05-09 05:54 PM
2.3.1
54kB
Akryn
05-01-09 07:05 PM
2.3.0
54kB
Akryn
04-30-09 07:56 PM
2.2.0
54kB
Akryn
02-24-09 11:51 PM
2.1.3
53kB
Akryn
02-10-09 10:53 PM
2.1.2
53kB
Akryn
11-02-08 06:44 PM


Post A Reply Comment Options
Unread 10-27-10, 09:45 PM  
Fionn
A Defias Bandit
AddOn Author - Click to view AddOns

Forum posts: 2
File comments: 25
Uploads: 2
Thanks for the update! (gonna test it)
Fionn is offline Report comment to moderator  
Reply With Quote
Unread 10-16-10, 06:21 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
2.7.0 is untested

I don't have an active account ATM, so I can't test it. It may not even load, so use at your own risk.
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 07-03-10, 01:14 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
FYI, GOM should not need to be changed to deal with the inspect rate capping in 3.3.5; but there's a much higher chance of addon conflicts. If you are getting bad performance with the talent scanner, turning on /gom debug might give you some information as to why. If you have too many addons trying to scan at once and it's triggering the cap, GOM's debug output will probably report that as "latency too high" but it might also report it as an addon conflict, depending on the situation.

I don't think GOM itself is likely to be a problem for other addons; but please let me know if you see it behaving poorly. If it does, you can always turn off "Continuous Scan."

Also, just as an extra piece of information for anyone who feels inclined to muck around, running this command:

Code:
/run GrOM_G_Vars.loadScript = "GrOM.talentRequestTTL = 1.8"
will let you change how fast GOM sends talent requests. Lower numbers mean more aggressive scanning. 1.8 is the default, increase it to make GOM be nicer to other addons. This requires a /reload before it will work. To go back to the default:

Code:
/run GrOM_G_Vars.loadScript = nil
Last edited by Akryn : 07-03-10 at 01:24 PM.
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 04-23-10, 08:02 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
Ah...that's a new one then. I don't usually use that so I'll have to experiment with it. I'm still not sure whether I can stop the tainting; but now that I know how to repeat it I'll see if I can figure it out.

Thanks again.

Originally posted by Fionn
Hi there

Its easy to replicate the problem. Log in sit down open the raid browser, and wait. it will happen soonTM-er or later.
I'm using PitBull unit frame since years so i gave up on setting the focus over the drop down menu long ago
I dont have problems at all with that error its causing no trouble, I just wanted to let you know, maybe it helps you a bit. Maybe it does not

/Keep up the good work!
/Cheers
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 04-23-10, 07:23 PM  
Fionn
A Defias Bandit
AddOn Author - Click to view AddOns

Forum posts: 2
File comments: 25
Uploads: 2
Hi there

Its easy to replicate the problem. Log in sit down open the raid browser, and wait. it will happen soonTM-er or later.
I'm using PitBull unit frame since years so i gave up on setting the focus over the drop down menu long ago
I dont have problems at all with that error its causing no trouble, I just wanted to let you know, maybe it helps you a bit. Maybe it does not

/Keep up the good work!
/Cheers
Fionn is offline Report comment to moderator  
Reply With Quote
Unread 04-18-10, 09:42 AM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
Hi,

I believe that this is an example of a bug in Bliz's dropdown menu code that has been there for some time. Almost always it manifests when trying to set/clear focus via the right-click context menu on a unitframe (although in this case I see it was the LFG tool, which I've seen happen before also). If you disable GOM you will probably still have the same problem caused by another addon because it just reports whichever one caused it last.

The usual way around the focus problem, if that happens, is to just use a keybind or the /focus command to set/clear your focus, rather than the right-click menu. If you're only getting the error from GOM and it's causing you a problem, a workaround may be to rename/delete groupomatic.xml (so that the GUI doesn't load) and then just use the slash commands -- although that seems like too much trouble to me, unless you don't use the GUI anyway. I've never seen it actually cause a problem either, it just reports the taint error and then continues on like nothing happened.

If you got this in some other circumstance, or if you can repeat it, or if it's actually breaking something, please let me know what steps to use to replicate the problem so that I can debug it.

Thanks for the report.

Originally posted by Fionn
4/18 02:47:44.380 Global variable COMBAT_TEXT_X_SCALE tainted by groupomatic - Interface\AddOns\Blizzard_CombatText\Blizzard_CombatText.lua:552 CombatText_UpdateDisplayedMessages()
4/18 02:47:44.380 Interface\FrameXML\InterfaceOptionsPanels.lua:1051
4/18 02:47:44.380 Execution tainted by groupomatic while reading COMBAT_TEXT_X_SCALE - Interface\AddOns\Blizzard_CombatText\Blizzard_CombatText.lua:376
4/18 02:47:44.380 An action was blocked because of taint from groupomatic - SearchLFGLeave()
4/18 02:47:44.380 Interface\FrameXML\LFRFrame.lua:389 LFRBrowseFrame_OnUpdateAlways()
4/18 02:47:44.380 UIParent:OnUpdate()
Last edited by Akryn : 04-18-10 at 09:47 AM.
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 04-17-10, 06:52 PM  
Fionn
A Defias Bandit
AddOn Author - Click to view AddOns

Forum posts: 2
File comments: 25
Uploads: 2
Hi,

Im not getting that one
But i have one that says: Interface action failed....

And the log is:

4/18 02:47:44.380 Global variable COMBAT_TEXT_X_SCALE tainted by groupomatic - Interface\AddOns\Blizzard_CombatText\Blizzard_CombatText.lua:552 CombatText_UpdateDisplayedMessages()
4/18 02:47:44.380 Interface\FrameXML\InterfaceOptionsPanels.lua:1051
4/18 02:47:44.380 Execution tainted by groupomatic while reading COMBAT_TEXT_X_SCALE - Interface\AddOns\Blizzard_CombatText\Blizzard_CombatText.lua:376
4/18 02:47:44.380 An action was blocked because of taint from groupomatic - SearchLFGLeave()
4/18 02:47:44.380 Interface\FrameXML\LFRFrame.lua:389 LFRBrowseFrame_OnUpdateAlways()
4/18 02:47:44.380 UIParent:OnUpdate()

I had the raid browser open at that time.
Fionn is offline Report comment to moderator  
Reply With Quote
Unread 03-31-10, 04:46 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
To anyone getting that error: what does this print?

Code:
/run print(select(2, UnitClass("player")))
Last edited by Akryn : 03-31-10 at 04:47 PM.
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 03-31-10, 02:15 PM  
-KAPMA-
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 40
Uploads: 1
1x Interface\FrameXML\UIParent.lua:2785: bad argument #1 to 'pairs' (table expected, got nil):
Interface\FrameXML\UIParent.lua:2785: in function `CopyTable':
groupomatic-2.6.5\groupomatic.lua:1339: in function <groupomatic\groupomatic.lua:1324>
groupomatic-2.6.5\groupomatic.lua:2539: in function <groupomatic\groupomatic.lua:2466>

Locals:
settings = nil
copy = <table> {
}

---
-KAPMA- is offline Report comment to moderator  
Reply With Quote
Unread 12-28-09, 09:08 AM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
Originally posted by -KAPMA-
149x groupomatic-2.5.10\groupomatic.lua:2396: attempt to get length of field 'debugCache' (a nil value )
I'm confused by this because debugCache is not referenced on that line. I don't think the difference between 2.5.10 and 2.6 is that big -- did you modify the code by any chance?

However, I did find a different line that would cause that error (in a part of the code that corrects for addon conflicts, so since I don't run with other talent scanning addons I didn't notice it before).

That one is fixed in 2.6.1. Please let me know if the error continues.
Last edited by Akryn : 12-28-09 at 11:32 AM.
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 12-28-09, 06:35 AM  
-KAPMA-
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 40
Uploads: 1
149x groupomatic-2.5.10\groupomatic.lua:2396: attempt to get length of field 'debugCache' (a nil value )
Last edited by -KAPMA- : 12-28-09 at 06:36 AM.
-KAPMA- is offline Report comment to moderator  
Reply With Quote
Unread 11-02-09, 08:22 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
I know I've said this before, but I haven't played WoW seriously for years, and I don't understand the current endgame very well at all. Cataclysm looks like it's going to bring some pretty massive changes to how characters are spec'd, which will no doubt mean lots of necessary changes to GOM which I'm definitely not the right person to make, anymore.

As long as the addon remains relevant -- e.g. Bliz doesn't redesign raids so there aren't subgroups, or something -- I'll probably keep updating GOM the way I have been: little patches for compatibility/talents, just because it's fun to do. But I'd like to let everyone know that I no longer make any claims to it (or ArrangeProxy/GOM_RS). It's public domain, if you want to do something with parts of the code, or the whole addon, feel free.
Last edited by Akryn : 11-02-09 at 08:23 PM.
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 08-11-09, 04:24 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
Originally posted by Fionn
Hi Akryn,

Thank you for the update
YW
Akryn is offline Report comment to moderator  
Reply With Quote
Unread 08-11-09, 05:58 AM  
Fionn
A Defias Bandit
AddOn Author - Click to view AddOns

Forum posts: 2
File comments: 25
Uploads: 2
Hi Akryn,

Thank you for the update
Fionn is offline Report comment to moderator  
Reply With Quote
Unread 07-31-09, 08:51 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 93
Uploads: 9
Originally posted by Jiminimonka
Is there somewhere that the debug information is stored so I can send that to you?
No unfortunately it doesn't have that ability at the moment. I assume that any debugging output that's useful will be short enough that you can just take a screenshot of it.

If you routinely get a lot of errors coming up in the debug output, I can write something up to let you just copy/paste it all. Of course, if you're reading this in 2 weeks, it'll probably be around the time 3.2 is coming out. Since I'm not on the PTR, I'm not sure that GOM will work right away; it might have to wait a bit if there are any significant problems updating to 3.2.
Akryn is offline Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: