<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>2018_NSW.nfo</title>
<style type="text/css">
@font-face {
font-family: nfo;
font-style: normal;
font-weight: normal;
src: url(nfo.eot);
}
.nfo {
padding: 12px;
font-family: nfo, courier new;
font-size: 11px;
line-height: 1em;
}
</style>
</head>
<body>
<pre class="nfo"> ______ _______ ______ _______ _____ _____ _______
_/ _ )__ _/ _ /_\ \ _/ _ /_ _/ \_ / _/_ _/ _ /__
\ _/ \\ -\___\ \\ \\ -\___\ \\ _\ \--\___ \\ -\___\ \
/ \ . _/ . . _/ . \ . :/ . _/ _\
./_____:\_____/____________\ \________/____:\_____\_______/___________\
/______/
_______
_______ _____ _____\ \ __________ _____
/ __ )__\ \\ \\ \ / _ / / _/____ 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 ┬│
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
</pre>
</body>
</html>