ESO Add-Ons on Console: How You Get Them, and What ## ConsoleDependsOn Means

What this page was checked against

Built 2026-08-22. Checked against the live game as it stood that day: interface (API) version 101050, which is Update 50, live since 2026-06-08. The next interface bump, Update 51, goes live on PC/Mac on September 28, 2026. Every rule quoted below carries the date it was fetched — all of the ESOUI quotes on this page were fetched on 2026-08-22, and the Update 51 date was verified at the ZeniMax announcement on 2026-08-19 and not re-fetched since.

How console players get add-ons

ZeniMax's own statement, republished by ESOUI in a block the sticky heads "Information about console AddOns, provided by ZOs" (fetched 2026-08-22). The announcement was written ahead of the rollout it describes, so it is phrased as a plan; quoted verbatim: "The week of June 23 2025, shortly after the Update 46 console launch on June 18, players will be able to download add-ons from within the in-game UI on next-gen consoles (Xbox Series X/S and PlayStation 5). This feature will not be available on last-gen consoles, nor on PC/Mac. (No downtime or game reload will be required.)"

We did not retrieve a source confirming that rollout landed exactly as announced. What we did retrieve, written as present practice on the same sticky and fetched the same day, is the instruction itself, verbatim: "You cannot use Minion or any other download source to install them to your console. To download and install AddOns on your console you must use the ingame addon browser on your console!"

The catalogue behind it is Bethesda.net. The sticky's opening line, verbatim: "To find AddOns installable on next gen gaming consoles, please visit this link: https://mods.bethesda.net/en/elderscrollsonline/all". For authors, the same sticky notes: "You need to create/login an existing account at Bethesda.net to use the Console AddOn uploader tool."

Two boundaries from the same ZeniMax block, both verbatim, both worth knowing before you start. On support: "The ESO team cannot assist with add-on related issues that players run into. It is up to add-on developers to fix any issues with their add-ons. We do not moderate, review, approve, QA, or guarantee ESO add-ons in any way." On scope: "please be aware that add-ons (PC and Console) for ESO are UI add-ons only. They are not like add-ons for some single-player games where you may change your character models or build/modify zones, quests, weapons, etc."

One console-specific trap, from ESOUI's troubleshooting sticky, fetched 2026-08-22, verbatim: "If you login to the same console with multiple different ESO @accounts, it could happen that login in with @account2 will deinstall the delta of addons". If you share a console between accounts and your add-ons keep disappearing, that is the documented cause.

Minion and PC add-on sites do not serve consoles

Stated by the publisher of both. ESOUI and Minion are the same organisation, so the sentence quoted above — "You cannot use Minion or any other download source to install them to your console" — is Minion's own publisher saying it, not a third party guessing.

It goes further for the website: ESOUI's troubleshooting sticky, second post (the console half), fetched 2026-08-22, verbatim: "esoui.com cannot host any console addons! You cannot download them to your console, that only technically works from bethesda's websites." And on files you will nonetheless find there, verbatim: "If you find addons here on esoui.com named like [Console]* or similar, this is just for source code reference".

An honest note on our evidence: Minion's own landing page (minion.mmoui.com, fetched 2026-08-22, HTTP 200, 5,122 bytes) is a navigation teaser and names no platform at all, and we did not read its Requirements or Supported Games detail. So the console answer above rests on the sticky — the same publisher stating it directly — rather than on Minion's own specification page.

The practical read-through: this site's add-on pages describe a PC/Mac file layout, and its folder checker reads a PC/Mac directory listing. Use them to research an add-on. Do not use them as an install route on console; the in-game browser is the only one.

## ConsoleDependsOn and ## PCDependsOn, with a real example

An add-on's manifest can declare two different dependency sets — one for each platform — using two directives most PC guides never mention. SkyShards does exactly this. Both lines quoted verbatim from SkyShards v10.64, file SkyShards\SkyShards.addon, read from our addon corpus 2026-08-22:

"## PCDependsOn: CustomCompassPins>=137 LibAddonMenu-2.0>=40 LibGPS>=73 LibMapPins-1.0>=10045" and "## ConsoleDependsOn: CustomCompassPins>=137 LibGPS>=73 LibMapPins-1.0>=10045".

The difference is one entry: LibAddonMenu-2.0. That is the library that draws settings menus, and the author left it off the console line. Reading the two lines against each other tells you something no download page does — which parts of the add-on are platform-specific and why. The same manifest also shows two other things worth recognising: it is a .addon file rather than a .txt, and it declares two interface versions on one line ("## APIVersion: 101047 101048").

Those lines name the direct requirements: four on PC, three on console. Resolving each of those libraries' own required dependencies gives the full set we show on the addon's page — 7 folders on PC and 6 on console (data/addon_deep.json, built 2026-08-22). The extra ones are libraries needed by the libraries, which is why the count on the page is larger than the count on the line.

