✅ | fade in doesnt work

[heavy finch]

using drippy, I set the mojang loading bar to fade in but it just snaps in even though it doesnt show that when editing the layour

[south bison]

The Mojang/vanilla loading bar is a built‑in element that can’t be tweaked the same way as custom ones, so the fade option you set there won’t do anything in-game. For fades to actually work, delete that vanilla progress bar and add a custom progress bar (or “Vanilla-Like Game Loading Bar”) instead. That way you can control its appearance, including fade timing, from the layout editor.

See the Drippy docs on custom progress bars for the exact steps: Custom Progress Bars

[heavy finch]

I added the vanilla like game loading bar and it still just appearead into frame no fade no appearance delay no opacity change like i set

[south bison]

If you already enabled the built‑in fade for the vanilla‑like loading bar but it still just snaps into place, I need a bit more info to figure out what’s going on. Could you share:

1. Your Minecraft version, mod loader (Forge/NeoForge/Fabric) and the Drippy/FancyMenu versions?
2. A screenshot of the element’s settings, especially the fade/opacity section and whether it has loading requirements?
3. Whether the layout is universal or “for current screen,” and if anything else is forcing the bar to be immediately visible?

Sometimes the fade only triggers when the element is toggled (via loading requirements) or if you animate its opacity manually, so knowing how your layout is set up will help a lot. You can read how the element fade feature works in FancyMenu here: Element Opacity 😊

[heavy finch]

1.20.1 Forge, latest Fancy Menu and Drippy version

[south bison]

The fade slider on the vanilla-like bar only runs when FancyMenu gets a “hide → show” event. On the game loading screen that bar is already visible the moment the layout loads, so there simply isn’t a transition for the fade to animate — the bar just snaps in.

To get a smooth appearance you can drive the bar’s opacity yourself instead:

1. Keep using the Vanilla-Like Game Loading Bar so it still follows game_loading_progress.
2. Right‑click the element → Opacity → Set and paste a placeholder like
   {"placeholder":"game_loading_progress"}
   (or use the calculator placeholder if you want to scale it) so the bar starts fully transparent and becomes opaque as the progress value climbs.
3. If you still want a delay before the bar becomes visible, add a loading requirement (e.g., a variable toggled by a ticker after a short wait) and only show the bar once that requirement passes.

That way you get the fade-in effect you want even though the built-in fade option can’t trigger on the constantly visible loading bar.

• Element opacity docs: Element Opacity
• Progress bar hook: Custom Progress Bars

[heavy finch]

elaborate on how I get the delay

[south bison]

To add a delay before the bar even begins fading in you can use the Delay Appearance controls on the element:

1. Right-click the Vanilla-Like Game Loading Bar and open Delay Appearance → Delay.
2. Set the delay to the number of milliseconds you want the bar to stay hidden before it appears. This delay runs before the element becomes visible at all, so the fade can then start once the delay ends.

If you need more precise control (e.g., start fading only after a ticking timer), you can also:

• Add a Ticker element that waits a few ticks, then runs an action like Set Variable Value to flip a loading_bar_ready variable.
• Give the loading bar a Loading Requirement that checks Is Variable Value for loading_bar_ready:true.
• Keep the fade configured as before, so it only plays once the requirement passes and the element actually shows up.

That setup gives you both a delay and a fade without forcing the bar to be visible from the very first frame.

[heavy finch]

but i have delay apperance already set but it doesnt work still

[south bison]

The Delay Appearance slider only waits between the moment the element is allowed to show and the moment it actually renders. On the vanilla-like loading bar the layout loads with the element already “allowed”, so nothing ever triggers the delay—it’s already visible and plays the fade immediately, which makes it look like the option doesn’t work.

To force a real delay you need to keep the bar hidden until you’re ready for it to appear. Here’s a reliable approach:

1. Create a variable (e.g. loading_bar_ready) via Customization → Variables → Manage Variables, default it to false.
2. Add a Ticker element to the layout that runs on the loading screen. Set its tick delay to the amount of time you want to wait (e.g. 500ms). In its action script add a Set Variable Value action:
   loading_bar_ready:true
   (This will flip the variable to true after the desired delay.)
3. Give the loading bar a Loading Requirement: right-click it → Loading Requirements → add “Is Variable Value [FM Variable]” with the name loading_bar_ready checking for true.
   Now it stays hidden until the ticker flips the variable, so the element only becomes eligible after the delay.
4. Keep your Delay Appearance / Fade-In settings. Once the requirement passes, the element appears, the delay option actually has something to delay, and the fade runs as expected.

You can read more about customizing opacity/fades on the FancyMenu docs page: Element Opacity.

[heavy finch]

how do i do the FM variable

[south bison]

You can create and use an FM variable like this:

1. Open FancyMenu’s menu bar (Ctrl+Alt+C) and go to Customization → Variables → Manage Variables.
2. Click Add Variable, give it a name (e.g. loading_bar_ready), and leave the value as false.
3. Close the screen. Now open the Ticker you added (right-click it → Edit Action Script) and have it run a Set Variable Value action after your desired delay:

   Set Variable Value → loading_bar_ready:true
   

