> For the complete documentation index, see [llms.txt](https://docs.myarc.icu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.myarc.icu/en/feature-configuration/projects.md). # Project manager As your server grows to include dozens of menus, cutscenes, and component templates, keeping track of individual file names and folder paths by hand gets tedious. The project manager brings all of your server's menus, Effect cutscenes, reusable group templates, local `.arcpack` archives, and the online marketplace into a single graphical interface where you can create, search, preview, configure, and package your work. With the client ArcMenu Editor mod installed and the `arcmenu.admin` permission, run this command in game to open the project manager: ``` /arcmenu projects ``` You can also switch to the project manager at any time from inside the visual menu editor or Effect workspace using the shared top navigation bar. ## Project list and everyday management The **Projects** page organizes your server's menus, Effects, and templates into a folder tree. Use the search bar at the top to filter items by name, and select multiple entries using the row checkboxes, `Ctrl + Click`, `Shift + Click`, or `Ctrl + A`. Double-click any row or press `Enter` to open it in its dedicated editor, or right-click to open the context menu: * **Create**: Create a new blank menu or Effect project. You can set the project ID, subfolder path (using letters, numbers, underscores, or hyphens), canvas dimensions, and access permission. * **Configure**: Edit the global settings of a saved menu or Effect directly without opening the canvas. Configurable fields include: * Canvas geometry: `width`, `height`, `pixels-per-block` (pixel density per block), and `distance` (design baseline distance), each accepting a positive number between `0` and `100000`. * `depth-mode`: Canvas depth mode, set to either `perspective` (3D perspective) or `layered` (flat layered depth). * `permission`: Permission string required to open the menu or play the Effect (leave empty for no extra permission requirement). * Menu-specific options: `main-menu` (`true` or `false`, controlling whether shortcuts like `Shift + F` open this menu) and `open-commands` (a list of custom commands that open the menu). * **Edit**: Open the project in the visual menu editor or the Effect timeline workspace. If you already have unsaved changes in another draft, the editor prompts you to save or discard that draft before switching. * **Export**: Package the selected menus, Effects, and templates together into a single `.arcpack` archive. * **Delete**: Remove the selected projects (up to 512 items in a single batch). Deletion is transaction-protected: original files are backed up automatically under `plugins/ArcMenu/workspace-backups//`, and if any file write or reload error occurs midway, the system rolls back the entire operation. Before configuring, exporting, or deleting a project, save and close any active editing draft for that project. ## Previewing and managing group templates Filter the project list by **Templates** to browse all visual group templates stored under `plugins/ArcMenu/templates/` and its subfolders. Templates are reusable components created by selecting a `group` node in the menu editor and saving it as a template. Double-click a template in the project manager—or right-click and choose **Preview**—to render the component centered in the live game viewport so you can inspect its appearance and scale. Press `Escape` or click the back button to return right where you left off in the project manager or editor. You can select and export templates on their own, or bundle them alongside menus and Effects in the same `.arcpack` file to share with other servers. ## Local packages and installed packages Two dedicated tabs on the navigation bar manage `.arcpack` archives: * **Packages**: Lists local `.arcpack` files exported to `plugins/ArcMenu/packs/`, showing each package's title, version, description, and cover image. Select a local package to recapture project preview screenshots, edit its publishing title and description, publish it to the marketplace with one click, or delete the local archive file (deleting a local `.arcpack` file does not uninstall running projects from your server). * **Installed**: Lists external packages that have been imported locally or downloaded from the marketplace onto your server. From here you can type a filename to import a new local package, or uninstall packages you no longer need. ## Exporting an ArcPack step by step To back up your finished menus and cutscenes or share them with other server owners: 1. Save and close any active editing drafts for the menus or Effects you plan to export. 2. On the **Projects** page of the project manager, check all the menus, Effects, and templates you want to include, then click **Export**. 3. Fill out the export form with a package ID (`1`–`64` lowercase letters, digits, underscores, or hyphens, starting with a letter or digit), a version string (such as `1.0.0`), a display title, and a detailed description. If your projects reference external custom items or sounds from plugins like CraftEngine, check the option to allow external dependencies so they are recorded in the package metadata. 4. Once confirmed, the editor opens a clean view of each included project in the background and captures a live `1280 × 720` in-game preview screenshot to embed in the archive (the screenshot of the first project automatically becomes the package cover). If you press `Escape` to skip screenshot capture, the archive is still saved to the **Packages** list, where you can click **Prepare Previews** at any time to capture them later. 5. When finished, the archive is written to `plugins/ArcMenu/packs/-.arcpack` on the server. You can copy this file to another server to import it, or publish it to the online marketplace from the **Packages** tab. For details on cross-server imports, directory isolation, automatic resource pack merging, and marketplace publishing, continue to [ArcPack and marketplace](/en/feature-configuration/arcpack.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.myarc.icu/en/feature-configuration/projects.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.