Closed GoogleCodeExporter closed 9 years ago
They were in there at some point. I have them in archived item data for
FFXIAH.com. I'm thinking they moved them around.
Original comment by scr...@gmail.com
on 13 Jan 2012 at 11:57
It's been a long time, but I _think_ POLUtils would detect and load item-type
DATs when you select them in the DAT browser.
Starting point would be to look at DAT IDs next to the existing range (note:
DAT ID, not necessarily dat file name).
Looking in ROMFileMappings.xml I see that the English item DATs are IDs 73-77
(77 being the puppet items, previously the last added set; there's also ID 91,
which just contains a single "item", i.e. money). So I suggest looking for the
DAT file that is assigned to ID 78 as the most likely candidate for a new item
data file.
Problem is that I think the current POLUtils no longer had the little dialog
that shows all the ID->file mappings.
But you can find out via FFXI.GetFilePath(78) in code, or by adding a line for
that ID to ROMFileMappings.xml (and maybe check 79 and 80 too). This is
something I can't do anymore (the mapping comes from the FTABLE/VTABLE files,
which requires a proper up-to-date FFXI install).
Original comment by tim.vanholder@gmail.com
on 14 Jan 2012 at 9:11
Hey Tim, Thanks for the response. I went ahead tried the 78-91 and even some
before 73. None of them were string tables for items. Is there a way to hack
POLUtils to scan each DAT for hints of item string tables?
Original comment by scr...@gmail.com
on 15 Jan 2012 at 10:41
I commented out the all the known Filetypes except Itemdata and then did a
full-scan with mass-extractor. I didn't find any new Item files :( Oh well,
this isn't a major issue.
Original comment by scr...@gmail.com
on 16 Jan 2012 at 12:05
It appears that this issue has the patch I'm looking for.
http://code.google.com/p/polutils/issues/detail?id=7
I forgot Doomer sent me a separate file for those items awhile back.
Original comment by scr...@gmail.com
on 16 Jan 2012 at 12:53
Resolved in 0.9.9.2
Original comment by radecfor...@gmail.com
on 3 Jul 2012 at 8:11
Original issue reported on code.google.com by
scr...@gmail.com
on 13 Jan 2012 at 11:47