General dat notes: Difference between revisions

From No-Intro ~ Wiki
Jump to navigation Jump to search
mNo edit summary
 
(112 intermediate revisions by the same user not shown)
Line 1: Line 1:
* Do not add dump to DoM unless you are going to add it properly+fully and have got as much info off the dumper as you reasonably can.
* Serials should be separated with a comma and no space
* Serials should be separated with a comma and no space
* Box barcodes should be added on their own line in Comment+ like<br><code>Box barcode: X XXXXX XXXXX X<tab>XXXXX</code><br>(preserving spaces if there are any and putting an actual tab to represent gaps between different "barcode boxes"). Put a comma (no space) if the two barcodes are completely separate.
* HTTP response headers should be attached to the file as a unique attachment.
* Publisher/developer serials on carts should be recorded in their own line in Comment+ like<br><code>[Company name] serial on [box/cart] [front/back]: XXXXXXXX</code>
* anonomous dumper names like <code>!anon-YYYY-MM-DD-########</code> can be used to uniquely identify an anonymous dumper, where YYYY-MM-DD is the GMT date the id was generated and ######## is a randomly generated lowercase alphanumeric 8-character string. The same id should be used across multiple dumps by the same anonymous person.
** For consistency, list Company names used in DoM for this purpose here:
* If the ROM was dumped as trimmed (dumping tool guesses or checks when the "real" data ends), but then restored from the header field, you can add: <code>[Dumped as trimmed, restored from header]</code> to the comment1 field
*** Activision
* If the dump date is from the http response header(s) date field, put <code>[Date from HTTP headers]</code> in the comment2 field.
** If you don't know what code company (if any) they are for, just put them down as for example <code>Additional cart front serial</code> in the Comment+
* If the file sizes are from the http response header(s) length field, put <code>[Sizes from HTTP headers]</code> in the comment2 field.
* If the language hasn't been checked, make a discussion called <code>!langs-not-checked</code>. The body of the discussion doesn't have to the same.
* The "Original Format" field in sources has been batched-modified to set it to the default format (e.g. Decrypted for DS). But for some sources, the default format may be something else - these will need to be corrected.
* HTTP response headers should be added in the Comment+, each starting with <code>!http-response-header-start</code> and then a newline and ending with a newline and <code>!http-response-header-end</code>. To specify what file the header is for, use <code>!http-response-header-define: filename</code> on the line before behind each <code>!http-response-header-start</code>.
* Dumper names set for Forest of Illusion releases may not always be correct, as these releases don't usually explicitly state who dumped the ROM, but do often provide credit to people who had an unspecified role.
[[Category:Datting guides]]
* Some "two games in one cart" entries have languages set like "Es,It+En,Es,It,Sv,Da". The "+" is the game separator - first set of languages is for one game, second set is for another.
* PC game platforms should be added as <code>!pc-platform-[platform]</code> each on line on the sticky note (e.g. <code>!pc-platform-windows</code>). Valid values: windows, mac, linux.
 
* anonomous dumper names like <code>!anon-YYYY-MM-DD-###############</code> can be used to uniquely identify an anonymous dumper, where YYYY-MM-DD is the GMT date the id was generated and ############### is a randomly generated lowercase alphanumeric 16-character string.
==Fields==
* If the ROM was dumped as trimmed (dumping tool guesses or checks when the "real" data ends), but then restored from the header field, you can add: <code>[Dumped as trimmed, restored from header]</code> to the comment2 field
===Archive===
{| class="wikitable"
!Field
!Explaination
|-
|Number
|
<pre>
numbering order is based on "dump date" of non-scene dump or "release date" of scene release.
 
most dats just use normal numbering (nnnn), but some dats use this format:
 
nnnn = scene releases
xnnn = scene other (demo, proto, pirate, etc)
xBnn = scene bios
znnn = non scene (p2p, trusted dump, etc)
</pre>
|-
|Special
|Comma+space seperated values.
|-
|Game ID
|This is for game serials from external sources that are approximately matched to the game. E.g. serials from official sites, shops that list the serial like Play-Asia, unofficial game lists, ROM checker tools that lookup in an external database, etc. Should only be as a stop-gap and shouldn't be filled in if the source/file has a serial filled in.
|-
|Version2
|For switch, this is for the user-facing version string from the NACP file
|}
 
===Source===
{| class="wikitable"
!Field
!Explaination
|-
|Session
|Generally, this shouldn't be used.
|-
|Title on media
|Generally, this shouldn't be used.
|-
|Origin
|This should only be used if the origin is non-standard for that system. E.g. just leave it blank instead of putting "Retail cart".
|}
 
