0 of 0
About this mod
Simple tool I've created to convert simple patches (Like Animated Ships Patches) form ESP plugin to BOS.ini config file.
- Requirements
- Permissions and credits
- Changelogs
Description
Hi all. In files you will find the script (Inator) I've developed and used for creation my Animated Ships Patches.
It's a simple script that will create a SWAP.ini file for BOS, so you can remove ESP and use just this.
But it's good to keep the ESP somewhere (example in 'Source' folder and in the actual modpage), as it may be needed at some point.
For now it's useful for patches that just change some Position, Rotation and/or Scale of placed objects.
And for patches that Delete or Disable references.
(It will send disabled or deleted refs to Z:-30000, deep underground far from render distance.)
Another feature is check if plugin can be converted to BOS.
Run it script called CanBeConvertedToBOS, it will print if selected ESP can or can not be converted to BOS (and why).
Hi all. In files you will find the script (Inator) I've developed and used for creation my Animated Ships Patches.
It's a simple script that will create a SWAP.ini file for BOS, so you can remove ESP and use just this.
But it's good to keep the ESP somewhere (example in 'Source' folder and in the actual modpage), as it may be needed at some point.
For now it's useful for patches that just change some Position, Rotation and/or Scale of placed objects.
And for patches that Delete or Disable references.
(It will send disabled or deleted refs to Z:-30000, deep underground far from render distance.)
Another feature is check if plugin can be converted to BOS.
Run it script called CanBeConvertedToBOS, it will print if selected ESP can or can not be converted to BOS (and why).
Sometimes plugin can't be, for example if it add new stuff or palce new objects.
Experimental:
Experimental:
In cases ESP can't be converted to BOS 100% my script can split esp to two esp
(You need to select that option on GUI, and know exactly what you are doing)
(You need to select that option on GUI, and know exactly what you are doing)
One ESP will have part that need to stay (new objects , new placed objects etc)
and other will have the part that can be BOS,ified. (So source esp to not be used and .ini BOS file)
I'm sure that a lot of patches can be replaced by just this config files.
(I've checked JK's patches and lot of them can be converted this way)
And I'm hoping they will.
It's definitely not a tool for users, but it's good for even beginners in modding.
In future I will probably add more functions.
I'm sure that a lot of patches can be replaced by just this config files.
(I've checked JK's patches and lot of them can be converted this way)
And I'm hoping they will.
It's definitely not a tool for users, but it's good for even beginners in modding.
In future I will probably add more functions.
Feel free to do with it anything you want and if you have idea how t improve this script, just tell me and you are more then welcome to do it and I will update it here.
Benefits from BOS,ing patches:
- Less ESP to load by game engine
- Less references in game (Reference cap)
- Patch don't count to ESP or ESL limit
- Better compatibility with other mods
-In some cases it can help with large references bug
- Easier priority sorting (not on user end, but on modder end, by .ini name)
Some disadvantages:
- More work from modders end
- Script is not perfect, it will be improved but modder should always review the output
- If modder will not put "source .esp" file somewhere, than it will be hard to make another patch.
But for last two I have ideas how to improve it or fix
(improve script by new functionality and make it more flexible and Another inator, this time it will be BOS to ESP-inator)