@ danemanuelk
Thank you for your kind words 
I'm in the middle of trying to get a (working) mega-mod install, and frankly haven't been having any luck. Many mods have been so modified to work with EE that they won't even install on BG anymore, and the ones that do won't work with other (original) mods. I'm afraid to offer you any advise at this time, but I can tell you the following.
WeiDu v249 seems to be incompatible with the original game. I'm not sure of this yet, but Leonardo himself commented on it in the PDF (specifically about using 249 when you'd already installed infinity animations ... you can't use generalized biffing). Seems to be an issue with (non English or Latin) codepages.
I'm getting closer to a working game, but still have issues. For one thing, downgrading to WeiDu v246 solves most of the errors I was getting with setup gui. You'll need to downgrade Shadows over Soubar to version 1.15 (the link to 1.16 is currently broken). Sadly, the new version (2.1.3) appears to be incompatible with the original game. Mainly, the info it writes to setup-gui.tp2. Weidu has a heart attack about it (undefined string references)
Moving to WeiDu 246 seems to solve many problems, but I still have yet to get a working mega-mod install.
On the list for the next install:
1) problems with BGT (in former installs (with 249)) BGT would not install without either TDD or SOS installed prior. Apparently the new version doesn't create it's own version of setup-gui.tp2 and can't install without one. Have been over the readme, but haven't seen any dependency listing. Not sure if that was a (249) issue or not. Will test tomorrow. Have already warned you of the music problem with it as well.
2) ToBEx-afterlife The (countless) issues with CTD ... I'm just not sure. Certainly didn't have them in the original game. I don't think afterlife would have anything to do with it, but it does patch bgmain.exe to be more like EE. Have decided to run a (test) install tomorrow without it. Afterlife has the potential to be the bane of Skellytz existence anyways, as it doesn't issue component listings (so the user has no idea what (fixes) it's installed).
Leonardo was having similar problems with TobEx ... namely other mods trying to change how things were working in game (mod space vs engine level). In Ascensions case, the problem was with the PDF for not warning folks they'd already installed that component. Now they have no idea, so you really can't blame the user for installing those components. If any of the new mods (Infinity Animations, Infinity Sounds, etc) depend on those (mystery) components ... 
That's another thing I've noticed in the PDF ... the only mod that got singled out for potential incompatibility with TobEx was P5Tweaks. Not fair (IMHO), as that was simply the last mod (in the install order) that was changing things. There were many others before. Depending on your install listing, well ... 
The biggest thing I can tell you right now is do NOT trust the PDF when it comes to installation order. Its advice is outdated and will end you up with an unplayable game. I'm afraid you'll have to give me more time to set things right tho. Too many variables at play here
As close as I got to a playable game on my last run, I (stupidly) trusted the PDF when it came time to run Lolfixer. It came AFTER infinity sounds in the PDF, but the readme (for Infinity Sounds) clearly states that's not going to work (and it didn't). One example, but I could give your many others.
@Skellytz
Think I've found another typo for you.
Am testing with the new version of 1PP (which you so graciously posted ... thank you!!!) (v4.2.1), and get the following:
ERROR: Failure("resource [r#asmstff.itm] not found for 'COPY'") -- from (1ppv4: Colourable Quarterstaves) and (1ppv4: Core updates and item patches)
Sorry to be such a PITA 
Edited by TDouglas, 01 April 2025 - 07:48 PM.