✅ | 🙋 | Packaging listeners

[upbeat belfry]

Hi, I would like to know how to package a listener, since it doesn't seem to be working in the modpack I just created.

[brazen fiber]

Listeners live inside your config/fancymenu/ folder just like layouts, backgrounds, etc. Packaging them for a modpack works exactly like the rest of FancyMenu’s data:

1. Open the source instance and copy the entire config/fancymenu/ folder (it contains customization, assets, listeners, options, …).
2. In your modpack instance, delete any existing config/fancymenu/ and paste in the copied folder.
3. Restart the modpack so FancyMenu picks up the packaged listeners.

If you don’t want players to keep the FancyMenu menu bar or hotkeys, make sure to set modpack_mode=true in config/fancymenu/options.txt once the config is in place (see the Modpacks guide for that detail). You can always flip it back to false later when editing again.

More on distributing FancyMenu setups with modpacks

[upbeat belfry]

I did just that, copied the entire config fancymenu to the modpack instance, but it doesn't seem to be working

[brazen fiber]

Thanks for the follow-up! Could you share a bit more about what “doesn’t seem to be working” looks like? For example:

• Are the listeners missing entirely from the listener manager menu, or do they trigger but don’t run?
• Did you check that the config/fancymenu/listeners folder actually made it into the modpack instance after copying?
• Are you using the exact same FancyMenu version in both instances?
• Is modpack_mode still true in config/fancymenu/options.txt? (That setting hides the menu bar and can make testing harder unless you flip it back to false temporarily.)

Any extra details you can provide will help me narrow it down.

[upbeat belfry]

I don't seem to have a listeners folder in my original folder

[brazen fiber]

If there was no config/fancymenu/listeners folder in your source instance, that means no listener definitions were saved yet. To create one:

1. In a normal (non-modpack) instance, go to Customization → Manage Listeners and create the listeners you want.
2. Once saved, FancyMenu automatically writes their files to config/fancymenu/listeners/.
3. Now you can copy the entire config/fancymenu/ folder (including that new listeners subfolder) into your modpack instance, just like you tried before.

If you still don’t see the folder after creating listeners, double-check that the instance you edited actually saved the listeners (look inside the listener manager to confirm they exist). Once the folder exists, packaging works the same way as any other FancyMenu data—copy the whole config/fancymenu/ over to the modpack.

[upbeat belfry]

all I seem to have is a listener_instances file instead of a folder, is it correct?

[brazen fiber]

The listener_instances file you see is just FancyMenu keeping track of the running listener state—it’s not where your listener definitions are stored. When you actually create listeners via Customization → Manage Listeners, the mod saves each listener as its own file inside config/fancymenu/listeners/. That’s the folder you need to include in your modpack.

So to get your listeners into the pack:

1. Create the listeners in a normal instance (make sure they show up in the manager).
2. Confirm that config/fancymenu/listeners/ now exists and contains .json-like files.
3. Copy the entire config/fancymenu/ folder (which now includes listeners/) into your modpack instance, replacing whichever one was there.
4. Restart the modpack instance so FancyMenu loads those files.

If the folder never appears, double-check you actually saved the listeners before copying. Once it exists, packaging works the same as for layouts or backgrounds 😊

[upbeat belfry]

should I also have a layouts foldeR?

[brazen fiber]

Yep, your config/fancymenu/ folder should also contain a layouts folder (it holds all your saved layouts). When you package FancyMenu for a modpack, copy the entire config/fancymenu/ directory—this brings listeners, layouts, assets, options, etc. with it. Then paste that into the modpack instance’s config/ (replacing any existing fancymenu folder) and restart the game so everything loads.

If you need a refresher, the Modpacks page walks through the whole process. 😊

[upbeat belfry]

how would this layouts folder look like ?

[brazen fiber]

The layouts folder inside config/fancymenu/ just holds your saved layout files (one .txt per layout). Each file contains the serialized layout data for a screen/universal layout. When you copy your FancyMenu setup to another instance, include that entire layouts folder so the modpack can load the same layouts.

If you haven’t created any layouts yet, the folder might be empty—just create and save one in the editor to populate it. When packaging, copy the whole config/fancymenu/ (layouts, listeners, assets, options, etc.) into the modpack instance and restart so FancyMenu picks up everything.

More details are on the Modpacks page.

[upbeat belfry]

How do I exactly save the listener? I see no clear option how to do so

