Can anyone explain why the filename of an EDAT prevents decryption? As an example, an official EDAT that has the space character in it, like "hot dog.edat", will crash any Java-based programs, like TA's EDAT Rebuilder, because it pathetically can't handle surrounding the file's path with quotations. make_npdata, being command-line based, has no issue. However, and this what my question is, is why will make_npdata bork if the EDAT is renamed? How is the filename somehow involved with the actual encryption of the EDAT's content? Take "hot dog.edat", and replace the space character with a hyphen, or a number, like hot-dog.edat, or hot0dog.edat, and make_npdata will claim that "NPD hash validation failed". Why would the hash matter of the filename, rather than the content of that file?
Last edited by sorewinner,
