📤 Sharing Workspaces (Packages)
NxMenu's Package system lets you share complete setups — menus, GUI canvases, and custom icons — between servers, team members, or as templates.
Exporting a Package
- Click ⇡ EXPORT in the top bar.
- A modal shows three columns:
- Logic Menus — Your menu configurations (slots, actions, conditions)
- Texture Canvases — Your painted GUI backgrounds from Texture Studio
- Custom Widgets — Your 18×18 icons (with their CMD numbers)
- Check the items you want to bundle. Use the TOGGLE button at the top of each column to select all/none in that group.
- Click GENERATE .ZIP. Your browser downloads a
nxpkg_xxxxx.zipfile.
The ZIP is a self-contained package with a JSON manifest. Send it to anyone running NxMenu.
Importing a Package
- Click ⇣ IMPORT in the top bar.
- Choose a
.zipor.jsonfile. - The same 3-column picker appears, showing what's inside.
- Check what you want to merge into your workspace. Items NOT checked are skipped.
- Click MERGE WORKSPACE.
Conflict Handling
NxMenu handles ID and CMD conflicts intelligently:
- Menu ID conflicts: Imported menus get suffixed with
_1,_2, etc. (e.g.shopbecomesshop_1). - Texture name conflicts: Same auto-suffix system.
- Unicode conflicts: Automatically reassigns next available F-range hex.
- CMD conflicts: The original CMD is preserved if free; otherwise the icon imports without a CMD (you assign one manually).
Sharing via URL (Texture Studio Only)
The Texture Studio also has a Share button that generates a permanent URL containing your full workspace. Anyone who opens that link clones your work into their own browser. Useful for quick collaboration without ZIP files.
💡 Real-World Use Cases:
• Selling pre-built menu templates on marketplaces
• Backing up your work to a different machine
• Sharing GUI designs with your design team
• Distributing community templates
• Selling pre-built menu templates on marketplaces
• Backing up your work to a different machine
• Sharing GUI designs with your design team
• Distributing community templates