[brazen fiber]

When you’re in Customization → Manage Listeners (while not in the layout editor), everything you create/edit there is saved automatically—there is no separate “Save” button. Just finish configuring your listener (name it, pick the event, add its action script, etc.) and close the manager (click Done or press the close button). FancyMenu writes the listener files into config/fancymenu/listeners/ as soon as the listener exists in that menu. Once the files are there you can copy the entire config/fancymenu/ folder into your modpack instance to package the listeners.

[upbeat belfry]

I did just that and there's no config/fancymenu/listeners folder

[brazen fiber]

Thanks for confirming you used the listener manager. Since the listeners/ folder still isn’t appearing, it means FancyMenu didn’t actually generate the files yet.

Could you double-check:

1. That the listener you created is listed inside Customization → Manage Listeners (with a name and actions)?
2. That you pressed Done/closed the manager after creating it so it could persist?
3. That you’re editing the same instance whose config/fancymenu/ you’re copying into the modpack?
4. That modpack_mode is temporarily false while testing, so the menu bar (and therefore the listener manager) is actually accessible?

If it still doesn’t spawn the folder, feel free to share the exact steps you took (which listener event, whether you added actions, etc.) so I can help identify what might prevent it from saving.

🙋 | Packaging listeners

<@&1365490168563372113>

Human Help Requested

@upbeat belfry has requested human assistance.

A human moderator will help you as soon as possible. In the meantime, you can continue asking questions to the AI support bot if you'd like.

The support team has been notified.

Requested by SheepyShambler

[upbeat belfry]

Just in case for any future helpers: what I'm trying to do is package a listener that opens up a custom GUI when joining a server for the first time, this is my own modpack's server so it's fine. What's happening is that the listener_instances file (which I assume is the place where listeners are stored) is being sent correctly to all users, but it doesn't show any screens whatsoever

[brazen fiber]

If the listener manager saved anything, there should be real files inside config/fancymenu/listeners/ (one file per listener). The listener_instances file is just runtime state—Fancybox doesn’t read listener definitions from there.

Steps to make your listener travel with the pack:

1. Open Customization → Manage Listeners (outside the layout editor) and make sure your listener is listed, named, has its event/action script, and that you press Done so FancyMenu writes the files.
2. Check that config/fancymenu/listeners/ now exists and contains .json files. If it’s still missing, re-open the manager, add a simple listener, close it again, and watch for the folder’s creation.
3. Copy the full config/fancymenu/ directory (layouts, assets, listeners, options, etc.) from the work instance into the modpack instance, replacing whatever’s there. That’s the same process described in the Modpacks guide.
4. Restart the modpack so FancyMenu loads the listener files. Also make sure modpack_mode is false while testing (or toggle it back temporarily) so the menu bar/Manager stay available, then flip it to true again once everything works.

If your listener opens a custom GUI, double-check that the layout for that GUI is also included in config/fancymenu/layouts/ and that the layout is enabled on the target screen.

Listener reference: Manage Listeners & Listener variables
Packaging reference: Modpacks guide

AI Answers Paused

@upbeat belfry paused AI answers for this thread. The bot will stay quiet until resumed.

Use the toggle again to change the AI state

[upbeat belfry]

I truly don't know what I'm doing wrong, and I feel the AI is hallucinating this listeners folder it's mentioning

[brazen fiber]

Ticket Summary

User wants to package a FancyMenu listener (that opens a custom GUI when joining a server) into their modpack, but the copied config lacks a listeners/ folder so nothing works—only a listener_instances file appears, and the listener never triggers on the modpack side.

Requested by Snowyccino 🎄⛄

[weary sparrow]

There is no listeners folder. The file is where the listeners are saved.

If you ship that file, you ship all listeners.

You need to show the listener and its action script for others to be able to help you ^^

[upbeat belfry]

Hi Snowy, thank you so much for answering

for some god forsaken reason, the changes started working with a delay in deployment

Great job with this mod btw, I'm amazed at the documentation most of all

Absolutely bonkers

[brazen fiber]

Thread Marked as Solved

This support thread has been marked as solved by @upbeat belfry.

The AI helper is now disabled, but you can still continue the conversation if needed. Thank you for using our support system!

Marked by SheepyShambler

✅ | 🙋 | Packaging listeners

[upbeat belfry]

Consider this as solved, even though I have no idea why it started working overnight