-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ghosted Plugins Sorted after the Bash Patch #164
Comments
@WrinklyNinja Can you look over this whenever you have time. Possibly at the same time you look into issue #162? |
I can't replicate point 3, Bash refreshes on refocus fine for me. However, I can replicate point 4, ghosted plugins are being moved to the bottom. Though I find that they're removed from loadorder.txt entirely. @wrye-bash/active: Anyone know of any Skyrim plugins that I can upload to my repo without crossing some "no redistribution" clause? I just used my own plugins for Oblivion... |
I have some patches where you need the original mod for the meshes and textures. As long as the file on the download tab does not say "Original Mod Not Required" then it should be a plugin only. You have my permission to use those. Also I have full permissions for Val's Crafting Meltdown, Bandit EyePatch, and Bikini Clothes. Weapons of the Third Era gives permission to authors to use it. All the links are on my patches page. |
I have not tried those steps but I don't have any issues with Bash refreshing on refocus either. |
OK, I updated the bundled libloadorder to the new v6.0.0 release, and I'm still getting the ghosted plugins being moved. Adding some debug logging to the Python code reveals that libloadorder is providing the correct load order output, so something must be going wrong after Bash gets those data. |
@Sharlikran: I can no longer replicate this issue in my |
I was testing the dev branch to provide Utumno with a tracelog from the dev branch. Two things happened. All my inactive plugins were automatically ghosted when I don't have the enabled and they were all sorted after the bash patch. @wrye-bash/active I remember at one point Utumno had commented on a fix from wrinklyninja-liblo-6-support. IIRC there was an error. Was that resolved in commit 89d3fb5? |
@Sharlikran: can you please try and reproduce this on my latest HEAD: ee68ccc |
Should relate to #164. self.name = normal -> this would set the name to an absolute path ! in the case: mod is inactive and ghosted -> mod activated by liblo and unghosted (works in liblo 6, didn't before) -> autoghost runs > finds isGhost = True while 'normal' exists > Boom - see pics in #187. Meaning all of a sudden self.name was an absolute path leading to all kind of weirdness as the code expects it to be Yada.espm (relative to Data/ dir) - FileInfo.name uses should be pruned as much as possible. Set ghost now also sets ctime - this way running FileInfos.refresh() two times in a row won't detect a change (it shouldn't in this case) - I hope at least (modInfos refresh is my lovely little garden of bugs for the last few months).
Closing this as I can't reproduce it - see linked commits for the possible fixes - ghosting was a can of worms both in libloadorder and Bash |
Revelant posts: WrinklyNinja felt this could be a possible bug here. Original post with steps to reproduce.
stickman1024's detailed steps to reproduce:
I repeated test case again, took more detailed notes, as in the forum post:
Background:
Test (numbers are actions, sub-points are observations):
The text was updated successfully, but these errors were encountered: