✅ | Setting button texture globally

[torpid perch]

Through the use of universal layouts, or other methods, is there a way to set the default button texture so as not to have to replace them in all menus?

[heavy solstice]

Yep! The easiest way is to create a template button that shares its custom textures with every button. You can do this in any layout (including a universal one that loads everywhere):

1. Add a custom button.
2. Right-click it → Template Settings → enable Is Template.
3. Set Share With to “Buttons” so it affects all vanilla/custom buttons.
4. Toggle on the properties you want to share (textures are always shared when set).
5. Apply your custom textures to that template button.

If you place that template inside a universal layout, its textures will automatically apply on all screens that load that layout, so you don’t need to edit every menu manually.

More detail here: Button & Slider Templates

[torpid perch]

If you say wanted to have a custom font for the buttons, is there a way to use for example placeholder: vanilla text or something along those lines to include the custom font in the template?

[heavy solstice]

You can absolutely make your template button use a custom font via a text component label. Button labels accept JSON text components, so just set the label to something like:

{"text":"Your Label","font":"your_font_name","color":"#ffffff"}

You can even inject placeholders inside that JSON if you need dynamic text (placeholders work inside strings). That way every button using the template will render with your chosen font without editing each screen.

More info on how Minecraft text components work and how to use placeholders in text from the Text Formatting guide: Text Formatting

[torpid perch]

But if you use custom text on a template button won’t it either not apply or replace the existing text of other buttons?

[heavy solstice]

Exactly—template buttons only overwrite other buttons’ text when you explicitly turn on the Label toggle in the template settings. By default only the textures (and any other toggled properties) are shared, so you can leave Label off to keep each button’s own text while still getting your custom visuals.

If you do want a unified font, set the template’s label to a Minecraft text component (e.g. {"text":"%placeholder...%","font":"your_font"}) and enable the Label toggle so every templated button uses that component. Otherwise leave Label disabled and just share textures—every button keeps its own wording. 😊

More on this: Button & Slider Templates

[torpid perch]

How would you go about the templated custom font not replacing existing text?

[heavy solstice]

To keep every button’s original text while still styling them with a custom font, don’t enable “Label” in the template settings. That way the template only shares the textures (and whatever other toggles you choose) and it won’t overwrite the buttons’ existing text.

If you still want to force a font via a template, you’d have to replace the labels with a JSON text component that specifies the font—but that will override the text, so you’d have to manually re-enter each button’s label (or use placeholders per button). There’s no built-in way for a template to change the font without replacing the label content.

More info: Button & Slider Templates

[torpid perch]

How do you request features, create an issue on GitHub?

[heavy solstice]

The docs don’t cover the process, so I can’t give detailed guidance here. The usual place for feature requests or bug reports is the FancyMenu GitHub repo—just open a new issue there (make sure to choose the correct issue template and include relevant info). If you need help with that, feel free to request a human so they can walk you through it.