Oh! I should list known issues (or issue (singular), really): Material maps that refer to locations that are not inside Runtime will not be affected usually However, if it looks like it's inside Runtime then the script will be fooled (because it doesn't know what's a real Runtime and what's not) and, as a result, may goof up things if you unzip a texture pack to somewhere besides Runtime, for instance, and just use a texture from the unzipped Runtime that's not a real Runtime. If that makes sense. Umm, in other words: "C:Program FilesCuriousLabsRuntimeTexturestextue.jpg" and "C:Progra~1Metacr~1Poser4~1RuntimeTexturestexture.jpg" will be fine and will both become :texture.jpg Which minimises the path, too. As will references to "D:downloadsTexturestexture.jpg" (though it will leave it like this) But if you for some reason have a prop referencing something like: "D:downloadsposerinstallsPropRuntimeTexturestexture.jpg" will get turned into: D::downloads:poserinstalls:Prop:texture.jpg Which is kinda weird. But it's not really common that you reference an install temp directory from an installed prop, texture, or whatever. I only did because I accidentally deleted a texture and pointed it back at the install directory which was kinda bad form anyway