Utumno

Yep - although when dust settles I still find the idea appealing of having a BOSS like button that calls LOOT functions - without launching LOOT's UI - dunno if...

So marking as won't fix rather than rejecting - also interesting ideas by @lojack5 above - binning most of our tools will take some really ugly code with it apart...

> I'll probably submit a PR updating it for Bash post-release That would be grand

Ok I now had to look more carefully into the records classes. The problem to me is that it uses the `__set/getattr__` pattern. I am not a big fan of...

I had an [illumination](https://github.com/wrye-bash/wrye-bash/compare/e6b40c3105e63f82e521bad34cb157f1890f6e27...utumno-312-patchers-broken), probably due to seeing your refactoring attack on the records @Infernio - it's fairly broken but I think it's in the right way - will clean...

I pushed some rename commits on nightly (along with @GandaG build changes and couple fixups) that are prerequisites for utumno-312-patchers-broken - this one is not so broken but we have...

allowUnloaded permits to "scan" mods that are not active/merged but yes I don't know either what this scanning does

Dug up a bit on allowUnloaded - I landed on its introduction of : 5ed48d6882990fc6a1c9fdc1ff51073a01a53d5b It is listed as a change in Pbash (??) This swicthed default of allowUnloaded to...

@Arthmoor are those mods meant to have some special bash tags? What are the CBash issues?

ooops good catch will fix On Wed, Dec 18, 2019, 20:44 Infernio wrote: > @Utumno On nightly right now, I get this when > hovering over patchers in the patch...