cabarius / ToyBox

Toy Box is a cute and playful mod with 500+ cheats, tweaks and quality of life improvements for Pathfinder: WoTR. It was created in the spirit of Bag of Tricks & Cheat Menu but with a little different focus . It of a powerful and convenient way to edit the party composition, stats, search and add Feats, Features, Items, etc. to party members.
MIT License
166 stars 106 forks source link

ToyBox 1.5.24 crashes Unity Mod Manager config window #1111

Closed h-joerg closed 2 months ago

h-joerg commented 3 months ago

Description of the bug

When starting the game, my Player.log file pops up. The game proceeds to load as normally, but the Unity Mod Manager config window is not present in the game's main menu, nor can you toggle it with Ctrl+F10. It shows up as expected as long as ToyBox is deactivated.

Steps To Reproduce

  1. Install ToyBox 1.5.24
  2. Start the game
  3. At the main menu, UMM config window is not present nor can it be toggled on

Expected Behavior

UMM config window should be present once the game enters game menu

Log Files

GameLogFullPrev.txt GameLogPrev.txt Player.log Player-prev.log GameLog.txt GameLogFull.txt

Save File

No response

Screenshots

No response

Settings

No response

Toybox Version

1.5.24

Operating System

Windows 10

What game are you using Toybox on?

Pathfinder Wrath of the Righteous

Game Version

2.3.2c

Anything else?

No response

xADDBx commented 3 months ago

Have you tried verifying your game files? If that doesn't work, maybe try reinstalling UMM. The error in your log is... weird.

CasDragon commented 3 months ago

For reference by what ADDB calls "weird", the log is saying that UMM itself is crashing (due to an invalid logger?). Obviously, that's not normal, so it's possible that either one of the UMM files is corrupted, or one of your game files is corrupted

h-joerg commented 3 months ago

So I've tried the following

GameLogFullPrev.txt GameLogPrev.txt Player.log Player-prev.log GameLog.txt GameLogFull.txt

EDIT: Another thing, this was not an issue when using version 1.5.13. But that one suddenly became incompatible with TTT so I had to update. Well, not both mods have no issues loading at once, but I can't configure them at all in-game.

xADDBx commented 2 months ago

I can't reproduce. Neither can other modders. None of us can even guess what could be the reason without attaching a Debugger.

Are you by chance blocking web requests? That shouldn't cause an issue normally, but I really can't say what's the problem here.

xADDBx commented 2 months ago

Somebody created a changed UnityModManager.dll. Replace your existing one (located in Steam\steamapps\common\Pathfinder Second Adventure\Wrath_Data\Managed\UnityModManager). Then try again. Please do share your logs again too. This files should have better logging.

File Link (it's the dl link from Discord, if it for you doesn't work I'll reupload myself)

https://cdn.discordapp.com/attachments/791053285657542666/1259503988278165596/UnityModManager.dll?ex=668bebff&is=668a9a7f&hm=9e5da4ebf50de510abc0a9f51f152f53fad18e818586561b7c5f3bdeba405609&

h-joerg commented 2 months ago

Here are the logs as requested with the new .dll, from a "crashed" launch GameLogFull.txt GameLogFullPrev.txt GameLogPrev.txt Player.log Player-prev.log GameLog.txt

I've also been trying whatever I can to get it to work and I finally managed it - if I use the Assembly install method for UMM instead of DoorstopProxy, the game starts normally as expected. Crashes however still occur if I use DoorstopProxy for any ToyBox version past 1.5.13.

aaronmaslen commented 2 months ago

If you're using Assembly install method, you should install WrathPatches and use it to upgrade Harmony or you will be stuck on an old version that may break certain mods.

xADDBx commented 2 months ago

I'm glad it worked out for you; still at this point nobody on our side could reproduce; the thoughts we did have for debugging (i.e. custom assemblies) didn't work out.

Since there's nothing more we can do for now I'll close until any new development regarding this occurs.

xADDBx commented 2 weeks ago

I think this will be fixed in 1.6.7 when it releases. We tracked down the source (though it doesn't make much sense), and did some changes that seems to have resolved the problem...