===File===
{| class="wikitable"
!Field
!Explaination
|-
|Date
|Generally, this shouldn't be used, as it is put into the datfile, and ROM managers may change the local file date to match this, which may be undesirable.
|-
|File version
|This should only be used if an archive encompases multiple game versions (e.g. Nintendo CDN stuff).
|-
|Origin
|This is a WIP alternative to making "Trusted Modification" sources, and shouldn't be used for now.
|-
|Serial
|
|}
 
==Extra Fields==
Note: Extra (aka custom) fields only exist for archives atm
 
===Archive===
{| class="wikitable"
!Field
!Explanation
|-
|Original Name
|
|-
|Original Name (x)
|Where x is the language.
|-
|Languages (Voice)
|
|-
|WikiData ID
|To enable cross-linking with other databases. E.g. "Q11168" (https://www.wikidata.org/wiki/Q11168 - page for Super Mario Bros.)
|}
 
==Tags==
Documentation for common "tags" that are used in comment fields.
===Archive===
====Sticky Note====
{| class="wikitable"
!Tag
!Explanation
|-
|!pc-platform-[platform]
|For IBM PC digital. Values: windows, mac, linux. e.g. !pc-platform-windows
|-
|[Original title: x]
|Where x is the original title. To be used if the Media fields aren't enabled for that dat yet.
|-
|[On redump]
|Used for archives in the Non-Redump sections that have been set to "not in dat" "unlisted" due to the ROM being added to redump.
|}
 
====Datter Note====
{| class="wikitable"
!Tag
!Explaination
|-
|!pc-platform-[platform]
|For IBM PC digital. Values: windows, mac, linux. e.g. !pc-platform-windows
|-
|[Original title: x]
|Where x is the original title. To be used if the Media fields aren't enabled for that dat yet.
|-
|[On redump]
|Used for archives in the Non-Redump dats that have been excluded due to the ROM being added to redump.
|-
|[Languages not checked]
|
|-
|[Dumper has been asked for more info]
|
|-
|[Title is not romanised properly]
|-
|[Title may not be romanised properly]
|
|}
 
===Source===
{| class="wikitable"
!Field
!Explaination
|-
|Release date
|Used for high-profile dump releases of prototypes and similar
|}
 
 
====Comment 1====
{| class="wikitable"
!Tag
!Explaination
|-
|[Trimmed]
|Used to mark something as trimmed without using the "Trimmed" ROM status, which sets the source as bad.
|-
|[Untrimmed]
|For Trusted Modification sources.
|-
|[Dumped as trimmed, but untrimmed for hashing]
|For use if you want to mark something as "dumped as trimmed", but want to put the proper non-trimmed hash.
|-
|[Overdump removed]
|For Trusted Modification sources.
|-
|[Modification of file: {size}-{sha256}]
|For Trusted Modification sources. size = Size in bytes, sha256 = sha256 of file, all caps
|-
|[Internal checksum mismatch]
|Internal checksum doesn't match data.
|-
|[Standalone fix]
|For Satellaview Trusted Modification sources that contain fixed standalone ROMs for games in a Memory Pack.
|-
|[Marked as deleted]
|For satellaview ROMs that were marked as deleted (blanked header)
|-
|[Loose files]
|For sources that just have the filesystem contents instead of a ROM/disc image
|-
|[Not redump standard]
|Used for things in Non-Redump dats that are not redump standard, but only for "[On redump]" archives. Don't put it on everything.
|-
|[Redump standard]
|Used for things in Non-Redump dats that are actually redump standard, just not in redump.
|-
|[edcchk v{version} {doesn't} report{s} error(s)]
|For CD images in non-redump dats. E.g. "[edcchk v1.26 doesn't report error(s)]"
|-
|[CD dump in ISO format]
|For CD dumps that are marked as bad due to just being an ISO dump rather than a full track dump.
|-
|[grw0 partition not in factory state]
|For PlayStation Vita PSVGameSD dumps that have grw0 partitions, and have been played, meaning the partition has been written to since the cart came out of the factory. Use in conjunction with the "HasSave" ROM status.
|-
|[mdf format]
|For disc images in mdf/mds format.
|-
|[ROM status set to "other" due to dump origin]
|Used when dump status is set to "other" due to a non-standard dump origin (which should be set in the dump origin field)
|-
|[Media was unused]
|Physical media unused before it was dumped. Only relevant for media where the software portion is (easily) rewritable like floppy disks.
|-
|[Unused save was all FF bytes]
|The factory-state save was all FF bytes.
|-
|[GodMode9 txt file lists no save chip ID]
|For DS/3DS dumps
|}
 
====Comment 2====
{| class="wikitable"
!Tag
!Explaination
|-
|[Asked dumper for more info]
|To be used when the dumper hasn't provide pictures, etc, you've asked them for this extra info/data and are waiting.
|-
|Demo {part/article} number (from barcode text): {number}
|The demo "part" (for US)/"article" (for Europe) number thats printed under the barcode on the sticker on some Nintendo DS/3DS demo carts. Keep the spaces.
|-
|Demo {part/article} number (from actual barcode): {number}
|Same as above, but for the number parsed from the actual barcode, e.g. using the "zbarimg" software. Don't add spaces.
|-
|[Cart barcode read with barcode reader]
|Put this if you have scanned the actual barcode bars (using barcode scanner software) for the cart barcode, and they match the numbers written below it. Was formerly "[Cart barcode scanned]". Todo: change instances of this to match the new wording.
|-
|[Released by: x]
|For public releases when the dumper isn't the one who released it
|-
|[PCB serial transcribed from physical media]
|For when the DS/3DS PCB serial is too blurry in the photo, but the dumper transcribed it from the physical media so its still recorded accurately.
|-
|[Comment from release: "x"]
|For public releases (protos etc), where the releaser has put a comment containing credits to contributor(s).
|-
|[HTTP Response Header Last-Modified: x]
|If you just want to put the last-modified date from the http header, and not the whole header.
|-
|[HTTP Response Header Last-Modified for file "x": x]
|Same as above, but specifying the file
|-
|[Parameters removed from Link x as they contained sensitive info]
|For when the URL parameters (?uniqueid=12345 - that sort of thing) have been removed from the Link [number] as they contained sensitive info
|-
|[Latest title version as of download appended to cetk filename]
|For 3DS CDN dat
|-
|["file/foldername1" downloaded using the "filename2" program]
|For digital PC dats where the website provides an installer that downloads data from the web.
|}
 
===File===
====File note====
{| class="wikitable"
!Tag
!Explaination
|-
|[Passes verification with hactool [version]]
|For Switch cart dat. To indicate that XCIs pass when running <code>hactool -t xci -y file.xci<code>.
|}
 
[[Category:Dat notes]]

Latest revision as of 09:49, 6 June 2023

  • Serials should be separated with a comma and no space
  • HTTP response headers should be attached to the file as a unique attachment.
  • anonomous dumper names like !anon-YYYY-MM-DD-######## can be used to uniquely identify an anonymous dumper, where YYYY-MM-DD is the GMT date the id was generated and ######## is a randomly generated lowercase alphanumeric 8-character string. The same id should be used across multiple dumps by the same anonymous person.
  • If the ROM was dumped as trimmed (dumping tool guesses or checks when the "real" data ends), but then restored from the header field, you can add: [Dumped as trimmed, restored from header] to the comment1 field
  • If the dump date is from the http response header(s) date field, put [Date from HTTP headers] in the comment2 field.
  • If the file sizes are from the http response header(s) length field, put [Sizes from HTTP headers] in the comment2 field.
  • The "Original Format" field in sources has been batched-modified to set it to the default format (e.g. Decrypted for DS). But for some sources, the default format may be something else - these will need to be corrected.
  • Dumper names set for Forest of Illusion releases may not always be correct, as these releases don't usually explicitly state who dumped the ROM, but do often provide credit to people who had an unspecified role.
  • Some "two games in one cart" entries have languages set like "Es,It+En,Es,It,Sv,Da". The "+" is the game separator - first set of languages is for one game, second set is for another.

Fields

Archive

Field Explaination
Number
numbering order is based on "dump date" of non-scene dump or "release date" of scene release.

most dats just use normal numbering (nnnn), but some dats use this format:

nnnn = scene releases
xnnn = scene other (demo, proto, pirate, etc)
xBnn = scene bios
znnn = non scene (p2p, trusted dump, etc)
Special Comma+space seperated values.
Game ID This is for game serials from external sources that are approximately matched to the game. E.g. serials from official sites, shops that list the serial like Play-Asia, unofficial game lists, ROM checker tools that lookup in an external database, etc. Should only be as a stop-gap and shouldn't be filled in if the source/file has a serial filled in.
Version2 For switch, this is for the user-facing version string from the NACP file

Source

Field Explaination
Session Generally, this shouldn't be used.
Title on media Generally, this shouldn't be used.
Origin This should only be used if the origin is non-standard for that system. E.g. just leave it blank instead of putting "Retail cart".

File

Field Explaination
Date Generally, this shouldn't be used, as it is put into the datfile, and ROM managers may change the local file date to match this, which may be undesirable.
File version This should only be used if an archive encompases multiple game versions (e.g. Nintendo CDN stuff).
Origin This is a WIP alternative to making "Trusted Modification" sources, and shouldn't be used for now.
Serial

Extra Fields

Note: Extra (aka custom) fields only exist for archives atm

Archive

Field Explanation
Original Name
Original Name (x) Where x is the language.
Languages (Voice)
WikiData ID To enable cross-linking with other databases. E.g. "Q11168" (https://www.wikidata.org/wiki/Q11168 - page for Super Mario Bros.)

Tags

Documentation for common "tags" that are used in comment fields.

Archive

Sticky Note

Tag Explanation
!pc-platform-[platform] For IBM PC digital. Values: windows, mac, linux. e.g. !pc-platform-windows
[Original title: x] Where x is the original title. To be used if the Media fields aren't enabled for that dat yet.
[On redump] Used for archives in the Non-Redump sections that have been set to "not in dat" "unlisted" due to the ROM being added to redump.

Datter Note

Tag Explaination
!pc-platform-[platform] For IBM PC digital. Values: windows, mac, linux. e.g. !pc-platform-windows
[Original title: x] Where x is the original title. To be used if the Media fields aren't enabled for that dat yet.
[On redump] Used for archives in the Non-Redump dats that have been excluded due to the ROM being added to redump.
[Languages not checked]
[Dumper has been asked for more info]
[Title is not romanised properly]
[Title may not be romanised properly]

Source

Field Explaination
Release date Used for high-profile dump releases of prototypes and similar


Comment 1

Tag Explaination
[Trimmed] Used to mark something as trimmed without using the "Trimmed" ROM status, which sets the source as bad.
[Untrimmed] For Trusted Modification sources.
[Dumped as trimmed, but untrimmed for hashing] For use if you want to mark something as "dumped as trimmed", but want to put the proper non-trimmed hash.
[Overdump removed] For Trusted Modification sources.
[Modification of file: {size}-{sha256}] For Trusted Modification sources. size = Size in bytes, sha256 = sha256 of file, all caps
[Internal checksum mismatch] Internal checksum doesn't match data.
[Standalone fix] For Satellaview Trusted Modification sources that contain fixed standalone ROMs for games in a Memory Pack.
[Marked as deleted] For satellaview ROMs that were marked as deleted (blanked header)
[Loose files] For sources that just have the filesystem contents instead of a ROM/disc image
[Not redump standard] Used for things in Non-Redump dats that are not redump standard, but only for "[On redump]" archives. Don't put it on everything.
[Redump standard] Used for things in Non-Redump dats that are actually redump standard, just not in redump.
[edcchk v{version} {doesn't} report{s} error(s)] For CD images in non-redump dats. E.g. "[edcchk v1.26 doesn't report error(s)]"
[CD dump in ISO format] For CD dumps that are marked as bad due to just being an ISO dump rather than a full track dump.
[grw0 partition not in factory state] For PlayStation Vita PSVGameSD dumps that have grw0 partitions, and have been played, meaning the partition has been written to since the cart came out of the factory. Use in conjunction with the "HasSave" ROM status.
[mdf format] For disc images in mdf/mds format.
[ROM status set to "other" due to dump origin] Used when dump status is set to "other" due to a non-standard dump origin (which should be set in the dump origin field)
[Media was unused] Physical media unused before it was dumped. Only relevant for media where the software portion is (easily) rewritable like floppy disks.
[Unused save was all FF bytes] The factory-state save was all FF bytes.
[GodMode9 txt file lists no save chip ID] For DS/3DS dumps

Comment 2

Tag Explaination
[Asked dumper for more info] To be used when the dumper hasn't provide pictures, etc, you've asked them for this extra info/data and are waiting.
Demo {part/article} number (from barcode text): {number} The demo "part" (for US)/"article" (for Europe) number thats printed under the barcode on the sticker on some Nintendo DS/3DS demo carts. Keep the spaces.
Demo {part/article} number (from actual barcode): {number} Same as above, but for the number parsed from the actual barcode, e.g. using the "zbarimg" software. Don't add spaces.
[Cart barcode read with barcode reader] Put this if you have scanned the actual barcode bars (using barcode scanner software) for the cart barcode, and they match the numbers written below it. Was formerly "[Cart barcode scanned]". Todo: change instances of this to match the new wording.
[Released by: x] For public releases when the dumper isn't the one who released it
[PCB serial transcribed from physical media] For when the DS/3DS PCB serial is too blurry in the photo, but the dumper transcribed it from the physical media so its still recorded accurately.
[Comment from release: "x"] For public releases (protos etc), where the releaser has put a comment containing credits to contributor(s).
[HTTP Response Header Last-Modified: x] If you just want to put the last-modified date from the http header, and not the whole header.
[HTTP Response Header Last-Modified for file "x": x] Same as above, but specifying the file
[Parameters removed from Link x as they contained sensitive info] For when the URL parameters (?uniqueid=12345 - that sort of thing) have been removed from the Link [number] as they contained sensitive info
[Latest title version as of download appended to cetk filename] For 3DS CDN dat
["file/foldername1" downloaded using the "filename2" program] For digital PC dats where the website provides an installer that downloads data from the web.

File

File note

Tag Explaination
[Passes verification with hactool [version]] For Switch cart dat. To indicate that XCIs pass when running hactool -t xci -y file.xci.