I've just recently started using oRA2 and I noticed a problem with the cooldown part.
I'm the druid class leader for my guild so I'm trying to track how many battle reses are available. The cooldown window tracks my res properly, but other druids have a 30 minute cooldown timer. All druid reses are on a 20 minute cooldown since a recent patch change.
after todays update I started to recieve EVENT ROSTER UPDATE megaspam in chat. The only two "raid addons" i have are sraidframes and ora2. Turned off srf and spam is still here - so i guess its ora2
I know you can do Vote with yes/no answer, but I would like to know if its possible to select the answers of the question and have more than 2 choices ?
when you dont have the good set up for an encounters (like twins or m'uru) and you members get sick of bt/hyjal because you kill illidan since november.. its more fun to give the choice to your raiders
Been having issues with the oRA2 MT windows recently. The tank windows keep getting reset to old tank lists when promoted people log on.
Example: MT list is set to Tank1, Tank2. A promoted person logs off and this list is saved for them. MT list is then set to Tank3, Tank4. The promoted person then logs back on and their saved list is set, over writing the current MT list. List is now Tank1, Tank2 again.
This usually is not a big deal, except for when I don't notice it has happened and we pull the boss. I did ask everyone who was promoted to update their oRA2 as a couple people did not have latest version, but most did have r76320.
Since russian localization of WoW is live now, can i volunteer as a translator? If you will approve me, i'd like to ask for few hints about how do i create a language file. Thank you.
Since russian localization of WoW is live now, can i volunteer as a translator? If you will approve me, i'd like to ask for few hints about how do i create a language file. Thank you.
Yes, go ahead.
Just open all the .lua files in oRA2/ and copy the enUS section:
Alrighty, created alpha-version of the ruRU translation. The archive i have attached contains the same folder tree oRA has, but *txt files in there only have translations, not the entire data original oRA files have. I didn't modify oroginal oRA files to not accidentely mess things up.
Recently (a few weeks perhaps), oRA2's automatic change of loot mode (to master looter) no longer seems to work. It's still configured as it was but when I create a new raid it always sticks on Group Loot. Is this a problem overall or something weird on my end?
Some code digging points to this being the reason why it doesn't work:
Hmm, it's working fine for me using that described method, NeoTron.
1) Invite a person in a party.
2) Convert to raid
3) At this point oRA autoloads (disabled prior)
-> -> right here for me it changes to the set loot method automatically, immediately after oRA2 loads up. <- <-
4) /rarinvite
Sounds silly, but make sure the loot module is set to enable. oRA2 -> Loot -> check Enable. Maybe two months back it was changed to not be enabled by default.
ps: I usually use "/ora invite inviteRank 7" or /rainvite, both of these commands will automatically convert to a raid as people are invited and both of these commands auto set the loot method for me. You don't have to invite a single person and convert to a raid. /rainvite works when oRA2 is in it's "sleep mode" (for a lack of a better term).
edit: I'm mistaken, using "/ora invite inviteRank 7" does not work unless you click the oRA2 button. /rainvite does without clicking the button to turn on oRA2.
Ammo, the slash-command interface for adding/removing main tanks is not parallel when using the free option. Specifically:
You can set a main tank (targeted party member) with:
/ora mt set free
But then to remove it, you need to know the slot number:
/ora mt remove 1
This makes it pretty much impossible to create macros to interwork with the Blizzard MT/MA (quote "crappy unordered list"). And since ORA can't set the Bliz interface due to the tainted code path stuff, slash-command macros might be a good way to go for folks that are struggling with this.
I propose an additional slash command option:
/ora mt remove target
which would remove the targeted player from the MT list.
I'm no expert in Ace programming (and I haven't tested this) but I believe the following code would come close. (Needs localization.)
In .../Leader/MainTank.lua
Right after this code...
all = {
name = L["All"], type="execute", desc = L["Delete all Maintanks"],
order = 10,
},
Add...
target = {
name = "target", type = "execute", desc = "Remove target",
func = function()
if not UnitInRaid("target") then
return
end
local targetname = UnitName("target")
for i, name in pairs(oRA.maintanktable) do
if name == targetname then
mod:Remove(i)
end
end
end,
order = 11,
},
Also, is it a bug that both "[10]" and "all" use "order = 10"?
tank windows seem to have changed recently, specifically the target and targetoftarget windows, they're collecting mouse clicks/movements whilst hidden - making that entire chunk of screen real estate useless.
any chance it can go back the way it was so we can use the mouse in that area when their target and targetoftarget are hidden? (ie they have none)
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm the druid class leader for my guild so I'm trying to track how many battle reses are available. The cooldown window tracks my res properly, but other druids have a 30 minute cooldown timer. All druid reses are on a 20 minute cooldown since a recent patch change.
It was LibGuildPositions-1.0, I believe.
I know you can do Vote with yes/no answer, but I would like to know if its possible to select the answers of the question and have more than 2 choices ?
ex:
what we do now?
1) BT
2) Hyjal + start BT
3) ZA/Kara
4) Nothing
1) Get better and more decisive raid leadership
2) Get better and more decisive guild leadership
3) All of the above
-Ammo
when you dont have the good set up for an encounters (like twins or m'uru) and you members get sick of bt/hyjal because you kill illidan since november.. its more fun to give the choice to your raiders
you dont like the suggestion ? fine, say "no"
Example: MT list is set to Tank1, Tank2. A promoted person logs off and this list is saved for them. MT list is then set to Tank3, Tank4. The promoted person then logs back on and their saved list is set, over writing the current MT list. List is now Tank1, Tank2 again.
This usually is not a big deal, except for when I don't notice it has happened and we pull the boss. I did ask everyone who was promoted to update their oRA2 as a couple people did not have latest version, but most did have r76320.
Yes, go ahead.
Just open all the .lua files in oRA2/ and copy the enUS section:
And replace enUS with ruRU.
Some code digging points to this being the reason why it doesn't work:
http://fish.wowace.com/browse/WowAce/trunk/oRA2/Leader/Loot.lua?r1=72861&r2=71764
How I create a raid:
1) Invite a person in a party.
2) Convert to raid
3) At this point oRA autoloads (disabled prior)
4) /rarinvite
1) Invite a person in a party.
2) Convert to raid
3) At this point oRA autoloads (disabled prior)
-> -> right here for me it changes to the set loot method automatically, immediately after oRA2 loads up. <- <-
4) /rarinvite
Sounds silly, but make sure the loot module is set to enable. oRA2 -> Loot -> check Enable. Maybe two months back it was changed to not be enabled by default.
ps: I usually use "/ora invite inviteRank 7" or /rainvite, both of these commands will automatically convert to a raid as people are invited and both of these commands auto set the loot method for me. You don't have to invite a single person and convert to a raid. /rainvite works when oRA2 is in it's "sleep mode" (for a lack of a better term).
edit: I'm mistaken, using "/ora invite inviteRank 7" does not work unless you click the oRA2 button. /rainvite does without clicking the button to turn on oRA2.
I just went and played with it. You're right. If I log in and do /rainvite, nothing. If I enable, then disable oRA2, then /rainvite it will work.
You can set a main tank (targeted party member) with:
/ora mt set free
But then to remove it, you need to know the slot number:
/ora mt remove 1
This makes it pretty much impossible to create macros to interwork with the Blizzard MT/MA (quote "crappy unordered list"). And since ORA can't set the Bliz interface due to the tainted code path stuff, slash-command macros might be a good way to go for folks that are struggling with this.
I propose an additional slash command option:
/ora mt remove target
which would remove the targeted player from the MT list.
I'm no expert in Ace programming (and I haven't tested this) but I believe the following code would come close. (Needs localization.)
In .../Leader/MainTank.lua
Right after this code...
Add...
Also, is it a bug that both "[10]" and "all" use "order = 10"?
Cheers, and keep up the good work!
any chance it can go back the way it was so we can use the mouse in that area when their target and targetoftarget are hidden? (ie they have none)