Download
(5Kb)
Download
Updated: 09-05-12 08:56 PM
Pictures
File Info
Updated:09-05-12 08:56 PM
Created:12-14-09 08:18 PM
Downloads:5,805
Favorites:20
MD5:

Assigned Tank Assist  Popular! (More than 5000 hits)

Version: 1.1.6
by: Akryn, GreyWolfSC

Assigned Tank Assist creates macros that are aware of the "tank" role assigned by the LFD tool. The default is to assist the tank, but they are normal macros except that they can be longer.

Note that !mt and !ma will also work, for the Bliz raid MT and MA. But if you have more than one MT or MA, it basically picks one at random.

To configure, go to the panel (/atassist will go there immediately), and type in a macro in the large box. In the macro, you can use !t where the name of the tank should be inserted. For example, "/assist !t". The addon will keep the macros up to date with the correct name.

Up to 30 macros are supported.

To actually run the macros, do one or both of the following:

1. Set a key binding in the addon's config. panel.
2. Create a normal macro, or edit an existing one, or in some other way run the command:

Code:
/click AssignedTankAssistButton
That line can also by copy/pasted in-game from the smaller text field in the configuration panel. For macros 2-30, you can do the same thing but put the number after, i.e. "/click AssignedTankAssistButton2"

1.1.5 (12-10-2011):
-Updated TOC for 4.3

