General dat notes: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 16: | Line 16: | ||
==Tags== | ==Tags== | ||
Documentation for common "tags" that are used in comment fields | Documentation for common "tags" that are used in comment fields. | ||
===Comment 1=== | ===Comment 1=== | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 27: | Line 27: | ||
|[Modification type: x] | |[Modification type: x] | ||
|For Trusted Modification sources. values: trimmed | |For Trusted Modification sources. values: trimmed | ||
|- | |||
|[Dev cart] | |||
|Used when dump status is set to "other" to prevent dev cart from counting towards verified status. | |||
|} | |} |
Revision as of 13:29, 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
- Box barcodes should be added on their own line in Comment+ like
Box barcode: X XXXXX XXXXX X<tab>XXXXX
(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. - Publisher/developer serials on carts should be recorded in their own line in Comment+ like
[Company name] serial on [box/cart] [front/back]: XXXXXXXX
- 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
Additional cart front serial
in the Comment+
- For consistency, list Company names used in DoM for this purpose here:
- If the language hasn't been checked, make a discussion called
!langs-not-checked
. The body of the discussion doesn't have to the same. - HTTP response headers should be added in the Comment+, each starting with
!http-response-header-start
and then a newline and ending with a newline and!http-response-header-end
. To specify what file the header is for, use!http-response-header-define: filename
on the line before behind each!http-response-header-start
. - PC game platforms should be added as
!pc-platform-[platform]
each on line on the sticky note (e.g.!pc-platform-windows
). Valid values: windows, mac, linux. - 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.
Comment 1
Tag | Explaination |
---|---|
[Modification of file with CRC32: x] | For Trusted Modification sources. x = CRC32 of file that was modified. |
[Modification type: x] | For Trusted Modification sources. values: trimmed |
[Dev cart] | Used when dump status is set to "other" to prevent dev cart from counting towards verified status. |