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
http://www.uesp.net/wiki/Skyrim:A_Return_To_Your_Roots
...for ways to fix the problem
I don't know what mod manager you are using. Can you see what mods are overwriting USKP?
What many players have not understood that often dirty edits are actually required for mods to work. Mod warnings in LOOT pointing to TES5Edit should be ignored, unless the mod author - or peoples who advices you consider trustworthy - actually recommend that you to clean a certain mod. Those cases would be very rare and it is usually wiser to find replacement for such mods.
None of my own mods is currently cleaned. I know that few mods has unnecessary dirty edits in them, but I don't have any mods that would work with same records. There is no need to clean them.
And there is also no need for you to delete mods giving warnings about dirty edits. LOOT only warns about them, but does not know if they are actually needed. While most mods working with same records would be incompatible with each other in any case, you don't really need to worry about dirty edits in modern mods. :)
I do recommend cleaning master files, because dirty edits there will cause CTDs with modded game. Update.esm is one of these files and is loaded directly after Skyrim.esm in your load order. I understand that not all peoples are comfortable with doing this, but it is actually easy enough. There is no 100% need to do this, but it does help you to avoid certain unexpected CTDs.
Gopher gives good instructions and actually cleans Update.esm in this video - and takes his time while doing so. I recommend that you take time to at least watch the video, to better understand what we are talking about in this forum.
http://youtu.be/fw3g_N1jcZQ
open the console and type
set NN01Count to amount
where amount is the number of crimson nirnroots you have in your inventory
then type
UpdateQuestInstanceGlobal NN01 NN01Count
Sorry for another necro.
It didn't work for me, I also got stuck with this quest. I tried what you suggested, it does update the quest global instance to 30/30, but remove one crimson root and it resets to 0/30. Even tried setstage NN01 20 to change the quest to another object. Putting all the crimson nirnroots in an empty container and taking them out again didn't work ass well. Counter keeps saying 0/30.
UESP.net says this is fixed by unofficial skyrim patch, not in my case...
thank you so much... that worked!