RPGHQ

SniperChris wrote: ↑ September 30th, 2023, 20:21

The mod has been updated - it hopefully should address the CTDs from those experiencing them. Still no solution for His Majesty because LSLib needs Version 7 support.

Just accept that His Majesty is a floating, talking cat head.

It's the Forgotten Realms!

1. LSF files in the same file path after SharedDev, Shared, GustavDev, Gustav all merge together into one before the game is loaded. E.g.
   • Public / SharedDev /Content/[PAK]Character_visual/merged.lsf
   • Public / Shared /Content/[PAK]Character_visual merged.lsf
   • Public / GustavDev /Content/ [PAK]Character_visual /merged.lsf
   • Public / Gustav /Content/[PAK]Character_visual /merged.lsf
   • Public / yourmodname /Content/[PAK]Character_visual /merged.lsf.
2. Renaming your merged.lsf to random.lsf still works.
3. Multiple .lsf files can be dropped in the same Public/yourmodname/ folder and have the same effect as dropping Gustav/../merged.lsf and GustavDev /../merged.lsf separately.
4. Your mod’s LSF file does NOT need to contain everything from the original file if you use this file convention:
   • Public/Yourmodname/Content/[PAK]Character_visual /renamed.lsf
   This way you can avoid issues like headless cats! being changed in a new patch. And your mod size will be tiny because your .LSF file will only contain the code for the character you changed only. E.g. I have only included Wyll’s variables so instead of a 100000+ lines, I have 2500.
   
5. Note: EVERYTHING between a <node=”Resource”> and </node> has to be included otherwise if you change eye colour in the Resource and leave out the rest. You’ll just have floating eyes.
6. It's best to use the LSV from the latest PatchXHotfixY.pak file instead of the one from Gustav.pak or Shared.pak when you first build your mod.
7. Finally, you can pack your mod into a handy little zip file using bg3-modders-multitool, and we can easily import stuff into BG3 manager. This way we can decide which mod gets priority if two mods have some clashing character Resources.

orinEsque wrote: ↑ October 17th, 2023, 19:07

SniperChris wrote: ↑ September 30th, 2023, 20:21

The mod has been updated - it hopefully should address the CTDs from those experiencing them. Still no solution for His Majesty because LSLib needs Version 7 support.

Just accept that His Majesty is a floating, talking cat head.

It's the Forgotten Realms!

Hi, I love this mod. This and white wyll mod just got me into modding. I’ve experimented with a few things in the past week and I thought my learning may help here. Especially if you want to prevent issues like headless cats and make a mod thats easy to manage with more and more patches incoming. For example if Larian, adds new characters your merged.lsf override will currently break them.

1. LSF files in the same file path after SharedDev, Shared, GustavDev, Gustav all merge together into one before the game is loaded. E.g.
   • Public / SharedDev /Content/[PAK]Character_visual/merged.lsf
   • Public / Shared /Content/[PAK]Character_visual merged.lsf
   • Public / GustavDev /Content/ [PAK]Character_visual /merged.lsf
   • Public / Gustav /Content/[PAK]Character_visual /merged.lsf
   • Public / yourmodname /Content/[PAK]Character_visual /merged.lsf.
   All the LSF files from above get merged into one big xml file. With yourmodname/merged.lsf getting priority.
2. Renaming your merged.lsf to random.lsf still works.
3. Multiple .lsf files can be dropped in the same Public/yourmodname/ folder and have the same effect as dropping Gustav/../merged.lsf and GustavDev /../merged.lsf separately. E.g.
   
4. Your mod’s LSF file does NOT need to contain everything from the original file if you use this file convention:
   • Public/Yourmodname/Content/[PAK]Character_visual /renamed.lsf
   This way you can avoid issues like headless cats! being changed in a new patch. And your mod size will be tiny because your .LSF file will only contain the code for the character you changed only. E.g. I have only included Wyll’s variables so instead of a 100000+ lines, I have 2500.
   
5. Note: EVERYTHING between a <node=”Resource”> and </node> has to be included otherwise if you change eye colour in the Resource and leave out the rest. You’ll just have floating eyes.
6. It's best to use the LSV from the latest PatchXHotfixY.pak file instead of the one from Gustav.pak or Shared.pak when you first build your mod.
7. Finally, you can pack your mod into a handy little zip file using bg3-modders-multitool, and we can easily import stuff into BG3 manager. This way we can decide which mod gets priority if two mods have some clashing character Resources.

I’m making a little R tool that lets you quickly find a character from all four [PAK]Character_visual /merged.lsf in one go using the latest patch and export the file. I’ll post a noob friendly non command line version once it’s done.

@rusty_shackleford Do we have a modding tutorial section? I'd like to leave this there for reference.

SniperChris wrote: ↑ October 18th, 2023, 20:10

orinEsque wrote: ↑ October 17th, 2023, 19:07

SniperChris wrote: ↑ September 30th, 2023, 20:21

The mod has been updated - it hopefully should address the CTDs from those experiencing them. Still no solution for His Majesty because LSLib needs Version 7 support.

Just accept that His Majesty is a floating, talking cat head.

It's the Forgotten Realms!

Hi, I love this mod. This and white wyll mod just got me into modding. I’ve experimented with a few things in the past week and I thought my learning may help here. Especially if you want to prevent issues like headless cats and make a mod thats easy to manage with more and more patches incoming. For example if Larian, adds new characters your merged.lsf override will currently break them.

1. LSF files in the same file path after SharedDev, Shared, GustavDev, Gustav all merge together into one before the game is loaded. E.g.
   • Public / SharedDev /Content/[PAK]Character_visual/merged.lsf
   • Public / Shared /Content/[PAK]Character_visual merged.lsf
   • Public / GustavDev /Content/ [PAK]Character_visual /merged.lsf
   • Public / Gustav /Content/[PAK]Character_visual /merged.lsf
   • Public / yourmodname /Content/[PAK]Character_visual /merged.lsf.
   All the LSF files from above get merged into one big xml file. With yourmodname/merged.lsf getting priority.
2. Renaming your merged.lsf to random.lsf still works.
3. Multiple .lsf files can be dropped in the same Public/yourmodname/ folder and have the same effect as dropping Gustav/../merged.lsf and GustavDev /../merged.lsf separately. E.g.
   
4. Your mod’s LSF file does NOT need to contain everything from the original file if you use this file convention:
   • Public/Yourmodname/Content/[PAK]Character_visual /renamed.lsf
   This way you can avoid issues like headless cats! being changed in a new patch. And your mod size will be tiny because your .LSF file will only contain the code for the character you changed only. E.g. I have only included Wyll’s variables so instead of a 100000+ lines, I have 2500.
   
5. Note: EVERYTHING between a <node=”Resource”> and </node> has to be included otherwise if you change eye colour in the Resource and leave out the rest. You’ll just have floating eyes.
6. It's best to use the LSV from the latest PatchXHotfixY.pak file instead of the one from Gustav.pak or Shared.pak when you first build your mod.
7. Finally, you can pack your mod into a handy little zip file using bg3-modders-multitool, and we can easily import stuff into BG3 manager. This way we can decide which mod gets priority if two mods have some clashing character Resources.

I’m making a little R tool that lets you quickly find a character from all four [PAK]Character_visual /merged.lsf in one go using the latest patch and export the file. I’ll post a noob friendly non command line version once it’s done.

@rusty_shackleford Do we have a modding tutorial section? I'd like to leave this there for reference.

This is awesome! Thank you so much!

Rand wrote: ↑ October 18th, 2023, 23:20

SniperChris wrote: ↑ October 18th, 2023, 20:10

orinEsque wrote: ↑ October 17th, 2023, 19:07