Another real PC-only line, from AwesomeGuildStore's manifest, same corpus and read date, verbatim: "## PCDependsOn: LibCustomMenu>=680" — a PC dependency set with no console counterpart declared.

The version syntax is the same as the PC directive: >=137 means version 137 or newer, not exactly 137. The dependency guide on this site covers reading those lines in detail.

The four signals we show, and what each one is worth

Every add-on page on this site carries one of four console states, computed from that add-on's own files and listing text. Across the 3,163 addons in our 2026-08-19 feed snapshot, scanned 2026-08-22, they split like this: 37 declare console dependencies, 14 declare a PC-only split, 62 mention console in their listing text, and 3,050 carry no console signal at all.

The underlying manifest counts, separately: 37 addons declare a ## ConsoleDependsOn line, 46 declare a ## PCDependsOn line, 32 declare both, and 51 declare at least one of the two. So fewer than two in a hundred addons in the catalogue say anything at all about platform in their own files.

The single most important thing to understand about all four states: they report what the author wrote, not what the console catalogue contains. Our dataset is built from the ESOUI feed and the downloads behind it. We hold no Bethesda.net catalogue, so no state on this site is evidence about whether the add-on is actually listed on your console.

• Declares console deps (37) — the author wrote a ## ConsoleDependsOn line. Strongest signal we have that console was considered. It is a declaration, not a test, and it is not evidence the add-on is listed on Bethesda.net.
• PC-only split (14) — a ## PCDependsOn line with no console counterpart. Suggestive, not a statement: the author declared a PC set and did not declare a console one. It does not say the add-on is unusable on console.
• Mentions console (62) — the string appears in the listing text, with no direction attached. It can mean the opposite of what you hope: LibZone's listing text reads "Only on PC (not console)". Read the actual sentence, which we quote on the page.
• No console signal (3,050) — the files and listing say nothing. This is not evidence of absence. It is the normal state of the catalogue, and it means our data simply has nothing to offer on the question.

When an addon page here says "no console signal"Unverified

Take it as "we do not know", because that is all it means — 3,050 of 3,163 addons are in that state, so it is the default, not a finding.

The one catalogue that settles it is the one you can open on the console itself. Search the add-on's name in the in-game add-on browser; that browser is both the authoritative list and the only install route, per the sticky quoted above. The Bethesda.net catalogue linked in that sticky is the web-side view of the same thing.

What not to do: do not download the file from esoui.com expecting to install it. The publisher's own words, quoted in full above — esoui.com cannot host console add-ons, and a [Console]-tagged file there is source code for reading.

Two things you can still get from an add-on's page here even when the console state is unknown: its dependency list, which tells you what else must be present under any platform, and whether its code calls functions the live build removed, which is a property of the code rather than the platform.

Which of our other guides do not apply to you

The file-system procedures in the rest of this section describe the PC/Mac live folder — the paths quoted from ESOUI's install FAQ, the folder-creation rule, the full-client-restart requirement for a newly added folder, and the folder checker that reads a directory listing. Every one of those sources addresses PC/Mac explicitly. We could not establish an equivalent console file location, or a console equivalent of any of those steps, from any source retrieved on 2026-08-22.

Two things do carry across, because they are properties of the add-on rather than of the platform: the dependency directives (which is what ## ConsoleDependsOn exists for) and whether the code calls removed interface functions. The out-of-date flag mechanics, the red "Dependency" state and the error-reading procedure are all described by PC-facing sources, and we did not verify how any of them present on console.

One partial exception in the error popup: the troubleshooting sticky distinguishes input modes rather than platforms, naming "the "Show more" checkbox (keyboard mode) / the "More info" keybind (gamepad mode)". That is about the controller, not about the console, and we did not establish whether the console client shows the popup at all.

What this guide cannot tell youUnverified

Whether any specific add-on is available on your console. We hold no Bethesda.net catalogue. Every console state on this site is read from the add-on's own files and listing text, which is a statement about the author, not about the store.

Whether the June 2025 in-game browser rollout landed as announced. The quote above is an announcement written before its own date; we did not retrieve a source confirming delivery. The present-tense instruction to use the in-game browser, fetched 2026-08-22, is the evidence that it is the current route.

Where add-on files live on a console, or whether anything equivalent to SavedVariables is reachable. Unestablished from any source retrieved on 2026-08-22.

Whether the out-of-date flag, the red "Dependency" state or the Lua error popup behave the same way on console. All of those are documented by PC-facing sources only.

Minion's own platform support statement. Its landing page names no platform and we did not read its Requirements detail; the console answer here rests on ESOUI's sticky instead.

Anything ZeniMax says about add-on rules. Their Add-On Terms page returned only "This page is under translation." on 2026-08-22. The only ZeniMax add-on text we could retrieve is the block republished by ESOUI and quoted above.