and i want to say, math OFFSET x 16 is fine or not good for that?
The "80" of your example is already aligned to 16 bytes, let's take 1234 instead, "math SIZE x 16" will result in 1248.
As far as I know the current beta is able to support alignment in reimport mode.
Do a test and let me know.
when we using a dictionary name (a list for names to rename CRC to names), those CRCs that are not available in list of names, will not renamed to original crc and will show like this: 00000001.dat, 00000002.dat, 00000000a.dat and so on, but it must be renamed to CRC if name is not available in list, like this :154821484, 42972494, 247442 and so on
It's something I can do it, yes.
It will break compatibility with files extracted in the past (what was 00000000.dat now would be 12345678.dat [hex is necessary]) but I think it's not a bad thing.
and another, problem 2:
names better be like this: 00000001.dat, 00000002.dat, 00000003.dat, 00000004.dat, 00000005.dat, 00000006.dat, 00000007.dat, 00000008.dat, 00000009.dat, 00000010.dat, 00000011.dat, 00000012.dat, 00000013.dat, 00000014.dat and so on, i mean dont use hex numbers as numbers
You can obtain decimal names with the command-line option -N, the option works in the quickbmsver command too.
better do something to add an option for edit config files, and export and import values to xml or a file and edit values, like xml files for coordination
That's complex, really complex. There are many types of configuration files with an unknown number of fields.