Hi, I love this mod. This and white wyll mod just got me into modding. I’ve experimented with a few things in the past week and I thought my learning may help here. Especially if you want to prevent issues like headless cats and make a mod thats easy to manage with more and more patches incoming. For example if Larian, adds new characters your merged.lsf override will currently break them.

1. LSF files in the same file path after SharedDev, Shared, GustavDev, Gustav all merge together into one before the game is loaded. E.g.
   • Public / SharedDev /Content/[PAK]Character_visual/merged.lsf
   • Public / Shared /Content/[PAK]Character_visual merged.lsf
   • Public / GustavDev /Content/ [PAK]Character_visual /merged.lsf
   • Public / Gustav /Content/[PAK]Character_visual /merged.lsf
   • Public / yourmodname /Content/[PAK]Character_visual /merged.lsf.
   All the LSF files from above get merged into one big xml file. With yourmodname/merged.lsf getting priority.
2. Renaming your merged.lsf to random.lsf still works.
3. Multiple .lsf files can be dropped in the same Public/yourmodname/ folder and have the same effect as dropping Gustav/../merged.lsf and GustavDev /../merged.lsf separately. E.g.
   
4. Your mod’s LSF file does NOT need to contain everything from the original file if you use this file convention:
   • Public/Yourmodname/Content/[PAK]Character_visual /renamed.lsf
   This way you can avoid issues like headless cats! being changed in a new patch. And your mod size will be tiny because your .LSF file will only contain the code for the character you changed only. E.g. I have only included Wyll’s variables so instead of a 100000+ lines, I have 2500.
   
5. Note: EVERYTHING between a <node=”Resource”> and </node> has to be included otherwise if you change eye colour in the Resource and leave out the rest. You’ll just have floating eyes.
6. It's best to use the LSV from the latest PatchXHotfixY.pak file instead of the one from Gustav.pak or Shared.pak when you first build your mod.
7. Finally, you can pack your mod into a handy little zip file using bg3-modders-multitool, and we can easily import stuff into BG3 manager. This way we can decide which mod gets priority if two mods have some clashing character Resources.

I’m making a little R tool that lets you quickly find a character from all four [PAK]Character_visual /merged.lsf in one go using the latest patch and export the file. I’ll post a noob friendly non command line version once it’s done.

@rusty_shackleford Do we have a modding tutorial section? I'd like to leave this there for reference.

This is awesome! Thank you so much!

I assume you'll be updating your mod to this method in the near future?

SniperChris wrote: ↑ March 4th, 2024, 19:30

fkirenicus wrote: ↑ March 1st, 2024, 08:40

Yep, had to remove the overwriting version altogether - which basically meant reinstalling. All good now, except I am left with extremely nasty cats again. Ah well. Hopefully someone that identifies as a cat cries out in outrage of cats in this game being so ugly, and Larian developers rushing to fix the problem lest they be accused of cat-transphobia or some such... ;-)

I just pretend it’s a magic cat.

orinEsque wrote: ↑ March 5th, 2024, 00:49

I made a packing mods for dummies:
viewtopic.php?t=1617-bg3-modding-bg3-ge ... ted#p58094

orinEsque wrote: ↑ March 5th, 2024, 00:49

I made a packing mods for dummies:
viewtopic.php?t=1617-bg3-modding-bg3-ge ... ted#p58094

Please update your mods and pack them properly.

loregamer wrote: ↑ March 10th, 2024, 08:35

orinEsque wrote: ↑ March 5th, 2024, 00:49

I made a packing mods for dummies:
viewtopic.php?t=1617-bg3-modding-bg3-ge ... ted#p58094

Please update your mods and pack them properly.

I gotta concur with Orin. @SniperChris please save yourself some pain and turn this mod into a pak file, brother. It'll pretty much future-proof the mod forever and it's easier to update as you only need the NPCs that you're updating in your lsx file.

Faceless_Sentinel wrote: ↑ March 10th, 2024, 09:07

No, @loregamer not you, you can't be so stupid to not see this in the description: