Any chance of Acheron seeing an update to work with 4.x? This add on is so much better than any of the other why did I die addons, I'd hate to see it disappear.
Any ideas on a fix for the chat box positioning bug? It's a small thing, sure, but I cant get to the chat tabs when I'm in a raid and its slightly annoying.
Thanks for all the work to get it updated after the patch.
The new Guppet skin is returning the following error on login:
(GupPet 1.210 and skinner b2.11573.4)
1x Skinner-b2.11573.4\SkinMe\GupPet.lua:30: attempt to index field 'MultiGround' (a nil value)
(tail call): ?:
<in C code>: in function `xpcall'
Skinner-b2.11573.4\Skinner.lua:781: in function <Skinner\Skinner.lua:779>
Skinner-b2.11573.4\Skinner.lua:826: in function `?'
Skinner-b2.11573.4\AddonFrames.lua:120: in function <Skinner\AddonFrames.lua:60>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Ace3):164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
Version r310 of ORA3 produces an following error on login because the methodology of creating the ready check window was changed significantly. Can someone update the ORA3 skin to handle the new ready check window?
Thanks
The following error is produced at login with the current skin:
1x Skinner-b2.11403.5\SkinMe\oRA3.lua:69: Usage: SecureHook([object], method, [handler]): Attempting to hook a non existing target
AceHook-3.0-5 (Ace3):211: in function <Ace3\AceHook-3.0\AceHook-3.0.lua:118>
AceHook-3.0-5 (Ace3):344: in function `SecureHook'
Skinner-b2.11403.5\SkinMe\oRA3.lua:69: in function <Skinner\SkinMe\oRA3.lua:2>
(tail call): ?:
<in C code>: in function `xpcall'
Skinner-b2.11403.5\Skinner.lua:780: in function <Skinner\Skinner.lua:778>
Skinner-b2.11403.5\Skinner.lua:825: in function `?'
Skinner-b2.11403.5\AddonFrames.lua:120: in function <Skinner\AddonFrames.lua:60>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Ace3):164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
I'd like to request a resizable window. A lot of the times, the bug is larger than the new, smaller window and there is no way to see the entire error short of Ctrl-A and copy/pasting it out to an external editor.
I'm looking for an add-on that lets you completely hide the blizzard boss frames (gunship battle, blood princes, etc.).
I use DXE and I don't really need or want the blizzard frames. Chinchilla lets you move them around, but it does not let you get rid of them completely.
This has been fixed in the latest version. Have you copied the updated oRA3 skin from the AddonSkins to the SkinMe folder. I have just checked this ingame and it is fine.
Ok, somehow, I managed to download the latest version and extract it somewhere totally random, so I THOUGHT I had the latest version running, but in fact I was running something completely different.
This is in fact working correctly, sorry for the confusion.
In the latest build (b2.11159.4) I am still having the problem with ORA3.
The problem is that, with the ORA3 skin enabled, all of the text on the ora raid stat panels (dura, zone, resist, etc.) is missing. You can still see the fact that there is supposed to be text there (i.e. the yellow mouse highlight is present on mouseover) but the text is not.
Here is a screen cap of with and without the ora3.lua installed:
But why would the leader be doing that? They are not in the raid. The point is to warn the leader or raid assistant that a pally has left the raid who had blessings assigned to them. Or is there something I don't understand?
I will, however, limit to telling paladins who are running PP and the leader.
Actually I think the error was being generated when the person WAS in the raid but maybe wasn't in the top 25? Not sure the specifics but the change you mentioned should make it all go away.
I would like to request an option to disable the warnings about "RaidBuffStatus: [Raidleader] is setting Pally Power for [RANDOMPALLY] but they are not in the raid/party"
I have pally power integration turned on so I can report on which pallies are slacking, however this is a bit nuts.
Some observations:
1) End-of-instance spam, should have a flag to turn it off. Couldn't find it.
Otherwise it works fine as best I could tell.
Perhaps this could be done with a Channel selection for the message. One of the channels could be Self, where the run time and avg run times are posted in your chat log, but not to party/group.
Any chances to get a "Adds Spawn" timer on Deathwhisper and possibly boat health indicators for Gunship Battle? I know there's a blizzard frame for the gunships, but it is attached to the bottom of the minimap and cant be moved.
0
0
Thanks for all the work to get it updated after the patch.
0
Sure enough - 1.217 fixed the error. I don't know how I missed that update, usually keep my stuff bleeding edge updated :/
Sorry for the false alarm.
0
(GupPet 1.210 and skinner b2.11573.4)
1x Skinner-b2.11573.4\SkinMe\GupPet.lua:30: attempt to index field 'MultiGround' (a nil value)
(tail call): ?:
<in C code>: in function `xpcall'
Skinner-b2.11573.4\Skinner.lua:781: in function <Skinner\Skinner.lua:779>
Skinner-b2.11573.4\Skinner.lua:826: in function `?'
Skinner-b2.11573.4\AddonFrames.lua:120: in function <Skinner\AddonFrames.lua:60>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Ace3):164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
0
0
Thanks
The following error is produced at login with the current skin:
1x Skinner-b2.11403.5\SkinMe\oRA3.lua:69: Usage: SecureHook([object], method, [handler]): Attempting to hook a non existing target
AceHook-3.0-5 (Ace3):211: in function <Ace3\AceHook-3.0\AceHook-3.0.lua:118>
AceHook-3.0-5 (Ace3):344: in function `SecureHook'
Skinner-b2.11403.5\SkinMe\oRA3.lua:69: in function <Skinner\SkinMe\oRA3.lua:2>
(tail call): ?:
<in C code>: in function `xpcall'
Skinner-b2.11403.5\Skinner.lua:780: in function <Skinner\Skinner.lua:778>
Skinner-b2.11403.5\Skinner.lua:825: in function `?'
Skinner-b2.11403.5\AddonFrames.lua:120: in function <Skinner\AddonFrames.lua:60>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Ace3):164: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
---
0
0
I use DXE and I don't really need or want the blizzard frames. Chinchilla lets you move them around, but it does not let you get rid of them completely.
thanks
0
Ok, somehow, I managed to download the latest version and extract it somewhere totally random, so I THOUGHT I had the latest version running, but in fact I was running something completely different.
This is in fact working correctly, sorry for the confusion.
0
The problem is that, with the ORA3 skin enabled, all of the text on the ora raid stat panels (dura, zone, resist, etc.) is missing. You can still see the fact that there is supposed to be text there (i.e. the yellow mouse highlight is present on mouseover) but the text is not.
Here is a screen cap of with and without the ora3.lua installed:
Without Skinner ORA3.LUA
Skinned:
0
Actually I think the error was being generated when the person WAS in the raid but maybe wasn't in the top 25? Not sure the specifics but the change you mentioned should make it all go away.
thanks
0
I have pally power integration turned on so I can report on which pallies are slacking, however this is a bit nuts.
0
Perhaps this could be done with a Channel selection for the message. One of the channels could be Self, where the run time and avg run times are posted in your chat log, but not to party/group.
0
Ready checks work just fine and if I delete the ORA3.LUA from the \skinme directory, it works just fine and I can see the results of the checks.
Anyone else seeing this issue? (I am running the latest beta of both).
0