Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
At the time (2013/2014) I have had no problems with this mod while using it myself ingame, not even with the latest patch 1.9.32.0.8, and I'm still using it in an altered form (withou replication). This mod uses scripts, that will be baked into saves, even after having uninstalled the mod. To my regret, that's something I wasn't aware off at that time.
Pity I didn't receive any such comments here before.
The Temple of Miraak
The Final Descent
A New Source of Stalhrim
Telvanni Research
Deathbrand
Prophet
Chasing Echoes
...and several other DLC quests.
Quest items are registered in the quests' records, meaning that the quests themselves have been modified.
However, more than just the quest objects have been modified within the quests' records.
It's readily visible using TES5Edit or SSEEdit.
This causes numerous quest events to not trigger, and so most of the quests it touches will be virtually impossible to complete by normal means.
I have even found reports that people with the mod, even after uninstalling it and even if it had been the only mod they had, have had all of the quests it touches be broken, and their save file be essentially ruined.
Using FallrimTools' ReSaver also won't be able to fix it because it's not errant scripts running that causes the issue.
I just figured that I should let everyone be aware.