ddThe thing there is that I would need to see those tickets. Basically I have to support 2 offsets for the keygeneration on tickets since some programs dumped it incorrectly before. Some dumps deviating from the standards format of tickets doesn't help there I guess but as I said I would need to see those tickets. Are you using the last version? I added something before to be able to support both offsets and some nxdumptool dumps that deviated from the standard dump format.
Basically I would need to see the ticket myself if someone made more changes on it because I don't have access to any dump that doesn't have the standard scene format.
Other way would be to ignore the ticket completely and trust the key is encrypted with the same masterkey as the nca headers which should be true. Alternatively I could make it pass a key verification check and force standardize the ticket to avoid issues.
One issue here is that I don't have time lately but I should at least release something this weekend since I added the RSV for 9.2.0 in the beta and well I also added the ability to show info for xc0, ns0 and 00 splitter files in the interface though is still missing the verification stuff. I'll probably add an option to ignore the ticket keygeneration check.
I ve re dump the games again and come to the conclusion that they won't dump correct and file corruption
But running file verify each file for the new dlc, and they all check out except it couldn't verify the ticket even tho I could create a custom xci with them. So u may need to update them
if you want to check them here are the dlc in question
Code:
Xenoblade Chronicles 2 v0 (0100E95004039006) (DLC)
Xenoblade Chronicles 2 v131072 (0100E95004039001) (DLC)
Xenoblade Chronicles 2 v196608 (0100E95004039004) (DLC)
Xenoblade Chronicles 2 v327680 (0100E95004039002) (DLC)
Xenoblade Chronicles 2 v327680 (0100E95004039003) (DLC)
Xenoblade Chronicles 2 v720896 (0100E95004039005) (DLC)