Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I see you made a bug report on WAFR's mod page[www.nexusmods.com] and posted your loadorder there. There were 2 things I noticed:
aMidianBorn_ContentAddon.esp already contains an updated version of aMidianborn_Skyforge_Weapons.esp, making that .esp not only redundant but a conflict. While not directly related to your issue, it will cause instability.
The problem you're describing sounds like something that might happen if LootandDegradation.esp is facing a conflict with another mod (again unlikely with WAFR though). If you can still reproduce the bug on your save with WAFR reinstalled, you might want to check if unchecking this mod instead fixes it too.
WACCF_BashedPatchLvlListFix.esp
I have only run in to few issues that have not been fixed in next version and your issue should not even be there
I have as @Mutenear also used that mod for atleast 6 years now.
Check his/her suggestions, and also make sure you place the LVL list plugin more or less last.
He uses Armor_TrueOrcishWeapons.esp and Armor_TrueWeaponsLvlLists.esp that come with WAFR and made a bashed patch, even though the leveled list file is in the middle of the loadorder that should not matter, and also not related to his issue.
What mods were affecting the Forsworn sword according to xEdit?
I can imagine conflicts between WAFR and ISC since both edit records for weapons, but neither should introduce a bug like you ran into.
Take it or leave it, but if you continue with this loadorder that is clearly not stable, you'll run into more trouble down the road. And while LOOT helps a lot, for a big loadorder such as yours it requires manual conflict resolution in xEdit to merge everything together nicely.