Community menus

/emenus browse

Menus other server owners have shared, browsable and installable in game.

Read this part first

A menu is not a picture. A menu carries click actions, and a [console] action runs a command as the server. Installing a menu written by a stranger is therefore running their script with full rights, in the same way installing a plugin is.

We are not going to pretend otherwise, and we are not going to put a small warning label on it either.

So nothing installs without you seeing what it does. When you click a listing, the menu is downloaded and read, and you get a screen listing every command it can run, one per slot:

• Actions that run as the server are red, and say so.
• Actions that run as the player are yellow.
• The full command line is shown, wrapped so you can read it.

Only then does an Install button appear, and on a menu with server-level commands it says Install anyway.

What we cannot check for you

The scan lists commands. It does not judge them, because it cannot. No plugin can tell lp user %player% parent add vip from lp user attacker parent add admin by looking at it. Read the red ones. If you would not type it into console yourself, do not install it.

Only players with embermenus.admin can reach any of this.

What else the plugin does

• https only. A plain http address is refused.
• No redirects. A listing cannot bounce the download somewhere else.
• 512 KB cap and an 8 second timeout. A slow or enormous file is abandoned.
• Never on the server thread. Every fetch is asynchronous, so a slow CDN cannot freeze your server.
• No path escapes. A listing may only point at files inside its own folder.

Sharing one of yours

Submit at emberplugins.online/community.

Send the file from plugins/EmberMenus/menus/, and say what it is for. Two things to do before you send it:

Take your server's specifics out. Warp names, rank nodes and IP addresses belong to you, not to whoever installs it. Leave sensible placeholders and say in the description what needs changing.

Say what it needs. If your menu only makes sense with EssentialsX or a particular PlaceholderAPI expansion, say so, and it gets fetched automatically for the person installing it.

Everything is read by a person before it appears in the listing. That is slow, and it is the only honest way to run a share hub for files that can run commands.

Running your own listing

Point the plugin somewhere else and you have a private listing for your own network, which is useful if you run several servers and want the same menus on all of them.

community:
  enabled: true
  url: "https://menus.yournetwork.com/"

That URL must serve index.yml in this shape:

menus:
  playerwarps:
    name: "Player Warps"
    author: "you"
    icon: ENDER_EYE
    description:
      - "A warp list that charges a fee."
    requires_plugins: []
    requires_expansions: [Vault]
    rows: 5
    updated: "2026-09-02"
    file: "menus/playerwarps.yml"

file is resolved against the same folder and may not contain .., a scheme, or a leading slash. Everything else is display only.

Setting enabled: false removes the browser entirely.