Why don't you auto detect the types like other dbc converters.
Quote from: "Chase"Why don't you auto detect the types like other dbc converters.that kind of auto detection nearly always is broken. either crawl dbcmeta in the binary, or require such a crawled definition.
Tried quickly dumping down Item-sparse.db2 on the tool and it converted to .csv fine, however, if I took that same .CSV and dumped it on the tool, then it would error out with this:Info: Open File Item-sparse.csv...Info: Read Mapping...Info: Read Header...Info: Write DB2 Records...Error: Index was outside the bounds of the array.I double-checked map.xml and the format of Item-sparse.db2 was indeed correct (I was using MoP 548 Item-sparse.db2). Item.db2, however, converted without problems between CSV and DB2.
Here ya go:https://mega.nz/#!f9BFnL7A!2A96AHxM5Jhg ... gWAw2d09ng
Quote from: "azeroc"Here ya go:https://mega.nz/#!f9BFnL7A!2A96AHxM5Jhg ... gWAw2d09ngYour Problem is fixed with the new Update 0.0.3
I could be wrong, but I think to convert spell.dbc we also need support for uint64. wowdev is 64+32 for SpellFamilyFlags, trinitycore is flag96 (which is just uint32+uint32+uint32). It's a clean convert with the only change on converting CSV back to DBC being replicating the final spell with a new spell ID, incase you need to test it yourself.