FS-UAE scans its Kickstarts directory and names a ROM by checksum
(src/fs-uae/config.c:121-140, main.c:431-470), opens kick.rom by name
only as a fallback (memory.cpp:1597-1606) and loads AROS when no ROM is
found (memory.cpp:2374-2379). required: true and the launcher's dialog
came from RetroPie's fs-uae.sh, which retropie.yml launchers: records.
The entry is now optional and found by content. kick13.rom stays as its
label, the name amiberry and uae4all give this 256 KB dump.
Each standalone profile records where its version is read: the source
at its pin (clk 2026-07-23-136-g9020107, shadps4 0.20.1 WIP, eden
v0.2.0-401-g26a03d2), the APK, binary or archive read (kind package),
or, where no reading can be made, kind unverified with the reason: a
host the tools cannot read, a forge gone or not answering, no build
recorded as read, a pin on another branch. Those keep their value,
unconfirmed.
100 emulator names the two platforms run had no profile, so their packs carried nothing for them. Each was read from the platform's own launcher or scriptmodule: the same program as an existing profile takes the name in cores:, a different build gets its own profile read from that version, a launcher or self-contained game goes to remove_cores, and the rest are new profiles written from their source or shipped binary. The files they need that the collection lacked are collected from the upstream distributions. Bungie and splitwolf trees are read by path and stay out of dedup.
Abdessamad Derraz