1.1.4 (10-19-2010):
-Update for WoW 4.0 (thanks to acidzero for providing the fix, since I don't have an account ATM).

1.1.2 (2-9-2010):
-!mt and !ma tags work properly now (note that the tags are designed for raids that only use 1, tags like this are pretty useless if you use multiple mt's or ma's since there's no way to differentiate between them).

1.1.1 (2-8-2010):
-The !mt and !ma tags work better now.
-Fix for "raidx" spam and lag during raid updates (sorry x.x).

1.1 (2-5-2010):
-Added !mt and !ma for raid "maintank" and "mainassist" roles.
-Fix for a bug that caused some ATA settings to be cleared when changing other interface settings without having opened ATA's config panel during the current session.
-Fixed a few typos.

1.0 (1-27-2010):
-You can now have up to 30 macros.
-Fixed the "default" button not resetting all the options.
-Added "Clear Binding" button.

0.1 B10:
-Added an option to suppress error text ("You aren't in a group.", "There is no tank.").
-Added an option to run the macro when called even if there is not a tank (replaces !t with blank space).
-Added a button to bind a key to the macro rather than using the /click command.

0.1 B9:
-Redesign, see the info page.

0.1 B8:
-Check for changes occasionally as well as on events.

0.1 B7:
-Bug fix.

0.1 B6:
-Added some customization options to the top of the .lua file.

0.1 B5:
-Fix for rarely leaving duplicate bindings.
-Allows using a macro (ATA_Temp) instead of a binding (see description).
-Registers PLAYER_ROLES_ASSIGNED in addition to PARTY_MEMBERS_CHANGED

0.1 B4:
-Let's try it this way...

0.1 B3:
-Bug fixes

0.1 B2:
-Bug fixes
Optional Files (0)


Post A Reply Comment Options
Unread 10-19-10, 05:44 PM  
acidzero
A Kobold Labourer

Forum posts: 0
File comments: 1
Uploads: 0
ATA needs a minor change to get it to work properly with 4.0.1 in randoms.

Found it was always selecting party1 as the tank which isn't always the tank in randoms. Can be fixed by altering one line of code in the lua:

Change line 255 in AssignedTanKAssist.lua from

if UnitGroupRolesAssigned(p) then

to

if UnitGroupRolesAssigned(p) == "TANK" then

and ATA should correctly identify the tank in 5-man randoms.
Report comment to moderator  
Reply With Quote
Unread 10-16-10, 03:24 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Huh...well, does ATA work still? My account isn't active ATM. If not, does it give you an error that you could post?

Originally posted by GreyWolfSC
party1 is not always the tank, though. In fact, it's quite often not for me.
Report comment to moderator  
Reply With Quote
Unread 10-16-10, 12:42 PM  
GreyWolfSC
A Murloc Raider

Forum posts: 5
File comments: 83
Uploads: 0
party1 is not always the tank, though. In fact, it's quite often not for me.
Report comment to moderator  
Reply With Quote
Unread 10-16-10, 10:22 AM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Re: update for 4

Originally posted by blankStare
not sure if this is causing a problem for 4 but can you check?
I'm not updating this anymore since "party1" does the same thing by default now. If someone wants (for some reason) to update it for WoW 4, though, feel free to send me the project page link and I'll add it to the description here.
Report comment to moderator  
Reply With Quote
Unread 10-16-10, 09:11 AM  
blankStare
A Kobold Labourer

Forum posts: 1
File comments: 82
Uploads: 0
update for 4

not sure if this is causing a problem for 4 but can you check?
Report comment to moderator  
Reply With Quote
Unread 02-08-10, 05:28 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

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

I've been having the same thing lately but it took me a while to realize where it was coming from. I have a fix written up, but it will be either late tonight or tomorrow before I can test it and upload a new version.
Last edited by Akryn : 02-09-10 at 12:20 AM.
Report comment to moderator  
Reply With Quote
Unread 02-08-10, 08:09 AM  
diablobase
A Kobold Labourer
 
diablobase's Avatar

Forum posts: 0
File comments: 3
Uploads: 0
very nice addon, i'm already using it since the very first version
but today i got something like a bug:



this happens always twice when i enter/open a raid or raidgroup, on reloadui, ...

edit: its german and means: "raid# is not in your group"
Last edited by diablobase : 02-08-10 at 08:28 AM.
Report comment to moderator  
Reply With Quote
Unread 02-05-10, 07:59 PM  
GreyWolfSC
A Murloc Raider

Forum posts: 5
File comments: 83
Uploads: 0
Originally posted by Akryn
Yep that's what it was. 1.1 fixes the settings bug. Thanks for reporting it!
Great! Testing it now.
Report comment to moderator  
Reply With Quote
Unread 02-05-10, 07:08 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Yep that's what it was. 1.1 fixes the settings bug. Thanks for reporting it!
Report comment to moderator  
Reply With Quote
Unread 02-05-10, 05:37 PM  
GreyWolfSC
A Murloc Raider

Forum posts: 5
File comments: 83
Uploads: 0
Originally posted by Akryn
That message means that tainted/insecure code tried to run a protected function in-combat. Some of the bugsack-type addons display the full text as errors. You can also enable taint logging via a cvar that I don't remember, you can find it via google though.

It is very unlikely that that message has anything to do with the problem you're having though.
I'll turn on the taint logging and check it anyway. The error message bothers me.
Report comment to moderator  
Reply With Quote
Unread 02-05-10, 12:34 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Originally posted by GreyWolfSC
It's quite possible. I occasionally get a message saying "An interface option failed due to an AddOn." Is there any way to find out more details on that error?
That message means that tainted/insecure code tried to run a protected function in-combat. Some of the bugsack-type addons display the full text as errors. You can also enable taint logging via a cvar that I don't remember, you can find it via google though.

It is very unlikely that that message has anything to do with the problem you're having though.
Report comment to moderator  
Reply With Quote
Unread 02-05-10, 12:11 PM  
GreyWolfSC
A Murloc Raider

Forum posts: 5
File comments: 83
Uploads: 0
Originally posted by Akryn
So the first macroText var is getting sent an empty string. Probably what is happening is that you're changing some other addon's settings without opening the ATA panel, and then when you press OK it is still calling ATA's OK handler even though you haven't opened the ATA panel (which I didn't think it did), and therefore setting the variable to the contents of the input box (which is "" because it hasn't initialized).

I will test that this evening when I can log in; and if I can reproduce it, I'll release a fix tonight.
It's quite possible. I occasionally get a message saying "An interface option failed due to an AddOn." Is there any way to find out more details on that error?
Report comment to moderator  
Reply With Quote
Unread 02-05-10, 11:43 AM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
So the first macroText var is getting sent an empty string. Probably what is happening is that you're changing some other addon's settings without opening the ATA panel, and then when you press OK it is still calling ATA's OK handler even though you haven't opened the ATA panel (which I didn't think it did), and therefore setting the variable to the contents of the input box (which is "" because it hasn't initialized).

I will test that this evening when I can log in; and if I can reproduce it, I'll release a fix tonight.
Report comment to moderator  
Reply With Quote
Unread 02-03-10, 01:09 PM  
GreyWolfSC
A Murloc Raider

Forum posts: 5
File comments: 83
Uploads: 0
Originally posted by Akryn
Does this only happen at login or does it sometimes happen in the middle of a session? <Edit: And by that I mean does it ever work at first but stop working in the middle of a session without reloading/relogging?> If it only happens at login could you post your saved variables file for the addon while it's in the broken state?

Thanks for the report, it's a new one for me.
No, it never stops working mid-session, I'm sure it's occurring at login/logout but I don't notice it until I'm in an instance. I'll zip up the SV file next time.

EDIT: It just did it again. Since the SV file is small I'll just put it here:

Code:
AssignedTankAssist_Vars = {
	["otherMacroTexts"] = {
	},
	["macroText"] = "",
}
AssignedTankAssist.lua.bak is still valid:

Code:
AssignedTankAssist_Vars = {
	["otherMacroTexts"] = {
	},
	["macroText"] = "/assist !t",
}
Last edited by GreyWolfSC : 02-04-10 at 10:57 PM.
Report comment to moderator  
Reply With Quote
Unread 02-02-10, 12:11 PM  
Akryn
A Firelord
AddOn Author - Click to view AddOns

Forum posts: 479
File comments: 95
Uploads: 10
Originally posted by GreyWolfSC
I've been having issues with the macro text entered in the addon disappearing after a while. It will work fine for a few sessions, then suddenly I can't assist in a dungeon and when I look at the config panel the text box is empty. The .bak saved variable still has the text in it.
Does this only happen at login or does it sometimes happen in the middle of a session? <Edit: And by that I mean does it ever work at first but stop working in the middle of a session without reloading/relogging?> If it only happens at login could you post your saved variables file for the addon while it's in the broken state?

Thanks for the report, it's a new one for me.
Last edited by Akryn : 02-02-10 at 05:17 PM.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: