I deleted it a a few minutes before you

[hallow bobcat]

ok, no problem. Discussing this with a colleague now. After you removed the mod folder, did the warning spamming still happen?

[lucid nexus]

Testing right now, sorry I am also working while doing this

Thanks for the support. Just a moment

[hallow bobcat]

No rush

[lucid nexus]

Just to be clear when I did that I deleted the entire Larian folder in appdata, conincidentally it also had the place you asked me to delete inside it

Idk what difference that'll make but I'm opening vortex right now to check

I'll also delete the vortex appdata thing again so it won't try to install any mods that aren't actually there or anything (not sure how vortex works in that regard)

For now no issues, I installed lslib and no errors - I'll install a random collection now to see if that does anything

Oh my god yeah I think it's fixed! @hallow bobcat Thank you so much for the great support!

Right when you posted that I was about to restore the larian folder because i was afraid it was gonna mess up my game haha

2gb into installing a collection and no errors. Safe to say it's all good

Should I do anything else to avoid any errors?

[hallow bobcat]

hmmm

bg3 is a bit weird as Vortex has to rely on lslib in order to read the pak files. It needs to read them so that it can get metadata from them that BG3 needs to know they exist etc

so it is quite fiddly but most of the time it's fine. I've seen your issue before and we are looking at how we can make catching the error better and less 'spammy'

I'm curious what mod that was though as it is an odd filename

and might just not be compatible

Either way, I'm glad it's sorted! This is never an exact science

[lucid nexus]

Thanks haha yeah I'm also not sure regarding the deets but there's at least a clear solution

[hallow bobcat]

Clearing the BG3 Mods folder and removing Vortex's AppData is always going to be a completely fresh start. Have a good day!