Can't decide between plugin formats.

[ibrahimguler]

Hello everyone.

I'm currently working on a mod that alters vanilla values and adds some new ones. In particular, I'm working on a food and drink overhaul mod for New Vegas (Tale of Two Wastelands). Almost every item on the vanilla list is modified, one way or another. Added some new loot and new recipes. Long story short, it's a vanilla extention overhaul and not creating something new from scratch. I'm having an issue with file extentions though. To me, most logical way to install this mod would be just after the main .esm files, including "TaleOfTwoWastelands.esm" and "YUPTTW.esm" etc. But that requires setting this mod as either a .esm or an .esl. I'm guessing .esl is not needed for a mod that only changes some vanilla values and doesn't touch to NPCs or quests. .esl would make the most sense since I want other mods that having their own food changes to overwrite this one, since mine is a vanilla extention. Is there any problems to set up my mod in this way (as an .esp with .esm flag)? Is there anything I should be aware of? Or, regardles of the use case of this mod, should I set it up as an .esp file?

[showler]

I don't believe New Vegas supports light plugins, so ESL or ESP-FE are not options.  But I think that was a typo anyway.

I wouldn't make it an ESM in any way unless you intend for other mods to use it as a master.

[ibrahimguler]

Hello showler. Thanks for the answer. I was mainly asking about the way xEdit handles the new plugins. There's the usual .esp and .esm of course. And there's another .esp in between with .esm flag. I thought it would be beneficial for such a mod as mine since I want my mod to be a new base for others changing those values. I decided to move forward with .esp anway. I don't think any other mod going to use my mod as a master.