submission:general

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
submission:general [2023/02/28 02:12] – hiccupsubmission:general [2024/08/12 16:15] (current) – [Required Dump Info] hiccup
Line 3: Line 3:
 Once you've dumped your games, it's time to submit the metadata to a preservation project for validating and cataloging. [[https://no-intro.org/|No-Intro]] focuses on game cartridges while [[http://redump.org/|Redump]] focuses on disc-based media. Once you've dumped your games, it's time to submit the metadata to a preservation project for validating and cataloging. [[https://no-intro.org/|No-Intro]] focuses on game cartridges while [[http://redump.org/|Redump]] focuses on disc-based media.
  
-If you are new to dumping and want to start sending in your dump information to places such as No-Intro, the below information is the minimum that's required. Complete this before submitting, so you don't have to go back and forth with the staff to verify your information.+If you are new to dumping and want to start sending in your dump information to places such as No-Intro, items in the [[#Required Dump Info]] section are the minimum that's required. The more information about a dump, the better. If you want to provide more details than the bare minimum, then please take a look at the [[#Optional info]] section below.
  
-====Basic Dump Info====+{{wst>vgpc_help}}
  
-Make a copy of the following template and fill it out to the best of your abilities. The more details the better!+==== Required Dump Info ====
  
-Check the [[submission:general-detailed|detailed submission info]] guide for instructions on generating the hash values and additional information you can include in your dump submission.+The most basic information necessary for verifying a game dump are the hashes/fingerprints generated from the ROM file as well as the dumping tool including hardware, firmware, and software version.
  
-{{wst>vgpc_help}}+**You can use [[https://www.romhacking.net/utilities/931/|GameHeader]] to get all this info in one go, on Windows (or Linux/macOS using wine/mono), or a common tool like 7-Zip, HashTab or HxD**. Or you can use built-in utilities: 
 + 
 +Size/hashes: 
 +  * **Size**: The size of the ROM in bytes. You can view this in your file manager, or on GNU/Linux and macOS, in the terminal run ''wc -c ROMFILENAME'' 
 +  * **CRC32**: On GNU/Linux and macOS, in the terminal run ''crc32 ROMFILENAME''. 
 +  * **MD5**: On GNU/Linux, in the terminal run ''md5sum ROMFILENAME''On macOS, in the terminal run ''md5 ROMFILENAME''. On Windows, in a PowerShell window run ''Get-FileHash ROMFILENAME -Algorithm MD5'' 
 +  * **SHA-1**: On GNU/Linux and macOS, in the terminal run ''shasum -a 1 ROMFILENAME''. On Windows, in a PowerShell window run ''Get-FileHash ROMFILENAME -Algorithm SHA1'' 
 +  * **SHA-256**: On GNU/Linux and macOS, in the terminal run ''shasum -a 256 ROMFILENAME''. On Windows, in a PowerShell window run ''Get-FileHash ROMFILENAME -Algorithm SHA256'' 
 + 
 +If the game is made up of a folder with subfolders, follow the [[https://dumping.guide/directory_dir2dat_guide|Dir2Dat guide]] for generating the hashes. 
 + 
 +You should also include any text/metadata file output from the dump tool or ROM checking tools used.
  
-<code -> +=== Photos === 
---Game--+PCB photos are an important, but often overlooked aspect of preservation. Along with providing some evidence that the game is genuine, they also help with verifying version numbers, manufacturing dates, and documenting component usage across games. 
 + 
 +Photos should include all sides of packaging, physical media, and the PCB, with all text clearly readable, including any imprinted/stamped text and any serials on ROM chips hidden under batteries. You may need to take photos at an angle to capture some of this information. However taking apart DS/3DS carts to get PCB photos is generally unnecessary. If possible, details/other labels that are underneath labels should also be photographed. 
 + 
 +==== Common dump info structure ==== 
 + 
 +Complete this template to the best of your abilities. 
 + 
 +<code>
 Game name: Game name:
  
---Dump-- +Dumper (person who dumped the ROM): 
-Dump tool:  +Affiliation (if applicable): 
-Dumper (who dumped the ROM):  +Dump tool: 
-Affiliation (if applicable):  +Dump date (YYYY-MM-DD): 
-Dump creation date (YYYY-MM-DD): +Dump logs:
-Link(s) to release (if applicable):+
  
 --ROM(s)/file(s)-- --ROM(s)/file(s)--
-Size in bytes: +Size (bytes): 
 CRC32:  CRC32: 
 MD5 hash:  MD5 hash: 
Line 31: Line 49:
 SHA-256 hash: SHA-256 hash:
  
---Physical media--  +Links/attachments to Cart/PCB/box photos/scans:
-Photos/scans:  +
- +
---Etc-- +
-Dump logs:  +
 </code> </code>
  
-Dump tool should include hardware, firmware, and software version.+==== Optional info ====
  
-Photos should be of the specific instance of hardware that was dumped, and should be kf all sides of packaging, physical media and the PCB (PCB photos are unnecessary for DS/3DS), with all text clearly readable, including any imprinted/stamped text and any serials on ROM chips hidden under batteries (you may need to take a separate photo(s) at an angle to capture those two). PCB photos are an important, but often overlooked aspect of preservation. Along with providing some evidence that the game is genuine, they also help with verifying version numbers, manufacturing dates, and documenting component usage across games.+This information isn't required, but maximizing the information in your submission helps the preservation community as a whole.
  
-Please note if you have modified the physical media in any way.+Aside from the hashes, items derived from the ROM file itself can be skipped if your ROM matches an existing dump. Serials are also less necessary as they can usually be transcribed from the photos/scans you provide.
  
-For DS/DSi/3DS dumps, you should provide hashes for the originally dumped (encrypted) file, plus the decrypted equivalent, made by making a copy of the file, then using [[https://github.com/SabreTools/NDecrypt|ndecrypt]]. You can use the --hash option to hash the ROM at the same time as decrypting it, saving time.+=== Game metadata ===
  
-Dump logs: any text/metadata file outputted by the dump tool or any ROM checking tools you've used+  * **Dump release date**: For public releases of prototypes, betas, or unreleased games. You should also include the build date, if known. 
 +  * **Languages**: Some games either show a language selection screen at startup or in the game options. If you haven't checked the language, note that in your submission. 
 +    *  Tip: Switching the BIOS language and fast-forwarding in an emulator can greatly speed up this process 
 +  * **ROM Region**: The region found in the ROM data. (Extractable with [[https://www.romhacking.net/utilities/931/|GameHeader]]) 
 +  * **ROM Revision**: The revision found in the ROM data. (Extractable with GameHeader) 
 +  * **ROM Serial**: The four character serial found in the ROM data. (Extractable with GameHeader, if the header includes it) 
 +  * **Physical Media Serial 2**: Secondary serial. For most carts, this is an optional "REV X" or "REV-X" (where X is a letter) on the top-right of the back label. For DS/3DS/Switch, it's a serial on the back of the cart. 
 +  * **Physical Media Stamp**: For most carts, this is two numbers imprinted on the top-left or top-right of the back label (front label for GB/GBC/GBA), possibly followed by an A or B. May need to view under a light source. Doesn't exist on DS/3DS/Switch. 
 +  * **Box Barcode**: Keep the spaces between numbers.
  
-If the game is made up of a folder with subfolders, follow this [[https://dumping.guide/directory_dir2dat_guide|Dir2Dat guide]] for generating the hashes. +Please note if you have modified the physical media in any way.
-\\ +
-\\ +
-Example: +
-<code -> +
---Game-- +
-Game name: Super Mario 1024 +
-System: Nintendo 4DS+
  
---Dump-- +DS/DSi/3DS dumps should include hashes for the originally dumped (encrypted) file, plus if it is a new ROM, the decrypted equivalent. Make a copy of the file, then use [[https://github.com/SabreTools/NDecrypt|ndecrypt]]. You can use the ''-h'' flag to hash the ROM at the same time as decrypting it, saving time. Note that wooddumper and GodMode9i produce decrypted files by default, so re-encryption with ndecrypt is needed for that instead. 
-Dump tool: Sanni's Cart Reader v3 with firmware v8.0 +
-Dumper: Nickname1234 +
-Affiliation (if applicable): https://dumping.guide +
-Dump creation date (YYYY-MM-DD): 2022-04-05 +
-Dump release date (YYYY-MM-DD) (if applicable): +
-Link(s) to release (if applicable): +
- +
---ROM(s)/file(s)-- +
-Size in bytes: 40960 +
-CRC32: 6ccc74cd +
-MD5 hash: 5cb884a924c5557477d0e91a0b9e2e5d +
-SHA-1 hash: df612f60bf925435d64535569ae8b39aacbc456d +
-SHA-256 hash: 5cecc3ef2e2791c4e19af34eb86065993a237d3599922e7f953cd97e3ff9d00b +
- +
---Physical media--  +
-Photos/scans: +
-https://dumping.guide/_media/carts/nintendo/ds/cart_front.jpg +
-https://dumping.guide/_media/carts/nintendo/ds/cart_back.jpg +
- +
---Etc-- +
-Dump logs:  +
-https://dumping.guide/_export/code/carts/nintendo/ds?codeblock=1 +
- +
-</code>+
  
 ==== Submission ==== ==== Submission ====
  • submission/general.1677546779.txt.gz
  • Last modified: 2023/02/28 02:12
  • by hiccup