Skip to content

Aedes API v3 - #3

Draft
Shob3r wants to merge 8 commits into
mainfrom
feat/api-v3
Draft

Aedes API v3#3
Shob3r wants to merge 8 commits into
mainfrom
feat/api-v3

Conversation

@Shob3r

@Shob3r Shob3r commented Sep 4, 2026

Copy link
Copy Markdown
Member

Some limitations on what I could do practically for the Gtk4-rs rewrite of Elysiae made me realise that another rewrite of the API into something a bit more sophisticated might be helpful for my long-term vision of the Elysiae project "ecosystem".

Changes

  • Aedes has been relicensed the AGPL-V3. Older versions of the Aedes codebase continue to remain licensed under BSD-3-Clause
  • Aedes has been rewritten to use hono, which has allowed me to create an endpoint that's a bit more fine-grained. I plan on creating documentation and actual bindings to Aedes at some point in the future
  • Adds support for two new games (game codes: abc, hyg)
  • The API now also supports background/video/overlay/icon assets of all locales supported by the endpoint the project scrapes from. These languages are:
    • English (US)
    • Chinese (Simplified)
    • Chinese (Traditional)
    • Korean
    • French (France)
    • German (Germany)
    • Spanish (Spain)
    • Russian
    • Indonesian
    • Japanese
    • Thai
    • Vietnamese
    • Portuguese (Brazil)
      If new languages do get added to the scrape endpoint, Aedes can be modified to search for that locale with one modification to a single line of code in the project
  • Chinese game icons are also a part of the above changes
  • To get asset data, you use the getAssets endpoint and supply a locale and game parameter (i.e. https://aedes.elysiae.app/getAssets?game=bh3&lang=en-us)
  • To get component data, you use the getComponentInfo endpoint and supply the name of the component you want to download (i.e. https://aedes.elysiae.app/getComponentInfo?component=proton)

Notes

  • The API rewrite is still not complete due to a planned fork of proton that will be modified to fit the needs to the Elysiae launcher that will have worked started on soon (and hopefully released soon too).
  • The asset optimizer script now optimizes ~300 files at once. Some sort of threading system would be very useful to prevent CPUs from getting nuked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant