> For the complete documentation index, see [llms.txt](https://docs.pvzm.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pvzm.net/engine/reference/menus.js/primary-operations/loadmenu.md).

# LoadMenu

Loads a menu overlay, injects its HTML, then runs its JS.

### Signature

```javascript
LoadMenu(menuId, background, extraData = {}, debounceElement) => Promise<HTMLDivElement>
```

### Parameters

* `menuId`\
  Menu identifier.\
  Used for asset URLs and the container ID.
* `background`\
  Optional background image URL.\
  Applied as `background: url(...) no-repeat`.
* `extraData`\
  Object passed into the menu script.\
  Default is `{}`.
* `debounceElement`\
  Optional DOM element to mark while loading.\
  Toggles the `cantSelect` class during fetch.

### Behavior

* Ensures `#dAll` exists via [`getDAll`](/engine/reference/menus.js/getdall.md).
* Chooses render target:
  * `#dSurface` if it exists and `display === "block"`.
  * Otherwise `#dAll`.
* Creates a full-screen container: `id="dMenu_<menuId>"`.
* Sets `z-index` to `9999 + menusAmount`.
* Appends HTML before running the menu script.
* Runs `menu/js/<menuId>.js` with `new Function(...)`.

The script receives:

* `menuContainer`
* `menuId`
* `extraData`

After mounting, it updates [`visibleMenus`](/engine/reference/menus.js/visiblemenus.md).

### Returns

The created menu container element.

### Errors

* Rejects if `#dAll` never appears in time.
* Rejects on network errors during `fetch`.
* Does not reject on HTTP `404` by itself.
* Throws if the menu JS throws.

### Example

```javascript
const menu = await LoadMenu("Options", null, { from: "pause" });
menu.classList.add("fade-in");
```

{% hint style="warning" %}
Do not load the same `menuId` twice at once. `UnloadMenu` uses `getElementById`, which becomes ambiguous.
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pvzm.net/engine/reference/menus.js/primary-operations/loadmenu.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.