Worth mentioning that instead of just dumping all the textures you can use GE debugger(Windows only I guess p) to export texture you're viewing, doing so will not give you a hash/filename reducing the usefulness for replacement, however for adventurous people, my personal builds have an additional option in GE debugger to also generate that filename/hash. There's also hashranges which can be very powerful tool in some cases, unfortunately most of the time can't be used.

Those special options are more workarounds to potential problems than anything else through as the main tools of texture replacement are hashes which you can read about in here including syntax explained with examples. ReduceHash - hashes only half of the texture, this is dangerous for many games, however there's an unfortunate, but somewhat common situation where textures include other/random data within them and can't be replaced by full hash, in some cases this can make texture replacement usable, but again, it should never be casually used, just as the previous option it also requires safer hash, IgnoreAddress - does what it says, ignores address saving textures only based on clut hash and texture hash since addresses are in some games changing rapidly generating thousands of textures, it also requires safer hash option so basically any except 'quick' Video - will allow dumping textures from the video, will not work for all videos through

Psp texture brocade