General dat notes: Difference between revisions

From No-Intro ~ Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
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.
* 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>
** For consistency, list Company names used in DoM for this purpose here:
*** Activision
** 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 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.
* 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>.
[[Category:Datting guides]]
* 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 8-character string. The same id should be used across multiple dumps by the same anonymous person.
* 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.
* 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
* 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
Line 17: Line 9:
==Tags==
==Tags==
Documentation for common "tags" that are used in comment fields.
Documentation for common "tags" that are used in comment fields.
===Sticky Note===
{| class="wikitable"
!Tag
!Explaination
|-
|!pc-platform-[platform]
|For IBM PC digital. Values: windows, mac, linux. e.g. !pc-platform-windows
|}
===Comment 1===
===Comment 1===
{| class="wikitable"
{| class="wikitable"
Line 25: Line 26:
|For Trusted Modification sources. x = CRC32 of file that was modified.
|For Trusted Modification sources. x = CRC32 of file that was modified.
|-
|-
|[Modification type: x]
|[Untrimmed]
|For Trusted Modification sources. values: trimmed
|For Trusted Modification sources.
|-
|-
|[Dev cart]
|[Dev cart]
|Used when dump status is set to "other" to prevent dev cart from counting towards verified status.
|Used when dump status is set to "other" to prevent dev cart from counting towards verified status.
|}
|}
[[Category:Datting guides]]

Revision as of 13:37, 20 December 2020

  • 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
  • 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.

Tags

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

Sticky Note

Tag Explaination
!pc-platform-[platform] For IBM PC digital. Values: windows, mac, linux. e.g. !pc-platform-windows

Comment 1

Tag Explaination
[Modification of file with CRC32: x] For Trusted Modification sources. x = CRC32 of file that was modified.
[Untrimmed] For Trusted Modification sources.
[Dev cart] Used when dump status is set to "other" to prevent dev cart from counting towards verified status.