Go to Page... |
Updated: | 12-22-10 07:38 PM |
Created: | 10-29-10 04:29 PM |
Downloads: | 8,116 |
Favorites: | 85 |
MD5: |
PugLax
Tank tested, Perky Pug approved!
What is PugLax?
PugLax is an addon aimed at making the pug experience smoother for the upcoming Cataclysm expansion pack. Many of us remember the good old days of actually using CC in five man dungeons. However, it can be time consuming to make customized macros to echo things like kill order and mark assignments to your group.
PugLax aims to make this easier by automatically generating a list of crowd control available to your group, sorting those CC's based on priority, and finally printing that list along with direct assignments to party chat for you along with the kill order. For baseline forms of crowd control, PugLax assumes that the character has the CC if they are the appropriate. For talent based forms of crowd control (like Repentance), the addon inspects the character to ensure they have the required talent.
For now much of this is hard coded; however, this initial release offers options for which marks you wish to enable/disable as well as which forms of crowd control you wish to enable/disable. Simple set the addon up once based on what you feel is worth using (sap and polymorph, but not fear and hibernate for example). Then, simply type "/puglax party" and the addon will take care of the rest.
Planned Features:
Comment Options |
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
12-27-10, 10:43 AM | |
|
I loaded up latest PugLax (v1.8.17) to test that I didn't break anything in the SRTI update I'm about to push.
In the process I came across some bugs and made a minor enhancement. - (bug) announce trying to announce to party when solo. - (bug) pulltimer trying to announce to party when solo. - (bug) group detection in general (is half-broken for normal parties/raids and would fail entirely in BG - wrong functions used) - (enhancement) tooltips for JumpMenu buttons. Modified files: (pastey) PugLax.lua: http://www.pastey.net/144325 PugLaxSync.lua: http://www.pastey.net/144326 PugLaxGUI.lua: http://www.pastey.net/144327 PugLocalization.lua: http://www.pastey.net/144328 Additionally from using it there were a couple things I would have as feature requests if you're working on a rewrite anyway 1. Would be nice if the kill order dropdowns had a "none" option. I rarely if ever use 3 kill marks. At most 2 and remark in combat (with keybinds) as the previous marks die. 2. The initial assignments spam is rather intimidating. It would be nice if there is an alternative option for grouping icon CC assignments. Not on the CC method but on the player. Announce would then be in the form of: One line / player (arguably they can figure out which method to use) "WarlockName please CC ([Banish],[Fear],[Seduction])" Instead of: x lines / player "WarlockName please [Banish] " "WarlockName please [Fear] " "WarlockName please [Seduction] " If you have a couple CC with 2 methods each it scrolls beyond the chatframe "page". I doubt players (especially in pugs that might have different marks assigned to them in each group) will remember what mark they were assigned if you get to enemies that need another form of CC (banish vs fear/sed for example) The only drawback I see to such a method is the rare cases where 1 player can simultaneously cc 2 enemies. (example: trap 1 + wyvern sting 2) Thanks for your work, I can certainly see uses for PugLax, anticipating next major version |
|
Dridzt |
View Public Profile |
Send a private message to Dridzt |
Find More Posts by Dridzt |
Add Dridzt to Your Buddy List |
12-23-10, 01:15 PM | ||
|
If you'll need help with checking/testing your code I'll be happy to, not too familiar with LUA but I do know coding and it's a lot similar.
Just PM me
Last edited by Noxarious : 12-23-10 at 01:17 PM.
|
|
|
Noxarious |
View Public Profile |
Send a private message to Noxarious |
Find More Posts by Noxarious |
Add Noxarious to Your Buddy List |
12-23-10, 08:42 AM | |
|
@Noxarious - Actually, I just forgot to remove it from the PugLax:EchoRow(v, channel)
Originally the EchoAll function sent the channel to the EchoRow function. However, once the GUI was implemented and we could echo individual rows it became necessary for the EchoRow function to also find the correct channel. I removed the extra information from that EchoRow call though for the next release - thanks for pointing that out. @Allcoast - It *should* be doing a live removal and addition. By this I mean - you start with the following group Mage Hunter (marks) Druid Warrior Death Knight -- PugLax sets up as: [moon] Polymorph [square] FTrap [diamond] Roots The druid leaves, and shortly thereafter a second mage joins. The addon should do this: [moon] Poly [square] FTrap [diamond] cleared when the druid left [moon] Poly [square] FTrap [diamond] Poly2 --- It should automatically remove the CC from the person leaving and add in the CC from the person joining without touching anyone elses settings. If this is not happening, please let me know what the situation is that's causing a silent reset. I'll be adding a "Never Automatically Reset" option to the next version though, as I have the feeling the intended functionality is not working properly. I've learned a lot about how to write an addon with this project so far, and PugLax is without a doubt in need of a complete rewrite. Too many functions changed too significantly; I have a much cleaner vision in mind for how to set it up for PugLax 2.0 which I'll be doing after New Years (hopefully finishing by mid-January). |
|
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
12-23-10, 07:24 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 12
Uploads: 0
|
Keeps reseting
Is it possible to add an option that keeps this thing from resetting everytime a grp member changes? Like when someone leaves the group and someone else comes in, all of the setup changes, and we have to re-set everything up. I would like to be able to setup kind of a default mark to cc setting or something like that. will this be possible?
Last edited by Allcoast : 12-23-10 at 07:25 AM.
|
|
Allcoast |
View Public Profile |
Send a private message to Allcoast |
Find More Posts by Allcoast |
Add Allcoast to Your Buddy List |
12-23-10, 03:32 AM | |
|
Code:
function PugLax:EchoAll() local channel if (GetNumRaidMembers() > 0) then channel = "RAID" else channel = "PARTY" end -- for k,v in pairs(PugLax.Marks) do -- if v["assignment"] then -- PugLax:EchoRow(k, channel) -- end -- end for i,v in ipairs(PugLax.SortedMarks) do if PugLax.Marks[v]["assignment"] then PugLax:EchoRow(v, channel) end end SendChatMessage(PugLocs[PugLax.loc]["echoKillOrder"] .. KillOrderToString() , channel, nil, nil) end function PugLax:EchoRow(rowname) local channel if (GetNumRaidMembers() > 0) then channel = "RAID" else channel = "PARTY" end if (PugLax.Marks[rowname]["assignment"]) then --local msg = PugLax.Marks[rowname]["assignment"]["playername"] .. PugLocs[PugLax.loc]["echoPlease"] .. PugLocs[PugLax.loc]["ccShortName"][PugLax.Marks[rowname]["assignment"]["ccKey"]] .. PugLocs[PugLax.loc]["echoThe"] .. "{" .. PugLax.Marks[rowname]["markstring"] .. "}" local msg = PugLax.Marks[rowname]["assignment"]["playername"] .. PugLocs[PugLax.loc]["echoPlease"] .. PugLax:SpellLink(PugLax.ccData[PugLax.Marks[rowname]["assignment"]["ccKey"]]["spellID"]) .. PugLocs[PugLax.loc]["echoThe"] .. "{" .. PugLax.Marks[rowname]["markstring"] .. "}" SendChatMessage(msg, channel, nil, nil) end end Code:
function PugLax:EchoAll() local channel if (GetNumRaidMembers() > 0) then channel = "RAID" else channel = "PARTY" end -- for k,v in pairs(PugLax.Marks) do -- if v["assignment"] then -- PugLax:EchoRow(k, channel) -- end -- end for i,v in ipairs(PugLax.SortedMarks) do if PugLax.Marks[v]["assignment"] then PugLax:EchoRow(v, channel) end end SendChatMessage(PugLocs[PugLax.loc]["echoKillOrder"] .. KillOrderToString() , channel, nil, nil) end function PugLax:EchoRow(rowname, channel) if (PugLax.Marks[rowname]["assignment"]) then --local msg = PugLax.Marks[rowname]["assignment"]["playername"] .. PugLocs[PugLax.loc]["echoPlease"] .. PugLocs[PugLax.loc]["ccShortName"][PugLax.Marks[rowname]["assignment"]["ccKey"]] .. PugLocs[PugLax.loc]["echoThe"] .. "{" .. PugLax.Marks[rowname]["markstring"] .. "}" local msg = PugLax.Marks[rowname]["assignment"]["playername"] .. PugLocs[PugLax.loc]["echoPlease"] .. PugLax:SpellLink(PugLax.ccData[PugLax.Marks[rowname]["assignment"]["ccKey"]]["spellID"]) .. PugLocs[PugLax.loc]["echoThe"] .. "{" .. PugLax.Marks[rowname]["markstring"] .. "}" SendChatMessage(msg, channel, nil, nil) end end |
|
Noxarious |
View Public Profile |
Send a private message to Noxarious |
Find More Posts by Noxarious |
Add Noxarious to Your Buddy List |
12-22-10, 06:55 PM | ||
|
Or do you mean automatically assigning CC's to marks on the jump menu? If so, you can disable auto-assignment entirely by going into PugLax config and disabling all of the CC (you'll still be able to manually assign things via the GUI). It may just be resetting itself, in which case you may have the "Silent Instance Reset" option enabled. |
|
|
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
12-22-10, 05:06 PM | ||
|
__________________
|
|
|
segadomcast |
View Public Profile |
Send a private message to segadomcast |
Find More Posts by segadomcast |
Add segadomcast to Your Buddy List |
12-22-10, 04:45 PM | ||
|
I'm pushing 1.8.16 live right now (pending approval atm). It does a two major things: 1) Fixed the kill order, silly bug was silly 2) Added a temporary work-around for the talent issue. How it works is this: Hunter joins the team. Wyvern Sting is immediately added to the "Missing Talents" sub-menu for manual assignments. Wyvern Sting is *not* automatically assigned. If PugLax is eventually able to successfully verify that the hunter does in fact have Wyvern Sting it will automatically assign it to an open mark (assuming Wyvern Sting is enabled). It's not a perfect solution, but at least you can assign rep/wyvern if the addon doesn't get the talents properly for some reason. Hopefully I'll have a better solution after the holidays when I rework it in general! |
|
|
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |
12-22-10, 04:26 PM | ||
|
__________________
|
|
|
segadomcast |
View Public Profile |
Send a private message to segadomcast |
Find More Posts by segadomcast |
Add segadomcast to Your Buddy List |
12-22-10, 08:31 AM | ||
|
The x-realm stuff is particularly annoying to try and debug with my play time so limited at the moment, sorry! Right now I'm using unitid (so party1, party2, party3...) - I think I'll switch it over to GUID (a totally unique value even in cross realm situations) and rewrite the talent stuff to make better use of the LibGroupTalents library. *Hopefully* that will fix it. (basically right now I'm just asking LGTalents "Does this user have this talent?" - what I could be doing, and probably should be doing, is adding all of the players in the group to a queue for inspection and registering some events for when their talents have been parsed). EDIT: At the very least today I'm going to push a version that includes a "Missing Talents" drop-down in the manual assignment list. Since I probably won't get time to do any major changes until January now, this will be a good band-aid so people can work around the darn inspect functionality.
Last edited by Virance : 12-22-10 at 08:36 AM.
|
|
|
Virance |
View Public Profile |
Send a private message to Virance |
Find More Posts by Virance |
Add Virance to Your Buddy List |