I searched for awhile and couldn't find it... Anyways good job, maybe I need to take a second crack at it tooFound ironfall title id in versionList.dat. Tutorial for patching the update message comming soon.
I searched for awhile and couldn't find it... Anyways good job, maybe I need to take a second crack at it too
It's a bit complicated to find the id, but tutorial will come soon.
Is it separated up into segments? Like all titles with the first part of the ID are under one part and the end part is the only significant piece?
Not really, only in a diffrent order.
For example
Ironfall + DLC
Title ID:
000400000015D800
ID in versionList.dat:
00D8150000000400(20)
Maybe you can see the difference.
Ahh so they reversed it I see... Also they flipped every 2 bytes around
That's called little-endian.Not really, only in a diffrent order.
For example
Ironfall + DLC
Title ID:
000400000015D800
ID in versionList.dat:
00D8150000000400(20)
Maybe you can see the difference.
That's called little-endian.
Almost every number on the 3DS is little-endian. That's a CPU thing.
https://en.wikipedia.org/wiki/Endianness#Little-endianThe byte reversing is little endian? I did know it would display backwards but I'm pretty sure byte reversing isn't little endian, though I may be wrong
Right.... but every two bytes are flipped as well in this file, from what I understand about endianness little endian is simply a flipped around version of big endian.... i.e. 1234 would be 4321 in little endian, right? Maybe I have no clue what I'm talking about but that's the way I always understood ithttps://en.wikipedia.org/wiki/Endianness#Little-endian
Extended NCCH headers values are in little-endian too.
Most numbers on the 3DS are stored little-endian.
I think it would be 3412Right.... but every two bytes are flipped as well in this file, from what I understand about endianness little endian is simply a flipped around version of big endian.... i.e. 1234 would be 4321 in little endian, right? Maybe I have no clue what I'm talking about but that's the way I always understood it
Bytes are reversed. Bytes are 2 hexadecimal digits. So 01 B0 98 04 in big endian is 04 98 B0 01 in little endian.Right.... but every two bytes are flipped as well in this file, from what I understand about endianness little endian is simply a flipped around version of big endian.... i.e. 1234 would be 4321 in little endian, right? Maybe I have no clue what I'm talking about but that's the way I always understood it
Ah alright, so my understanding was just off then, thanks for clearing that upBytes are reversed. Bytes are 2 hexadecimal digits. So 01 B0 98 04 in big endian is 04 98 B0 01 in little endian.
And as I said before, most numbers are little-endian on the 3DS.