Wrye bash for nv is released.
If i make one, i don't need to make the other?
The forum has been set to read-only mode. For community discussion and questions, head over to our Discord: https://discord.taleoftwowastelands.com
Ok to create a bash patch after i create a merge patch?
-
CVB_Taihou
- Posts: 67
- Joined: Tue Jun 21, 2016 7:27 pm
-
Mystical Panda
- Posts: 750
- Joined: Wed Mar 30, 2016 2:02 pm
Wyre and xEdit are usually
Wyre and xEdit are usually used for different things- at least from what I've read. I'm not sure if that's the way it is now, but Wyre was better at merging 'lists' than xEdit. So both were kinda needed... one to merge leveled lists, and the other to created merged, override patches.
-
RoyBatty
- Gary
- Posts: 7742
- Joined: Sun Apr 27, 2014 10:26 am
- Location: Vault 108
Wrye is an automated patch
Wrye is an automated patch solution where xEdit is a more powerful editing tool.
-
jlf65
- Posts: 1535
- Joined: Wed Aug 10, 2016 9:10 pm
I prefer making merged
I prefer making merged patches in xEdit because no matter how good the algorithm, you're probably going to need to make changes, and xEdit allows you to make those changes.
-
Tacitvrno
- Posts: 20
- Joined: Tue Jun 19, 2018 1:40 pm
I experimented a lot with
I experimented a lot with bashed patches and merged patches during my installation of TTW and look, i'm still a retard when it comes to modding (real modding), i mostly fiddle with x edit, so have this in mind for what I'm about to say.
I noticed that if you are not going to mess with your mods further than a merged patch (as you should), a bashed patch might help you, specially in things like the list of weapons that work with a certain perks (cowboy, comando, etc.). But remember that it will be a double edged sword, if you just use a merged patch, some items might be missing from loot lists, you might not find a weapon mod in-game and stuff like that. On the other side, if you make a bashed patch, you might have the opposite problem, imagine, you kill a raider, and find two versions of the weapon he is using and you might find two types of ammo (like finding both .32 and .22 bullets on the .22 revolver added by project nevada), other weird stuff might happen.
If you don't want to spend too much time in x edit manually patching conflicts, FROM MY EXPERIENCE , make your merged patch, then a bashed patch, and don't forget to have the wild wasteland perk, so you can maybe justify all the weird stuff that will happen xD. In the end just do whatever you want, worst thing that can happen is that you learn something and next time you do better.
I noticed that if you are not going to mess with your mods further than a merged patch (as you should), a bashed patch might help you, specially in things like the list of weapons that work with a certain perks (cowboy, comando, etc.). But remember that it will be a double edged sword, if you just use a merged patch, some items might be missing from loot lists, you might not find a weapon mod in-game and stuff like that. On the other side, if you make a bashed patch, you might have the opposite problem, imagine, you kill a raider, and find two versions of the weapon he is using and you might find two types of ammo (like finding both .32 and .22 bullets on the .22 revolver added by project nevada), other weird stuff might happen.
If you don't want to spend too much time in x edit manually patching conflicts, FROM MY EXPERIENCE , make your merged patch, then a bashed patch, and don't forget to have the wild wasteland perk, so you can maybe justify all the weird stuff that will happen xD. In the end just do whatever you want, worst thing that can happen is that you learn something and next time you do better.