Thanks for the help. I was looking at the pointer as 8 bytes instead of 4. I guess now it's just to figure out what the other 4 bytes represent.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
DEBUG: file size = 00029184 (168324)
No. of Model = 01
reading model 0...
DEBUG: texnum = 6
tex (matid=6): 'ttl_01'
tex (matid=1): 'ttl_03'
tex (matid=2): 'ttl_04'
tex (matid=0): 'ttl_05'
tex (matid=5): 'ttl_06'
tex (matid=7): 'ttl_07'
DEBUG: palnum = 6
pal (matid=6): 'p1'
pal (matid=1): 'p3'
pal (matid=2): 'p4'
pal (matid=0): 'p5'
pal (matid=5): 'p6'
pal (matid=7): 'z'
DEBUG: matid = 0, texname: ttl_05, palname: p5
DEBUG: matid = 1, texname: ttl_03, palname: p3
DEBUG: matid = 2, texname: ttl_04, palname: p4
DEBUG: matid = 3, texname: , palname:
DEBUG: matid = 4, texname: , palname:
DEBUG: matid = 5, texname: ttl_06, palname: p6
DEBUG: polynum = 8
DEBUG: codeoffset = 0000028c
DEBUG: blockoffset = 000040c8, blocksize = 00024dd4
texnum = 6, palnum = 6
tex 0 'ttl_01 ': offset = 0000425c size = 00010000 [W,H] = [256,256]
tex 1 'ttl_03 ': offset = 0001425c size = 00002000 [W,H] = [32,256]
tex 2 'ttl_04 ': offset = 0001625c size = 00000800 [W,H] = [16,128]
tex 3 'ttl_05 ': offset = 00016a5c size = 00002000 [W,H] = [128,128]
tex 4 'ttl_06 ': offset = 00018a5c size = 00010000 [W,H] = [256,256]
tex 5 'ttl_07 ': offset = 00028a5c size = 00000200 [W,H] = [16,64]
pal 'p1' size = 512
pal 'p3' size = 16
pal 'p4' size = 16
pal 'p5' size = -16
pal 'p6' size = 48
DEBUG: converting pal 'p1', palentry = 256
DEBUG: converting pal 'p3', palentry = 8
DEBUG: converting pal 'p4', palentry = 8
Unknown ID VCL0 is not supported
Are the files decompressed then recompressed? If so, then even if you only change a few bytes per file...the patch size will be very large. Try to 7z the xdelta patch and see what you end up with.
Otherwise, maybe you didn't set the window size large enough in xdelta?
Not if you use xdelta.
I dunno if Cartographer can handle this specific case, but it's actually pretty common that you won't get far with a generic tool since there are just too many possiblities in which pointers can be layed out. You might consider just writing your own little dumper, at least how you describe the system it should be pretty simple in this case.
Not if you use xdelta.
You'll definitely want to work on each file individually. Text pointers generally *should* be local to the file they're in, but of course that's not always the case. If you just work with one file by itself, then you'll at least have a much smaller area to search.