Removing 'gloss' from attribute bars?

[myslex]

Helu esoui,

Ever since I discovered theres an alternative way to display the attribute bars by adding these lines:

ZO_PlayerAttributeHealthBarLeftGloss:SetHidden(true) ZO_PlayerAttributeHealthBarRightGloss:SetHidden(true)

.. I've been inlove, and I cannot imagine going back to using the original 'glossy' version.. However there's a slight issue with this..

It would seem that some function is re-enabling the 'glossyness' when player gain a buff or loses/gain health.. It is then automatically reversed after the 'translation effect'..

Is there a way to completely disable the gloss, and preventing the default functions from 're-enabling' the gloss?

EDIT: also TL;DR
Gloss also has a 'alpha value'. Is it possible to set a 'max alpha value' to say 0 for gloss, like in this example:

ZO_PlayerAttributeHealth.playerAttributeBarObject.timeline:GetAnimation():SetStartAlpha(1.0)

Any help is grately appreciated, thank you in advance!
MYSLxxx

[Fathis Ules]

what about hooking it directly

local function newSetHidden(...)
    --origZO_PlayerAttributeHealthBarLeftGloss(...)
end
local origZO_PlayerAttributeHealthBarLeftGloss.SetHidden = ZO_PlayerAttributeHealthBarLeftGloss.SetHidden
local origZO_PlayerAttributeHealthBarRightGloss.SetHidden = ZO_PlayerAttributeHealthBarLeftGloss.SetHidden
ZO_PlayerAttributeHealthBarLeftGloss.SetHidden = newSetHidden
ZO_PlayerAttributeHealthBarRightGloss.SetHidden = newSetHidden

that's a sample of course but that's how you can change the SetHidden behaviour after you changed it once

[myslex]

Originally Posted by Fathis Ules what about hooking it directly local function newSetHidden(...)     --origZO_PlayerAttributeHealthBarLeftGloss(...) end local origZO_PlayerAttributeHealthBarLeftGloss.SetHidden = ZO_PlayerAttributeHealthBarLeftGloss.SetHidden local origZO_PlayerAttributeHealthBarRightGloss.SetHidden = ZO_PlayerAttributeHealthBarLeftGloss.SetHidden ZO_PlayerAttributeHealthBarLeftGloss.SetHidden = newSetHidden ZO_PlayerAttributeHealthBarRightGloss.SetHidden = newSetHidden that's a sample of course but that's how you can change the SetHidden behaviour after you changed it once

I must start this post with saying that I am a mediocre c# programmer, and have never worked with lua before.. and while I :REALLY: appreciate you taking the time to reply in this thread, I have no idea what to make of this proposition you made regarding hooking it directly..

Would it be to much to ask for a 'working' example, since I am too stupid to understand what you're trying to teach me?

/hugs
MYSleX

[Fathis Ules]

If :SetHidden(true) is your solution but something calls again :SetHidden(false) to revert your solution then you need to replace SetHidden by your function to filter out the calls made to SetHidden with false

In the sample I show you how to replace the SetHidden function by yours so you can decide then to pass the original execution to origZO_PlayerAttributeHealthBarLeftGloss to have the result of a normal SetHidden, or to not continue the execution , that's how you can forbid any call made to SetHidden

It is not specific to Lua, it is just called function hooking and is present in all the programming language, the only requirement is overwrite the pointer of the original function by your and to store a pointer of the original function in a local variable before you replace it so you can call later the original function from your.

local originalSetHiddenLeft = ZO_PlayerAttributeHealthBarLeftGloss.SetHidden
local originalSetHiddenRight = ZO_PlayerAttributeHealthBarRightGloss.SetHidden
 
local function newSetHiddenLeft(self, hidden, ...)
    if hidden == false then
        --do nothing, meaning, SetHidden is disabled
        return
    end
    originalSetHiddenLeft(self, hidden, ...) -- Calls the normal ZO_PlayerAttributeHealthBarLeftGloss.SetHidden
end
 
local function newSetHiddenRight(self, hidden, ...)
    if hidden == false then
        --do nothing, meaning, SetHidden is disabled
        return
    end
    originalSetHiddenRight (self, hidden, ...) -- Calls the normal ZO_PlayerAttributeHealthBarRightGloss.SetHidden
end
 
ZO_PlayerAttributeHealthBarLeftGloss.SetHidden = newSetHiddenLeft
ZO_PlayerAttributeHealthBarRightGloss.SetHidden = newSetHiddenRight

[myslex]

Originally Posted by Fathis Ules If :SetHidden(true) is your solution but something calls again :SetHidden(false) to revert your solution then you need to replace SetHidden by your function to filter out the calls made to SetHidden with false In the sample I show you how to replace the SetHidden function by yours so you can decide then to pass the original execution to origZO_PlayerAttributeHealthBarLeftGloss to have the result of a normal SetHidden, or to not continue the execution , that's how you can forbid any call made to SetHidden It is not specific to Lua, it is just called function hooking and is present in all the programming language, the only requirement is overwrite the pointer of the original function by your and to store a pointer of the original function in a local variable before you replace it so you can call later the original function from your. local function newSetHiddenLeft(self, hidden, ...)     if hidden == false then         --do nothing, meaning, SetHidden is disabled         return     end     originalSetHiddenLeft(self, hidden, ...) -- Calls the normal ZO_PlayerAttributeHealthBarLeftGloss.SetHidden end   local function newSetHiddenRight(self, hidden, ...)     if hidden == false then         --do nothing, meaning, SetHidden is disabled         return     end     originalSetHiddenRight (self, hidden, ...) -- Calls the normal ZO_PlayerAttributeHealthBarRightGloss.SetHidden end   local originalSetHiddenLeft = ZO_PlayerAttributeHealthBarLeftGloss.SetHidden local originalSetHiddenRight = ZO_PlayerAttributeHealthBarRightGloss.SetHidden   ZO_PlayerAttributeHealthBarLeftGloss.SetHidden = newSetHiddenLeft ZO_PlayerAttributeHealthBarRightGloss.SetHidden = newSetHiddenRight

This is very impressive, A new way (for me) to tackle the problem. Its kind of like overriding a function, isnt it?

However.. Hiding the 'glossy frame' and then disabling the sethidden function, still results in the 'glossyness' being shown when first aggroing an enemy thinking theres something glossy somewhere else.. Damn it!!

I appreciate you helping me out, really! thank you!
MysLEx

[myslex]

Originally Posted by myslex This is very impressive, A new way (for me) to tackle the problem. Its kind of like overriding a function, isnt it? However.. Hiding the 'glossy frame' and then disabling the sethidden function, still results in the 'glossyness' being shown when first aggroing an enemy thinking theres something glossy somewhere else.. Damn it!! I appreciate you helping me out, really! thank you! MysLEx

It seems that the game's default behaviour to fade in the attribute bar on combat begin is messing with the alpha of the 'glossy frame' .. requires further investigation.. Any help is always appreciated. Again.. thanks =)

MsysELx