4. Back on the loading bar element, give it a loading requirement: right-click → Loading Requirements → add Is Variable Value [FM Variable] and set it to check that loading_bar_ready equals true.

Once the ticker flips the variable, the requirement passes and the element can show (with your fade/delay kicking in). Let me know if you’d like a screenshot of any step 😊

[heavy finch]

how many MS should i set the ticker to

[south bison]

Start with 500 ms for the ticker delay—this gives about half a second before the variable flips and lets the loading bar stay hidden long enough for the fade to matter. You can adjust that value up or down to taste (e.g., 250 ms for a shorter wait or 1000 ms for a full second).

Just make sure the ticker’s tick mode is set to something that runs on your loading screen (like “Normal” or “While Screen Is Open”) and that it runs once by having it set the variable and then stop itself (or use a short delay and disable repeat).

[heavy finch]

now my progress bar just isnt showing

[south bison]

If the loading bar never shows it usually means the requirement guarding it is still failing—loading_bar_ready is still false, so FancyMenu never lets the element render.

Double-check this flow:

1. Variable default: In Customization → Variables → Manage Variables, make sure loading_bar_ready is created and set to false. That keeps the bar hidden until the ticker says otherwise.

2. Ticker setup:

   • Set the ticker’s Tick Mode to something that runs while the loading screen is open (e.g., “Normal” or “On Screen Loaded”).
   • Set the Tick Delay to your desired wait (e.g., 500).
   • In the ticker’s action script add a Set Variable Value (FM Variable) action with the value loading_bar_ready:true.
   • Optionally add a second action that disables the ticker (e.g., disable or set variable to false), so it doesn’t keep running.

3. Loading requirement: On the progress bar element, add Is Variable Value [FM Variable] and point it at loading_bar_ready:true. That keeps the bar hidden until the ticker flips the variable.

4. Testing: Reload the layout, let the ticker fire, and you should see the bar appear with your fade/delay.

If it still stays hidden, open the Manage Variables screen while the loading screen is up and watch loading_bar_ready. If it never switches to true, the ticker isn’t firing or the action value is wrong—double-check the action script and make sure the variable name matches exactly (case-sensitive). You can read more about variables here: Variables.

[heavy finch]

it switched to true but still isnt loading

[south bison]

Because loading requirements are only re-checked when the layout reloads, the bar will stay hidden even after loading_bar_ready flips to true unless you force a refresh. Add an Update Screen action right after the ticker sets the variable:

1. In your ticker’s action script, keep the Set Variable Value action that writes loading_bar_ready:true.
2. Add another action below it: Update Screen (update_screen) (no value required). This forces FancyMenu to re-run loading requirements immediately.
3. As soon as the screen updates, the requirement sees the variable is true, the bar becomes eligible to appear, and your delay/fade can finally run.

That way the bar actually shows up after the delay instead of staying permanently hidden. You can read more about actions like update_screen here: Action Scripts.

[heavy finch]

for some reason that didnt work and then when i tried to open any of the menus like customization menu it didnt work

[south bison]

Sounds like the Update Screen action caused FancyMenu to refresh while the loading screen was still trying to load, which can mess with the editor overlay. Let’s revert to a simpler, safer setup:

1. Remove the loading requirement from the progress bar for now so it always shows again.
2. Instead of Update Screen, keep ticker simple:
   • Ticker waits (500 ms)
   • Action: Set Variable Value loading_bar_ready:true
3. After the ticker fires, manually reload FancyMenu (Ctrl+Alt+R or Customization → Reload FancyMenu) so it re-evaluates requirements. That avoids forcing a refresh mid-loading.
4. Once the bar shows again, you can re-add the requirement and rely on the manual reload (or restart the game) to let the variable take effect without triggering the problem menu state.

If you still want the delay to automatically apply each time, you’ll need to keep the ticker requirement but avoid calling update_screen while a menu is open. Instead, use an action that only runs on the next screen load (e.g., set the variable via a ticker that only ticks once when the layout opens). Let me know if you want a version of that setup—happy to explain the exact ticker settings.

[heavy finch]

i cant even open the custimization tools ui or help menu

[south bison]

If FancyMenu can’t even open the customization tools anymore, it’s because the layout is stuck in a state that keeps blocking the UI. You can fix that without opening the editor by turning off the layout manually:

1. Close Minecraft.
2. Open your instance folder, go to config/fancymenu/customization/.
3. Find the .txt file of the layout you edited (the loading screen layout you were working on).
4. Either rename it to something.txt.disabled or open it in a text editor and set is_enabled = false near the top, then save.
5. Restart Minecraft. The layout will be disabled, so FancyMenu’s menu bar/customization UI should work again.

Once you get back in, you can re-enable the layout and rebuild the delay/fade steps more carefully (e.g., keep the loading requirement + ticker but don’t run update_screen while the loading screen is still open—just restart or reload to apply). Let me know if you need help editing the layout file safely.

[south bison]

✅ | fade in doesnt work

Thread Marked as Solved

This support thread has been automatically marked as solved because there were no new messages for at least 24 hours.

If you still need help, feel free to continue the conversation or create a new support thread.

Marked automatically after 24h of inactivity

[heavy finch]

@south bison how do i take someone elses fancy menu and put it in my own