What problem does this solve?
Game systems can already carry a cover (game_systems.cover_image / cover_book_id exist), but there's no first-class way for an admin to set a system's image directly. You either fall back to a book cover or leave it blank. Users want to brand a system with their own artwork.
What would you like to see?
Two complementary ways to set a system's cover image:
- Upload — an image upload in the system editor UI that populates
game_systems.cover_image.
- Folder convention — drop a
cover.<ext> or folder.<ext> image at the root of the system directory and have the scanner pick it up automatically on rescan.
Notes / implementation pointers
- The folder-artwork convention already exists for audio:
_find_folder_artwork() in backend/indexer.py matches cover.* / folder.* against IMAGE_EXTS (_AUDIO_COVER_STEMS = {"cover", "folder"}). This could be generalized to system folders during the scan.
- Precedence question to settle: uploaded image vs. folder image vs.
cover_book_id fallback — which wins, and does a rescan overwrite a UI upload (cf. how tags.json overwrites UI-set tags).
Filed for tracking.
What problem does this solve?
Game systems can already carry a cover (
game_systems.cover_image/cover_book_idexist), but there's no first-class way for an admin to set a system's image directly. You either fall back to a book cover or leave it blank. Users want to brand a system with their own artwork.What would you like to see?
Two complementary ways to set a system's cover image:
game_systems.cover_image.cover.<ext>orfolder.<ext>image at the root of the system directory and have the scanner pick it up automatically on rescan.Notes / implementation pointers
_find_folder_artwork()inbackend/indexer.pymatchescover.*/folder.*againstIMAGE_EXTS(_AUDIO_COVER_STEMS = {"cover", "folder"}). This could be generalized to system folders during the scan.cover_book_idfallback — which wins, and does a rescan overwrite a UI upload (cf. howtags.jsonoverwrites UI-set tags).Filed for tracking.