Add a curated mod-asset directory and /api/mods#493
Closed
ptrlrd wants to merge 1 commit into
Closed
Conversation
Foundation for resolving modded entity art as a third fallback after main and beta on the run and live pages. data/mods.json is a vetted directory of mods whose image repos are named by the in-game entity id (lowercased), matching the official convention, so a modded id maps straight to a raw URL (<raw_base>/<paths[type]>/<id>.<ext>). /api/mods serves the directory. Seeded with WatcherMod (lamali292/WatcherMod), whose relics/cards/potions follow the convention (relic DAMARU -> relics/damaru.png, verified 200 on raw GitHub). Frontend wiring (resolve unresolved ids to the mod URL, with a placeholder as the final fallback) is the next step, since it touches several entity-image sites across the live and run components and is best done with one shared resolver.
This was referenced Jun 16, 2026
Owner
Author
|
Folded into #496, which delivers the whole modded-card feature (directory, ingest, parse, bake, backend serving, and frontend resolution) in one MR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Foundation for the third entity-art fallback (main -> beta -> mod -> placeholder) on the run and live pages, starting from the idea of a provided mod-asset repo.
data/mods.json is a curated, vetted directory of community mods. Each entry points at the mod's image repo and its per-type subpaths. Because the images are named by the in-game entity id, lowercased (relic DAMARU -> relics/damaru.png, the official convention), a modded id maps straight to a raw URL: <raw_base>/<paths[type]>/.. /api/mods serves the directory.
Seeded with WatcherMod (lamali292/WatcherMod). Verified the convention holds and that raw GitHub serves the images (relics/damaru.png -> 200 image/png).
Next step (separate PR): the frontend resolution. For a deck/relic/potion id that resolves in neither the main nor beta catalog, build the mod URL and use it, with a generic placeholder as the final fallback. That touches several entity-image sites across the live components (ticker, deck/relic/potion strips, shop) and the run page, so it is best done with one shared resolver. Hotlinking raw GitHub works for v1; mirroring vetted mods to the CDN is a later robustness step (raw GitHub has no canvas-export CORS and rate limits).
Backend only here: the directory + endpoint.