Community request list
From Redump Wiki
This is a page for ideas from the community, not an official plan.
Website
| Description | Status |
|---|---|
| Ability to have photo/scan/log attachments for each dump | |
| SHA256 support | |
| MIA tracking built into database and datfiles | |
| Publisher and Developer fields | |
| Parent/clone support | |
| Store each dump as a separate object in the database, rather than having each entry be a summary of all dumps | |
| Full ISO metadata for each disc (filenames etc) | |
| Ability to edit new disc form submissions (with version history) | |
| Verification submission form | |
| Ability to submit entry change requests via form | |
| Dump tool field | |
| Dump creation date field | |
| Fields for the disc title in different languages | |
| Wiki file uploads enabled for photos/scans, for undumped lists | |
<ref> tag support in the wiki
| |
Possible issue with Jaguar CD dumps. RichWhitehouse has said:
bios decrypts its own md5 (sort of, unconventional implementation) hash of the TOC, then it creates a hash of the disc TOC, and if they don’t match it aborts. And part of the TOC data includes session lead-out times, and these Redump rips don’t specify lead-outs. It seems like this whole library needs to be dumped with proper subchannel (which includes TOC and everything else) data DiscJuggler or Trurip dumps might not have this issue. |
DATs
Nintendo - Wii
| Description | Status | Check built-in hashes for the Wii disc images. |
|---|
