Including your FancyMenu setup in a modpack is very easy and only takes some simple steps.
This page is ONLY for FancyMenu setups made completely in FancyMenu v3+, so if you use a legacy setup (made in v2 and converted to v3), some steps could be different.
The main thing you need to do is copy one special folder that FancyMenu uses to save all your designs.
config
Folder: Inside your Minecraft instance folder, there's usually a folder named config
. This is where many mods store their settings.fancymenu
Folder: Inside that config
folder, FancyMenu creates its own folder called fancymenu
. This is the golden folder we need!Look for a similar "Open Folder," "Open Instance Folder," or "View Files" option for your specific Minecraft setup.
config
folder of your MODPACK instance (the one you want to copy your setup to).fancymenu
folder inside, DELETE it.config
folder of the SOURCE instance (the one you want to use the setup from).fancymenu
folder inside the config
folder of your SOURCE instance to the config
folder of your MODPACK instance.Please keep in mind that old legacy setups made in FancyMenu v2 (even if converted to v3) allowed you to store layout assets outside FancyMenu's
/config/fancymenu/assets/
folder, so in that case you need to make sure you also include all of your assets in the modpack.
You surely don't want to keep FancyMenu's menu bar visible in your modpack, so you should disable it. But since people can still press the hotkey to make it visible again, let's do something a little bit more aggressive.
Navigate to /config/fancymenu/options.txt
and open the file in a text editor.
Now set modpack_mode
to true
and save the file.
This will completely disable all overlays and hotkeys.
To be able to edit your layouts again, set the config option back to false
.
This shouldn't be needed in most cases, but if you didn't close the Welcome screen yet (the screen that tells you to read the documentation), make sure to set show_welcome_screen
to false
in /config/fancymenu/options.txt
.
The screen only shows once and disables itself when clicking on the Open Documentation button, so again, doing this manually shouldn't be needed in most cases.