Skip to content

Contributing

Joe edited this page Aug 5, 2026 · 3 revisions

Thank you for your interest in contributing to Epithet!

Reporting Title Data Issues

Title data (source, rarity, category, obtainability) is generated by an offline sibling tool, not hand-edited in this repo — see Title Data Generation. If you spot a missing title, wrong field, or an obtainability change, please open an issue using the matching template rather than a generic bug report:

Template When to use
New Title A title exists in-game but is missing from the database
Title Correction Any field on an existing title is wrong (rarity, source, type, etc.)
Obtainability Change A title was removed, re-added, or made seasonal in a patch
Bulk Update Multiple titles added/changed in a single patch or event
Feature Request An idea for a new feature or improvement

Please include patch notes, in-game screenshots, or other official sources as evidence where possible.

Contributing Translations

Epithet's own translation system is not AceLocale — it's a small custom locale registry (Locales/LocaleManager.lua) with per-language files that fall back to the English base for anything untranslated. The full walkthrough — adding a new language, encoding gotchas, bundled fonts for non-Latin scripts, translating the title database, and the validator scripts — lives on its own page: Locales and Translations.

The short version:

  1. Copy Locales/enGB.lua to Locales/<locale>.lua and translate the right-hand side of each L["KEY"] = "..." line.
  2. Register the new file in LocaleManager.lua and Epithet.toc.
  3. Run scripts/validate/validate-locales.ps1 and fix anything it flags.
  4. Submit a Pull Request with your changes.

Named Locale Contributors

  • Hubbotu — contributed to the ruRU locale/lang files.

Submitting Pull Requests

  1. Fork the repository.
  2. Create a feature branch (git checkout -b feature/my-new-feature).
  3. Commit your changes (git commit -am 'Add some feature').
  4. Push to the branch (git push origin feature/my-new-feature).
  5. Open a Pull Request.

See docs/RELEASE_NOTES.md in the repo for the full version history.

Clone this wiki locally