Classic Floating Combat Text

Classic Floating Combat Text

514k Downloads

[SoD] ClassicFCT nil value error; possibly due to Scrolling Function changes

illutian opened this issue ยท 4 comments

commented

I believe this is caused by Blizzard depreciating how 'scrolling' worked in the Era Client.

1x ClassicFCT/config.lua:637: attempt to index a nil value
[string "@ClassicFCT/config.lua"]:637: in function `?'
[string "@ClassicFCT/config.lua"]:1383: in main chunk

Locals:
self = ClassicFCTConfigPanel_ClassicFCT_ScrollChild {
Container = ClassicFCTConfigPanel_ClassicFCT {
}
widgets =

{
}
widgetCount = 15
}
label = "Animation Duration"
tooltip = "Animation length in seconds"
parent = FontString {
}
point1 = "TOPLEFT"
point2 = "BOTTOMLEFT"
x = 20
y = -24
minVal = 0.100000
maxVal = 5
step = 0.100000
defVal = 1.500000
ConfigPathOrFunc = "Config.animDuration"
slider = ClassicFCTConfigPanel_ClassicFCT_ScrollChild_Frame15 {
tooltipRequirement = "Default: 1.5"
tooltipText = "Animation length in seconds"
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "ClassicFCTConfigPanel_ClassicFCT_ScrollChild_Frame15"
(*temporary) = "BOTTOMLEFT"
(*temporary) = 20
(*temporary) = -24
(*temporary) = "attempt to index a nil value"

commented

Seems like the creator has stopped playing or something? Can a fan upload a fix to it so it works again for SoD? I really need this mod.

commented

I have stopped playing but I'm committed to fixing the addon. I'm back home on 11th of October. I will explore the issue before that but I cant test changes in the game (because I don't have the client and the internet here is bad). So if the fix isn't something obvious I'll fix it on 11th.

commented

It might be from the fact Blizzard, in their infinite "wisdom", removed the scrolling function from the Era client. But then reversed and re-added it.

So far, I haven't gotten the error to happen again since the last maintenance, when they supposedly re-added the scroll function.

commented

Interestingly the error you've provided would happen when the code fails to retrieve subelements of a blizzard value slider. It's something I'd have to be in the game to test so can't do it until 11th.