Some GUI question

It's indeed a bit tricky to get the names/paths of the built-in UI elements... for this reason we've added a small tool which can be enabled by typing uidebugger into console - it shows the path of the currently hovered element in the top left corner of the screen

While this tool is active, you can also rightclick on an element to copy the UI path to clipboard. To close the tool, just hit the X in the top left corner (if you can't hit it properly, press ESC and try to hit it again).

This enables you to get the paths of most elements For instance, the path to the inventory background would look like this: InventoryLayer/inventoryContainer etc.

Unfortunately you can't access all elements this way. To overcome this limitation, you could also type uidebugger <layername> into console - this prints the paths of all elements on a particular layer into console.

But if there is a particular UI element you're looking for, just let me know and I can post the path here

Quote from paulevs

I noticed one thing - some elements will ignore style changes, is this related to overriding style by the game itself during player value updates (like hunger)?

Hmm... which elements do you mean exactly? And which style change do they ignore specifically?

The game indeed changes certain style paramters of some elements, e.g. the DisplayStyle of stamina and breath bar or the broken bone icon. For some elements the backgroundImageTintColor gets also changed (e.g. for the hunger and thirst icons), but that shouldn't interfere with other style changes

Quote from paulevs

Another thing that I notices is that stamina value in player is not updated correctly on server side, it is always 100 and if you will spend a lot can instantly change to 20 or other number, and then back to 100. Default player UI shows it correctly. Is it possible to get correct player stamina?

Oh, indeed That seems to be a bug... thanks for bringing this to my attention!

Quote from paulevs

I also have another question - how do make elements behave similar to built-in during screenshot capture? I mean that built-in can be hidden during screenshot and I'm not sure how to reach same behaviour

Right now the screenshots only hide the HUD (and its content)... but probably it makes sense if API elements attached to the HUD (which is the default attach target) are only hidden on screenshots... we'll change that

Quote from paulevs

Thirst and stamina ignores visibility, opacity, width and height:

Hmm... changing visibility, opacity, width or height for the thirst or hunger icons work properly on my end

Style s1 = new Style();
s1.width.set(100);
s1.height.set(200);
s1.opacity.set(1f);
Internals.overwriteUIStyle(player, "HudLayer/hudContainer/statusContainer/rightContainer/statusIconContainer/thirstIcon", s1);

Style s2 = new Style();
s2.width.set(200);
s2.height.set(100);
s2.opacity.set(0.2f);
Internals.overwriteUIStyle(player, "HudLayer/hudContainer/statusContainer/rightContainer/statusIconContainer/hungerIcon", s2);

However, for the "thirstLabel" and "hungerLabel", the game indeed overwrites the visibility (everytime the inventory is opened). To get rid of these labels, you could set display to DisplayStyle.None though

Quote from paulevs

Bar container also ignore same style changes: HudLayer/hudContainer/statusContainer/statusBarContainer/barContainer

That also works on my end (at least visibility and width/heigh [although that doesn't change the progress bar size of course, because it's just the container])

Quote from paulevs

Another small question - how does the game handle when player heal broken bones status?

Unfortunately this isn't exposed yet... but we could add a hasHealedBones() method with the next hotfix

Quote from paulevs

I think that I found an answer - if the style is created on plugin startup and applied to several elements it will change only the first element. Looks like style argument will be mutated, and if it will be applied to the next element it will not have effect.

Yes, in fact each Style field has a "dirty" flag which is set whenever a property is changed. When applying the Style, the game only serializes the dirty properties (and removes the dirty flag at the same time). So when reusing the Style object, it no longer has any dirty flags.

For regular, built-in UI elements this usually makes sense (because you can't assign Style objects anyway), but when overriding game UI elements (through the Internals method), it's probably better if the fields remain "dirty" after serialization. We will change that with the upcoming hotfix, so Style objects will be reusable when overriding UI elements Until then, the workaround is indeed to create a new Style object everytime you override an element (which is a bit cumbersome unfortunately)^^