2018_NSW.nfo

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205 ______ _______ ______ _______ _____ _____ _______ _/ _ )__ _/ _ /_\ \ _/ _ /_ _/ \_ / _/_ _/ _ /__ \ _/ \\ -\___\ \\ \\ -\___\ \\ _\ \--\___ \\ -\___\ \ / \ . _/ . . _/ . \ . :/ . _/ _\ ./_____:\_____/____________\ \________/____:\_____\_______/___________\ /______/ _______ _______ _____ _____\ \ __________ _____ / __ )__\ \\ \\ \ / _ / / _/____ NSW Scene Rules 2018 / /_ \ \ \ \\ -\____\---\___ \ [xx August 2018] / \ . \ . . _/ . :/ \ \______:\______\___________\ \___________\___________/. ----------------+ . /_______/ . ³ ³ ³ ³ NSW Release Standards v1.0 2018 ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ ³ ³ 1) Packing: ³ ³ 1.1) Releases must be packed in RAR. SFV and NFO must be included. ³ ³ 1.2) RAR, SFV, NFO and JPG files must have unique filenames. ³ ³ 1.3) Rars must be in multiples of 50.000.000 bytes but no larger than ³ ³ 500.000.000 bytes. ³ ³ 1.4) Rars must be RAR4 or RAR5 using M1 compression (fastest) or better.³ ³ ³ ³ 2) NFO: ³ ³ 2.1) The release must include a .NFO. The file must be a plain-text ³ ³ document and at least include the name of the title. ³ ³ 2.2) NFO must include NCA title IDs. ³ ³ 2.3) In the case of a trainer or other game patch, all compatible ³ ³ title IDs must be included in the NFO. ³ ³ 2.4) The source region must be included in the NFO. ³ ³ 2.5) All game languages are encouraged to be included in NFO. ³ ³ 2.6) A short description of the release is encouraged to be in the NFO. ³ ³ ³ ³ 3) Image format: ³ ³ 3.1) For cartridge dumps, only XCI or NCA format are acceptable. ³ ³ 3.2) For eShop releases, only NSP format releases are acceptable. ³ ³ 3.3) NCA dupes XCI if XCI release came first. ³ ³ An XCI release after a cartridge NCA release is not a dupe. ³ ³ 3.4) NCA files must not be renamed from their original filenames. ³ ³ 3.5) XCI files must have the CERT sector replaced with all FF bytes. ³ ³ 3.6) For a cartridge dump in NCA format, the release must include only ³ ³ the contents of the secure partition. ³ ³ 3.7) A dump of a new cartridge revision must only be released if the ³ ³ secure partition has differences to a previous revision ³ ³ (game updates/DLC/etc included), and only if the changes have not ³ ³ been previously released in some other form. ³ ³ 3.8) For an eShop release, all NCA files downloaded from eShop must be ³ ³ included in the release. They must have the NAX-layer decrypted. ³ ³ 3.9) For an eShop release, the NSP must include a forged ticket. The ³ ³ titlekey in this ticket must be encrypted with the relevant common ³ ³ ES key ("titlekek"). All console identifying information ³ ³ (including signature) must be removed. ³ ³ This ticket must be able to be imported using ES with signature ³ ³ checks patched out! ³ ³ ³ ³ 4) Proof: ³ ³ 4.1) All releases are encouraged to include a proof picture ³ ³ with cartridge and a group tag, for "new" groups which pred less ³ ³ then 50 "working" releases this is mandatory. ³ ³ 4.2) You have 24 hours AFTER NUKE to release a Prooffix. ³ ³ After this 24 hours grace period, any other group is allowed to ³ ³ release a PROPER with scans/photos. ³ ³ 4.3) Proof picture can be scanned and must be in JPEG format. ³ ³ 4.4) Proof picture must not be blurry. Cartridge Code must be clearly ³ ³ visible. ³ ³ 4.5) If the medium or cover/booklet contain anything that may expose ³ ³ your identity, then that part of the image can be blurred or ³ ³ blackened. Additional scans may be added but these DO NOT count ³ ³ as sufficient proof! ³ ³ 4.6) eShop releases will be exempt from proof requirements as they are ³ ³ downloadable. ³ ³ ³ ³ NOTE: We STRONGLY recommend the removal of all Exif data! Uniquely ³ ³ identifying information such as the camera serial number and GPS ³ ³ coordinates can pose a security threat if not removed. ³ ³ Use tools such as jhead, PureJPG, EXIF Cleaner... ³ ³ ³ ³ 5) Update/Patch/Trainer/eShop releases. ³ ³ 5.1) NSP game patches are allowed to be released, for the benefit of ³ ³ reducing / accomodating those with console bans / "superbans". ³ ³ 5.2) eShop releases must provide the titlekey in the NFO. ³ ³ 5.3) If update/patch/trainer is for an iNTERNAL release, ³ ³ update/patch/trainer must also be tagged iNTERNAL. ³ ³ 5.4) Source of update/patch origin must be included in NFO. ³ ³ Can also be tagged in dirname. ³ ³ 5.5) Any custom modifications to an NCA (for example: crack, trainer ³ ³ etc) must be in a custom patch format compatible with popular ³ ³ open-source custom firmware solutions, or an NSP/homebrew NRO that ³ ³ generates such custom patches. ³ ³ 5.6) A trainer for a paid game must be compatible with at least one of ³ ³ the releases of a game. Compatible releases must be included in ³ ³ the NFO. ³ ³ 5.7) An in-app purchase crack can dupe a trainer or vice versa if they ³ ³ provide wholly the same features. ³ ³ For example: if a group releases an in-app purchase crack that ³ ³ allows to get unlimited coins, a later trainer that only has ³ ³ options for increasing coins by a certain amount, and options ³ ³ related to obtaining the benefits of coins, would be a dupe. ³ ³ 5.8) It is allowed to release paid DLC, trainers or in-app purchase ³ ³ cracks for free eShop games. ³ ³ 5.9) The latest compatible game version may be included in the release, ³ ³ if a previous release did not include it. ³ ³ Therefore: it is allowed to release free eShop games, as long as ³ ³ you either provide some paid DLC with it, or put in the work and ³ ³ make a trainer or an in-app purchase crack! ³ ³ In this case, "Incl." must be added to the dirname where ³ ³ appropriate. If the latest compatible game version is a patch NCA, ³ ³ then the directory name of the release including the base game NCA ³ ³ must be included in the NFO. ³ ³ 5.10) An NSP game update that has already been released as part of an ³ ³ updated XCI cart revision must be tagged iNTERNAL. ³ ³ ³ ³ 6) Region, Languages, Tags: ³ ³ 6.1) The dirname should only contain the game name, CNMT version number ³ ³ when non-zero and tags. ³ ³ If a game does not include the English language, this must be ³ ³ specified in the dir name unless the region tag implies that ³ ³ regions native language is the only language in the game ³ ³ eg. game tagged JPN is Japanese only, hence does not need to state ³ ³ the language. ³ ³ 6.2) The version number must be the parsed format, cut down to the last ³ ³ non-zero non-dot character. Therefore: if CNMT version is ³ ³ v65536 (0.1.0.0), version number in dirname should be v0.1 ³ ³ 6.3) For non English releases (JAPANESE/KOREAN/etc.) the directory ³ ³ name MUST have a region tag (JPN/KOR/MULTI...) ³ ³ 6.4) The source region should be included in the NFO. ³ ³ 6.5) If a game is re-released for having additional foreign languages, ³ ³ the release must be tagged as MULTI and the NFO must specify ³ ³ which additional languages are included. ³ ³ 6.6) A cartridge dump as NCA must be tagged as NCA. ³ ³ 6.7) If the release is (or includes) an in-app purchase crack then the ³ ³ dirname must include the IAPCrack tag (also see rule 5.9). ³ ³ 6.8) If the release is (or includes) a trainer then the dirname must ³ ³ include the PlusX.Trainer tag where X is the number of options ³ ³ that the trainer provides (also see rule 5.9). ³ ³ 6.9) If the release is an NSP game update then the dirname must include ³ ³ the Update tag. This tag must NOT be included if the release is an ³ ³ XCI/NCA cart revision! ³ ³ ³ ³ 7) Other NFO information: ³ ³ 7.1) If the version number in-game is different to the CNMT version ³ ³ number, then the in-game version number can be included in the NFO ³ ³ 7.2) If the release is an XCI/NCA cart revision, the revision number of ³ ³ the cartridge can be included in the NFO. ³ ³ 7.3) If the game is online-only, the NFO must include this information. ³ ³ 7.4) If the release is a crack or trainer compatible with more than one ³ ³ version/update of a game, the highest compatible version number ³ ³ must be included in the dirname, and other compatible versions ³ ³ listed in the NFO. ³ ³ 7.5) If the release uses REPACK, PROPER or iNTERNAL tags, then the ³ ³ reason for using these tags must be explained in the NFO. ³ ³ ³ ³ 8) Dupes, Nukes, REPACK, PROPER, iNTERNAL: ³ ³ 8.1) You cannot release a game if another group has already released ³ ³ it. This is a dupe and will be nuked accordingly. ³ ³ 8.2) If a releases is flawed for any reason, for example if the game ³ ³ crashes on level 2. Then you can release a PROPER that fixes the ³ ³ issue. If you are fixing your own release, then use the REPACK tag ³ ³ instead of the PROPER tag. ³ ³ 8.3) If the release has a packing issue, such as it will not extract, ³ ³ a rar does not match the crc in the SFV or it pre'd with missing ³ ³ files (RAR/NFO/SFV) then it will be nuked and can be REPACK'ed or ³ ³ PROPER'ed. ³ ³ 8.4) If a dirname is mislabeld, The release will be nuked. No other ³ ³ group can PROPER in this instance, it is expected that the release ³ ³ will be fixed with a DiRFiX from the original group. ³ ³ 8.4) If you would like to release a DUPE for whatever reason then you ³ ³ must use the iNTERNAL tag. iNTERNAL is always shilded from Nuke. ³ ³ ³ ³ 9) FiXES: ³ ³ 9.1) The only allowed fixes are DiRFiX and PROOFFiX. ³ ³ 9.2) A DiRFiX must contain an NFO and the NFO must state the dirname of ³ ³ release that is being fixed. ³ ³ 9.3) A PROOFFiX must follow the PROOF requirments laid out in 4.2, 4.3 ³ ³ and 4.4. It must also contain an NFO and the NFO must state the ³ ³ dirname of the release being fixed. ³ ³ 9.4) If a release cannot be fixed with DiRFiX or PROOFFiX then you must ³ ³ REPACK the release. ³ ³ 9.5) You cannot DiRFiX a release to iNTERNAL to avoid a Nuke for Dupe. ³ ³ 9.6) DiRFiX to iNTERNAL is permitted for technical reasons, but never ³ ³ to shield from a Nuke for Dupe. ³ ³ ³ ³ 10) Only these characters are allowed in dirname and filenames: ³ ³ ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789.-_ ³ ³ ³ ³ 11) Suggested directory formats ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.NCA.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.MULTI.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.IAPCrack.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.Plus3.Trainer.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.v0.1.Update.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.MULTI5.v0.1.Update_NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.v0.1.IAPCrack.NSW-GROUP ³ ³ Game.Name.<PROPER/READ.NFO/REPACK>.Incl.IAPCrack.NSW-GROUP ³ ³ ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ Signed ³ ³ ³ ³ ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´ ³ Compliance with this document is mandatory as of 2018-xx-xx 00:00:01 UTC ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