ESO Addon Index

A curated, peer-reviewed registry of Elder Scrolls Online addons

⚠️ This is an experiment. Do not rely on this site... yet.

-
Addons
-
Authors

Browse Addons

Loading addons...

API Endpoints

All endpoints are static JSON served via GitHub Pages.

Full Index

Complete addon list with all metadata

https://xop.co/eso-addon-index/index.json

Minified Index

Smaller payload for production use

https://xop.co/eso-addon-index/index.min.json

Version History

Historical versions for all addons

https://xop.co/eso-addon-index/version-history.json

Atom Feed

RSS/Atom feed of version updates

https://xop.co/eso-addon-index/releases.atom

JSON Feed

Feed format for updates

https://xop.co/eso-addon-index/feed.json

Missing Dependencies

Dependencies referenced but not in index

https://xop.co/eso-addon-index/missing-dependencies.json

Get Started

Download an addon manager that uses the ESO Addon Index, or build your own using our API.

View on GitHub Client Docs View Raw JSON

Building an Addon Manager?

Check out our Client Integration Guide for detailed documentation on consuming the index, resolving dependencies, and handling different addon packaging structures.

About the Project

The ESO Addon Index is a decentralised, community-controlled, curated registry of Elder Scrolls Online addon metadata. We store only metadata - addon source code remains in author-owned repositories.

🔎

Peer Reviewed

All submissions are reviewed for quality, security, and accuracy before inclusion.

🔄

Auto Updates

Daily polling for new releases keeps version information current.

🔒

Security Scanned

Automated checks for suspicious patterns like shell commands or external network calls.

🚀

Open Source

MIT licensed. Build your own addon manager or contribute to the index.

Submit Your Addon

Have an ESO addon on GitHub? Get it listed in the index!

Submit Addon

For Addon Authors

Best practices for packaging and versioning your addon for the index.

Versioning with GitHub Releases

The index polls GitHub every 6 hours for new releases. Use semantic versioning with GitHub Releases or tags for automatic update detection.

Recommended: GitHub Releases

Create a GitHub Release with a semver tag (e.g., v1.2.3 or 1.2.3). The index uses the tag name as the version and provides the release ZIP as the download URL.

# Semantic versioning format: MAJOR.MINOR.PATCH # Examples of valid version tags: 1.0.0 # Initial release 1.1.0 # New feature (backwards compatible) 1.1.1 # Bug fix 2.0.0 # Breaking change v1.2.3 # "v" prefix also supported # Creating a release via GitHub CLI: gh release create 1.2.0 --title "Version 1.2.0" --notes "Added new feature X"

Repository Structure

Your addon can live at the repository root or in a subdirectory.

# Option 1: Addon at repository root (recommended for single addons) MyAddon/ MyAddon.txt # ESO manifest (required) MyAddon.lua # Main code README.md # Documentation LICENSE # License file # Option 2: Addon in subdirectory (common for libraries) ESO-LibAddonMenu/ LibAddonMenu-2.0/ # <-- Specify this path in source.path LibAddonMenu-2.0.txt LibAddonMenu-2.0.lua README.md LICENSE

Manifest Requirements

Your addon must include a valid ESO manifest file (.txt) with required fields.

# Example: MyAddon.txt ## Title: My Addon ## Description: A brief description of what the addon does ## Author: YourName ## Version: 1.2.3 ## APIVersion: 101044 ## SavedVariables: MyAddonSavedVars # Optional: Declare dependencies ## DependsOn: LibAddonMenu-2.0 ## OptionalDependsOn: LibCustomMenu

Keep Versions in Sync

The version in your manifest (## Version:) should match your GitHub release tag. Addon managers may use either source for version comparison.

Files to Exclude

The index automatically excludes common non-addon files from install instructions. Keep these at your repo root, not mixed with addon code.

# Automatically excluded from addon installs: .* # Hidden files (.git, .github, .gitignore) .github/ # GitHub Actions, templates tests/ # Test files *.md # Markdown files (README, CHANGELOG) *.yml, *.yaml # CI/CD configs LICENSE # License file (kept in repo, not needed in-game)

Submission Checklist

Before submitting your addon to the index:

☑ Repository is public on GitHub (or GitLab)

☑ At least one release or tag exists with a semver version

☑ Valid ESO manifest file with ## Title: field

☑ License file or license field in manifest

☑ No malicious code (shell commands, external network calls)

☑ Dependencies listed if your addon requires other addons

Submit Your Addon

License & Attribution

MIT License

Copyright (c) 2025 brainsnorkel

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.

Thanks & Attribution

Addon Authors

Thank you to all the addon developers who create amazing tools for the ESO community. This index exists to help players discover your work.

ESO Community

Built for and by the Elder Scrolls Online community. Special thanks to everyone who contributes submissions, reviews, and feedback.

ESOUI

Respect to ESOUI.com - the original ESO addon hub that has served the community for years.

Open Source Tools

Built with Python, TOML, Luacheck, and GitHub Actions. Hosted on GitHub Pages.

Elder Scrolls Online and all related trademarks are property of ZeniMax Media Inc.
This project is not affiliated with or endorsed by ZeniMax or Bethesda.