Rethinking the 3DS (DLC) DAT
- Connie
- Datter
- Posts: 355
- Joined: 20 Jun 2008 12:15
Re: Rethinking the 3DS (DLC) DAT
I agree, but isn't CIA (or 3ds) currently just an 'archive' of this folder structure anyway?
-
- Posts: 210
- Joined: 16 Jul 2010 06:27
Re: Rethinking the 3DS (DLC) DAT
Yes, but in the same way an ISO is a folder structure for whatever they contain; It's basically the packaging around everything.
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
Re: Rethinking the 3DS (DLC) DAT
I'm pretty sure CIA contains more data than 3DS.
-
- Posts: 210
- Joined: 16 Jul 2010 06:27
Re: Rethinking the 3DS (DLC) DAT
I would think so as well. Anyone ever opened a 3DS title that is also on eShop and compared?Hiccup wrote:I'm pretty sure CIA contains more data than 3DS.
And really even if it does or doesn't is sort of beside the point. It's just about capturing the best case of the files for the DAT.
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
-
- Datter
- Posts: 435
- Joined: 14 May 2010 22:14
Re: Rethinking the 3DS (DLC) DAT
3DS contain more data , it has also a update in it and CIA has not.Hiccup wrote:I'm pretty sure CIA contains more data than 3DS.
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
Re: Rethinking the 3DS (DLC) DAT
What do you mean update? Digital titles don't contain updates.
-
- Posts: 210
- Joined: 16 Jul 2010 06:27
Re: Rethinking the 3DS (DLC) DAT
Interesting question. Don't they update the eShop releases to have the patches in them?Hiccup wrote:What do you mean update? Digital titles don't contain updates.
Say you purchased Smash Bros when it first came out (v1) and then you re-bought it today, wouldn't it come pre-patched to the last version (v1.5 or whatever it is)?
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
Re: Rethinking the 3DS (DLC) DAT
I thought jimmsu meant system updates - which only exist in physical titles.
As for of a new version of a title contains the changes that patches made - that is different per-game. But I haven't heard of any digital title doing this, though I suspect at least some the many new versions (aka revisions) of *physical* Smash Bros. contain the changes that downloadable update/s made.
As for of a new version of a title contains the changes that patches made - that is different per-game. But I haven't heard of any digital title doing this, though I suspect at least some the many new versions (aka revisions) of *physical* Smash Bros. contain the changes that downloadable update/s made.
-
- Posts: 356
- Joined: 22 Sep 2012 16:36
Re: Rethinking the 3DS (DLC) DAT
I remember when I downloaded Pokemon Y a couple months after release, it still made me update immediately after (if I recall, 1.2 was the last version of the game on its own, before ORAS compatibility updates).
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
Re: Rethinking the 3DS (DLC) DAT
That has nothing to do with the contents of the ROM. Later versions of the system menu force you (or ask you) to update the title or install a patch ("Update Data") for it.
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
Re: Rethinking the 3DS (DLC) DAT
Question about potential Nintendo CDN dats:
where should the cetk be stored in the datfile?
cetks (common tickets) aren't exclusive to particular title versions, so where should they be stored?
ideas:
-as a separate entry? e.g. Game Name (USA) (cetk)
-duplicate to each entry? (but wouldn't that waste space? although cetks are tiny)
-put them in the lowest version entry? e.g. cetk would go in Game Name (USA) and not Game Name (USA) (Rev 1)
-seperate dat? maybe this theoretical dat could also contain normal tickets dumped from people's consoles?
where should the cetk be stored in the datfile?
cetks (common tickets) aren't exclusive to particular title versions, so where should they be stored?
ideas:
-as a separate entry? e.g. Game Name (USA) (cetk)
-duplicate to each entry? (but wouldn't that waste space? although cetks are tiny)
-put them in the lowest version entry? e.g. cetk would go in Game Name (USA) and not Game Name (USA) (Rev 1)
-seperate dat? maybe this theoretical dat could also contain normal tickets dumped from people's consoles?
-
- Datter
- Posts: 16
- Joined: 20 Aug 2016 21:30
Re: Rethinking the 3DS (DLC) DAT
I am not sure I fully understand how the tickets work (why I haven't tried to do these yet) but if the issue is that cetk is the only redumpable key needed for full decryption then I would say it should be duplicated in every set it works on because otherwise you would need a separate list of which keys go with which sets and it would be harder to know which just don't have keys dumped yet versus having been verified to be duplicate of some other one. They should be very small size. For the sony packages with the same decryption keys (not many examples but some), the raps work the same way in that they are present in each set.
Another question is whether it is worth datting sets where keys are undumped, if that would discourage proper dumping...
Another question is whether it is worth datting sets where keys are undumped, if that would discourage proper dumping...
-
- Datter
- Posts: 435
- Joined: 14 May 2010 22:14
Re: Rethinking the 3DS (DLC) DAT
Hiccup wrote:Question about potential Nintendo CDN dats:
where should the cetk be stored in the datfile?
cetks (common tickets) aren't exclusive to particular title versions, so where should they be stored?
ideas:
-as a separate entry? e.g. Game Name (USA) (cetk)
-duplicate to each entry? (but wouldn't that waste space? although cetks are tiny)
-put them in the lowest version entry? e.g. cetk would go in Game Name (USA) and not Game Name (USA) (Rev 1)
-seperate dat? maybe this theoretical dat could also contain normal tickets dumped from people's consoles?
You have 2 files
tmd and the 00000000 file
And then you need the keys for encrypting en decrypting
And all should be in 1 archive
-
- Datter
- Posts: 244
- Joined: 09 Oct 2015 11:29
Re: Rethinking the 3DS (DLC) DAT
yeah but should cetk be in every revision or just the original one?