I've noticed that several texture replacers use an ESP instead of being pure replacers. The reason is that by giving the new files new file paths there won't be any chance of overwriting files from other replacers. But it also means no easy way to check for conflicts when using BAIN.
So what do others think of this? Personally I think that as long as the ESP only changes the file paths it is a waste of an ESP slot and I prefer to be able to easily detect conflicts.
You can choose more than one option, that's how generous I am.

I think it is a waste of an ESP slot, and I prefer conflict detection. Not to mention, repacking the BSAs is more troublesome with the folder structure expanded. With application-aided installation, it is not necessary to worry about overriding the original files. The original original files are packed in BSAs and mods are backed up in archives (i.e., BAIN packages and OMODs.)

I wish I could choose both of the last two options.

No it is problematic at times but more often just cumbersome.

As long as the esp from these is active though there won't be a conflict ad the diverted file path is what will be used. But yeah if wanting to see what it is replacing and how it conflcits with other replacers you are right. Then you gotta do research.

I get that some want to make sure not to disturb vanilla content and file paths but like many things a good installer and conflict detector (like ... mmmm BAIN) can handle most of those issues.

Aren't there examples though where the esp does more than divert file paths - like add extra content or also utilize meshes that have their own textures married to them.

I did choose both of the bottom options, haha.

You can. I shoud have made that clear.



Yes, there are some of these too, like a book replacer that edits the Book Warehouse in the Testinghall,

I voted the bottom two. I like to have control! :toughninja:

gothemasticator

I'm not against it, but I'd prefer to use a texture replacer as an omod, or with BAIN.

I voted "As long as it works, I don't care," because I'm just going to tag it with graphics and merge it into my Bashed Patch :shrug:

I prefer pluginless whenever possible, but if for whatever reason it's better to use an esp I don't mind.

I take great care in creating my own merged texture pack.
And while such an esp could be easily merged, it helps me to know when I am overwriting an already present texture by the simple prompt.

I would like to see espless Book Replacer as cool as Book Jackets
I use Shiny Gold (espless) and like it.
I use JQ's Skeleton Key replacer - espless and so witty and cool!
Bomret's Normal Maps + Corepc's Vibrant Textures easily matches QTP3 and is so less demanding FPS-wise.
The more the better I say!

Phaedra released an http://www.tesnexus.com/downloads/file.php?id=29358... the thing is, though, that lots of books share the same graphics, so to be "as cool as Book Jackets," you NEED an .esp. I just merge it into my Bashed Patch, so it doesn't take up a plugin slot.

This is my point exactly. I prefer pluginless but in this case you get something better by using an esp, so I don't mind using it.

I'd prefer an ESP only when its necessary. If you can make it plugin-less then why go through all the work of editing in the CS when you can just make the texture and that's it?

In some cases I know this is not possible though as you may want different objects to use different textures. I think the book jackets mod falls under this category since all the vanilla books share textures.

An ESP only when necessary would be my answer. Otherwise you are just creating more work for yourself, and possibly might end up creating a conflict somewhere.

You could try mine, http://www.tesnexus.com/downloads/file.php?id=27527

I voted yes, because I've installed so many texture replacers for various things since I installed the game several years ago, I don't remember what I installed! As an end user, having an esp would allow me to keep track of things - if I had already installed a texture for an item, but didn't remember that I'd installed a replacer, and then installed another, just deleting the texture would revert back to the vanilla bsa and I wouldn't remember where I found the one I had before!

I chose all four. Just to mess up the results in a friendly pre-April Fools spirit. :laugh:

But honestly, I like non-esp dds-replacers as far as possible. Don't mind if they're in a bsa, though that might make it a bit tricky at first.

If it's possible to avoid, then a replacer shouldn't require an ESP. There are options for those who want to keep track of their replacers, for example using Bash Installer or OBMM's omods.

It's far less important now that Bash has Import Graphics.

Before, it used to matter a lot because changing graphics messed with stats and vice versa.

However, if it is a straight replacer, whether or not it has an ESP you will not be able to see any other graphics from other mods. Not much point in not overwriting files in that case.

What it might do, however, is cause a difference in looks between items changed by the replacer ESP and added items that use vanilla textures. Which can be weird.