Just came back to WoW this week and noticed Skinner no longer is skinning the namplaces of Mobs. I doubled checked that I had updated all my addons. I tried only using skinner with no luck. I tried turning on and then off the NPC nameplate option with no luck. Is this a bug or did Blizzard do somthing new to the UI while I was gone from WoW?
I am also getting unskinned nameplates, and like Mushito tried toggling nameplates in Skinner's options with no success. I also tried just Skinner and saw the same thing.
If anyone has any info about this, it'd be awesome. The default nameplates are really rather jarring and distracting to me at this point.
hi well i am have a problem and it is that when i move the view point and look in one direction the water will drop down and i get a double image and this seems to only happen it uldum and in throne of tides i have had this happen back in 4.0.3 but then it was fix so now i get it again pls help.
Hmm, I wonder if it had something to do with TukUi and Skinner's code for it, then. They overhauled completed between version 12 and 13. Either way, I can turn icons off.
Getting the following error, but only seems to be happening when I log in on my lock if that helps.
1411x Skinner-b4.14007.1\UIElements2.lua:683: attempt to index a nil value
Skinner-b4.14007.1\UIElements2.lua:683: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
hi i love this addon :) but as of today im getting spammed with lua error after lua error :(
it still works as far as i can tell but ive had to turn off lua errors in the interface hehe :D
Interface\AddOns\Skinner\UIElements2.lua:683: attempt to index a nil value
Time: 05/15/11 20:31:53
Count: 1227
Stack: (tail call): ?
Interface\AddOns\Skinner\UIElements2.lua:683: in function <Interface\AddOns\Skinner\UIElements2.lua:679>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
...\AddOns\DataStore\libs\AceTimer-3.0\AceTimer-3.0.lua:166: in function <...\AddOns\DataStore\libs\AceTimer-3.0\AceTimer-3.0.lua:138>
Locals: <none>
hi there thank you for the update to the bug i posted :D but i seem to have aquired another one :(
Message: Interface\AddOns\Skinner\Skinner.lua:857: attempt to call method 'SetStatusBarTexture' (a nil value)
Time: 05/16/11 12:02:20
Count: 668
Stack: (tail call): ?
Interface\AddOns\Skinner\Skinner.lua:857: in function `glazeStatusBar'
Interface\AddOns\Skinner\UIElements2.lua:705: in function <Interface\AddOns\Skinner\UIElements2.lua:679>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
...\AddOns\DataStore\libs\AceTimer-3.0\AceTimer-3.0.lua:166: in function <...\AddOns\DataStore\libs\AceTimer-3.0\AceTimer-3.0.lua:138>
Locals: <none>
[40:04]Skinner\Skinner-b4.14007.2.lua:857: in function "glazeStatusBar"
Skinner-b4.14007.2\UIElements2.lua:705: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
[40:04]Skinner\Skinner-b4.14007.2.lua:857: in function "glazeStatusBar"
Skinner-b4.14007.2\UIElements2.lua:705: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
[40:04]Skinner\Skinner-b4.14007.2.lua:857: in function "glazeStatusBar"
Skinner-b4.14007.2\UIElements2.lua:705: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
[40:04]Skinner\Skinner-b4.14007.2.lua:857: in function "glazeStatusBar"
Skinner-b4.14007.2\UIElements2.lua:705: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
[40:04]Skinner\Skinner-b4.14007.2.lua:857: in function "glazeStatusBar"
Skinner-b4.14007.2\UIElements2.lua:705: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
[40:04]Skinner\Skinner-b4.14007.2.lua:857: attempt to call method "SetStatusBarTexture" (a nil value)
[40:04]Skinner\Skinner-b4.14007.2.lua:857: in function "glazeStatusBar"
Skinner-b4.14007.2\UIElements2.lua:705: in function <Skinner\UIElements2.lua:679>
(tail call): ?
<in C code>
<string>:"safecall Dispatcher[1]":9: in function <string>:"safecall Dispatcher[1]":5
(tail call): ?
Ace3-Release-r1025\AceTimer-3.0\AceTimer-3.0-5.lua:166: in function <Ace3\AceTimer-3.0\AceTimer-3.0.lua:138>
Skinner b4.13914.4 - seems to be working ok, but all versions i try to use after that are spamming me 2-3 times per second with this same error.
Just came back to WoW this week and noticed Skinner no longer is skinning the namplaces of Mobs. I doubled checked that I had updated all my addons. I tried only using skinner with no luck. I tried turning on and then off the NPC nameplate option with no luck. Is this a bug or did Blizzard do somthing new to the UI while I was gone from WoW?
V/r
If anyone has any info about this, it'd be awesome. The default nameplates are really rather jarring and distracting to me at this point.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumUpdated Ace3, Altoholic (as reported by Decabah/Gabriel/chrisgriffith25/lunamunasi) & Scrap (as reported by Decabah) skins
Updated Nameplates skin (as reported by Mushito/paks2)
Removed Patch checking code
Updated some utility functions
b4.14007.1
@Decabah, The Quartz skin never put a border around the Castbar icon AFAIK, skin hasn't changed for a while.
@Luckyjack_SL, LFD UI seems fine to me, I'm not seeing any extra textures.
@bigpete1982, Are you using the Viewport module? This was a Blizzard problem before, fix was to set water detail to Fair.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumThanks for the update.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAm getting the same on my shaman.
GuildMaster
http://wow.curseforge.com/addons/guildmaster/
Thanks again for all your hard work it is much appreciated
it still works as far as i can tell but ive had to turn off lua errors in the interface hehe :D
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBugfix for Nameplates skin(as reported by Craxziz/Greevir/Mirruan)
Bugfix for ClassTrainer skin
Patch 4.1 tidyup
b4.14007.2
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumkeep up the great work :D
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHi Gabriel,
Skinner b4.13914.4 - seems to be working ok, but all versions i try to use after that are spamming me 2-3 times per second with this same error.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBugfix for Nameplates skin (as reported by Mirruan/panthy)
Bugfix for ClassTrainer skin
b4.14007.3
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNot sure why he would link you there... It's even a completely different addon from this: http://www.wowinterface.com/downloads/info18942-GuildMaster.html I assume this is the one he meant, since it's up to date and relevant.