They are alphabetical order =P (Elemental/Enhancement/Restoration) etc...
However, I think I may have found an easy way to to give that option without having to maintain the "mapping" of spec name to spec levels. If I can make that work I will make it an option.
Yeah Grayhoof my lord, think about the alphabetical order only works on English client...
And there are millions of gladiators who not using English client...
I could tell how I face every spec name for every class, but I just can't make this name connected to the numbers...
Your codes were spread all over the world, so please, consider it again.
a bug ive noticed in Proximo2 (which was also present in Proximo) is that sometimes when an arena game is done, the window is still up for a little bit. Also, sometimes its still highlighting even if there isnt any targets on the Proximo window. I can try to get a screenshot if you need to see it, but i wont be arenaing for a bit and skirmish queues are unbearable.
Actually is there a way to ensure that the targetting bypass the cheap hunter pet exploit.
I have posted on this here and you said that is could be reported. I did and the GM stated that this was ok and not against the rules. So here we are against top team that use proximo too but with a difference, since if they have used the hunter pet naming exploit we cannot target their healer while their proximo works fine.
It would be nice if there was a way to use unique IDs in the targetting of proximo and have an option to show pets too.
This is for me currently a big show stopper until something is done (on blizzard or the mod community) to sort this out.
Actually is there a way to ensure that the targetting bypass the cheap hunter pet exploit.
In short : not with the current API. "Dynamic" targeting in addons is emulated by binding a "/target Name" macro to a frame. It has all the limitations of that macro.
since if they have used the hunter pet naming exploit we cannot target their healer
Actually you cannot use Proximo (or any kind of addon or macro) to target their healer. It seems you will have to use the raw method : clicking on the toon.
Benumbed, are you clicking the little "ok" button that appears in the text box after typing in the spell name?
psyquest, unfortunately as Adirelle already stated there is really no way around this issue. The 2.4 combat log changes don't help things either because you cannot use the unique GUID's to target with. Until Blizzard gives us a way to only target a player or some other method then you will just have to get by with manually targeting with your mouse or tab or assisting. Maybe just kill the pet first =)
- Added Talent Name display
- Added few additional Auras to watch
- Allow talents to still be obtained if one person's fails
- Fixed Right Click spell casting issue
I noticed, as the one that reports to the party, that if someone else targets them and i get them on proximo. I report them to chat but not their talents. If I am the one that targets them, it reports their talents. Dunno if thats bug or feature, just reporting it.
The issue with Talent announcements is that is takes a short time for WoW to actually return the talents the first time you see someone. I don't want the talents to hold up the announcements, so they are not there every time. However, the talents will still appear correctly in the Proximo window for everyone, and the second time you see someone in the same session they will work with announcements. Basically, it won't ever be consistent the first time you retrieve someone talents. That is why I didn't put talent announcements in to begin with, but people still requested it.
The issue with Talent announcements is that is takes a short time for WoW to actually return the talents the first time you see someone. I don't want the talents to hold up the announcements, so they are not there every time. However, the talents will still appear correctly in the Proximo window for everyone, and the second time you see someone in the same session they will work with announcements. Basically, it won't ever be consistent the first time you retrieve someone talents. That is why I didn't put talent announcements in to begin with, but people still requested it.
Ahh might be, didnt notice. I thought it was due to them targeting and me reporting it instead of me targetting it first.
Arandorus, all but one of those have to do with global string issues. Can you try two things for me to see if the issues go away (for now):
- Turn off the Grow Frame option
- Turn off the Auras option
The Auras code is going to change a lot for the 2.4 WoW patch, so I may just hold off supporting it for some languages until then. Ace3 is still new, so not all libraries have been ported over to it or LibStub yet.
how can I control Proximo2 while I'm not in the Arena? /proximo doesnt work at all? (ok done, /ace3 :P)
1-) could you add to the reporting system with options /rw and their Talent Tree, like XXXX Mage (Frost) (I solved this)
1.1 - I can only report one way, I want to report on Party char and I want to see it with SCT options at the same time or more report like whisper as well. (Only one option atm)
2-) is there any possibility to give it another function like warns HP when it is about 10-20% according to user's option?
2.1 - Wanna do it Raid Warning (not working atm I think) and Party at the same time like above option.
3-) Drink warning - It will warn raid member while one of the opponent starts to drinking.
4-) Out Of Combat Warning - If one of the opponent goes out of combat, it could report it as well, easy to be done, it will only look up how much seconds one of the opponent doesnt do anything except himself.
5-) Ressing warning - It will warn raid members while someone is trying to ress, specially good for 5v5.
oray, HP warning and drink icons are already in. I don't plan on supporting announcements to multiple locations. Proximo works bet when everyone is using it and in that case you don't need to announce to party or to raid warning. Out of combat and resurrecting are both too situational and I don't plan on adding them. If your team lets someone resurrect, Proximo isn't going to help them =)
Xinhuan, thanks for the heads up. I don't plan on supporting any of those armory database mods, so guess talents will just be going away for Proximo unless another option presents itself.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Yeah Grayhoof my lord, think about the alphabetical order only works on English client...
And there are millions of gladiators who not using English client...
I could tell how I face every spec name for every class, but I just can't make this name connected to the numbers...
Your codes were spread all over the world, so please, consider it again.
I have posted on this here and you said that is could be reported. I did and the GM stated that this was ok and not against the rules. So here we are against top team that use proximo too but with a difference, since if they have used the hunter pet naming exploit we cannot target their healer while their proximo works fine.
It would be nice if there was a way to use unique IDs in the targetting of proximo and have an option to show pets too.
This is for me currently a big show stopper until something is done (on blizzard or the mod community) to sort this out.
In short : not with the current API. "Dynamic" targeting in addons is emulated by binding a "/target Name" macro to a frame. It has all the limitations of that macro.
Actually you cannot use Proximo (or any kind of addon or macro) to target their healer. It seems you will have to use the raw method : clicking on the toon.
psyquest, unfortunately as Adirelle already stated there is really no way around this issue. The 2.4 combat log changes don't help things either because you cannot use the unique GUID's to target with. Until Blizzard gives us a way to only target a player or some other method then you will just have to get by with manually targeting with your mouse or tab or assisting. Maybe just kill the pet first =)
Thank you =P
- Added Talent Name display
- Added few additional Auras to watch
- Allow talents to still be obtained if one person's fails
- Fixed Right Click spell casting issue
The function of Talent Name display and announcement works well in the test windows but fail to announce when you came into the real arena. :-(
Ahh might be, didnt notice. I thought it was due to them targeting and me reporting it instead of me targetting it first.
Date: 2008-02-24 13:43:54
ID: 5
Error occured in: Global
Count: 10
Message: ..\AddOns\Proximo2\Proximo.lua line 631:
bad argument #1 to 'match' (string expected, got nil)
Debug:
(tail call): ?
[C]: match()
Proximo2\Proximo.lua:631: GetMaxUnit()
Proximo2\frame.lua:364: UpdateFrameHeight()
Proximo2\frame.lua:354: UpdateFrame()
Proximo2\options.lua:58:
Proximo2\options.lua:55
(tail call): ?
[C]: ?
[string "safecall Dispatcher[2]"]:9:
[string "safecall Dispatcher[2]"]:5
(tail call): ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:693:
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:519
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9:
[string "safecall Dispatcher[3]"]:5
(tail call): ?
...ace\AddOns\GatherMate\Libs\AceGUI-3.0\AceGUI-3.0.lua:204: Fire()
...te\Libs\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:51:
...te\Libs\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:47
Date: 2008-02-24 13:32:46
ID: 2
Error occured in: Global
Count: 416
Message: ..\AddOns\Proximo2\auras.lua line 117:
invalid capture index
Debug:
(tail call): ?
[C]: match()
Proximo2\auras.lua:117: ?()
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[12]"]:4:
[string "safecall Dispatcher[12]"]:4
[C]: ?
[string "safecall Dispatcher[12]"]:13: ?()
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
...AddOns\GatherMate\Libs\AceEvent-3.0\AceEvent-3.0.lua:70:
...AddOns\GatherMate\Libs\AceEvent-3.0\AceEvent-3.0.lua:69
Date: 2008-02-24 13:32:52
ID: 3
Error occured in: Global
Count: 339
Message: ..\AddOns\Proximo2\auras.lua line 96:
invalid capture index
Debug:
(tail call): ?
[C]: match()
Proximo2\auras.lua:96: ?()
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[12]"]:4:
[string "safecall Dispatcher[12]"]:4
[C]: ?
[string "safecall Dispatcher[12]"]:13: ?()
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
...AddOns\GatherMate\Libs\AceEvent-3.0\AceEvent-3.0.lua:70:
...AddOns\GatherMate\Libs\AceEvent-3.0\AceEvent-3.0.lua:69
Date: 2008-02-24 13:32:52
ID: 4
Error occured in: Global
Count: 498
Message: ..\AddOns\Proximo2\auras.lua line 103:
invalid capture index
Debug:
(tail call): ?
[C]: match()
Proximo2\auras.lua:103: ?()
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146:
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146
[string "safecall Dispatcher[12]"]:4:
[string "safecall Dispatcher[12]"]:4
[C]: ?
[string "safecall Dispatcher[12]"]:13: ?()
...ate\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:91: Fire()
...AddOns\GatherMate\Libs\AceEvent-3.0\AceEvent-3.0.lua:70:
...AddOns\GatherMate\Libs\AceEvent-3.0\AceEvent-3.0.lua:69
- Turn off the Grow Frame option
- Turn off the Auras option
The Auras code is going to change a lot for the 2.4 WoW patch, so I may just hold off supporting it for some languages until then. Ace3 is still new, so not all libraries have been ported over to it or LibStub yet.
http://img201.imageshack.us/img201/1391/scoreboardyt2.jpg
I know it is pretty much beyond the scope of a targeting addon...
1-) could you add to the reporting system with options /rw and their Talent Tree, like XXXX Mage (Frost) (I solved this)
1.1 - I can only report one way, I want to report on Party char and I want to see it with SCT options at the same time or more report like whisper as well. (Only one option atm)
2-) is there any possibility to give it another function like warns HP when it is about 10-20% according to user's option?
2.1 - Wanna do it Raid Warning (not working atm I think) and Party at the same time like above option.
3-) Drink warning - It will warn raid member while one of the opponent starts to drinking.
4-) Out Of Combat Warning - If one of the opponent goes out of combat, it could report it as well, easy to be done, it will only look up how much seconds one of the opponent doesnt do anything except himself.
5-) Ressing warning - It will warn raid members while someone is trying to ress, specially good for 5v5.
So you can probably stop working on any section of code that deals with talent inspection and their display.
Xinhuan, thanks for the heads up. I don't plan on supporting any of those armory database mods, so guess talents will just be going away for Proximo unless another option presents itself.