O
Omzy
Guest
I sent some relevant info to someone in a PM the other day regarding what it means when images fall into different dump folders. I remember encountering this problem and designing a solution for it (this is why objmap file exists, but no one uses it and I haven't tested if it works):where the tiles are flipped to the opposite sites of the image (top/bottom). I'll have all of the codes if I use all 4 objmap codes for each enemy. I think it has something to do with if the texture is loaded with multiple rows of enemies...
If I provide all of these codes (objmap codes actually), then it seems like most every instance of that enemy works unless they share a hashcode.
-unsupported: size/format is not yet supported (256x256 currently only supported)
Originally I programmed Tonberry to only care about 256x256 size textures, which is the size of the memory image buffer. The hashing algorithm only looks at the left side of this square since the left half (128x256) contains the last image loaded into memory. I later added the getobj() function, which checks the top/bottom left quarters of memory for a single texture since I noticed many objects like save points and many character textures use only a quarter of the memory (128x128), so it searches through hashes in the objmap.csv. I'm not sure that anyone uses/knows about that functionality, but maybe they do (might explain why many character hashes fail). Anyhow, unsupported fall outside of those ranges and really only should occur if the texture is larger than 256x256 (video frames, for example).
-nomatch: not yet hashed, but will be in the future with modder help
In other words, there isn't any hashcode in the csv files that matches the image (hasn't been replaced yet by modders)
-nomatch2: hashed once, failed second round of hashing (shouldn't happen)
When textures are so similar that the second hash fails too
-noreplace: hashed and intended to be replaced but the new texture failed to load or didn't exist
-replaced: successfully replaced
-error: texture not otherwise accounted for (shouldn't happen)
Last bucket category, no images should really fall into it