Skip to content

BaseLib loads but appears not to complete its later patch/modeldb path on one machine, causing ModelDb hash mismatch in multiplayer #121

@Lemonade8120

Description

@Lemonade8120

Hi, I’m reporting what looks like a machine-specific BaseLib runtime issue.

Environment:

  • Slay the Spire 2 public-beta
  • Game version: v0.102.0
  • BaseLib version: 0.2.6.0
  • Windows 11
  • Installed from BaseLib release assets (.dll + .pck + .json)

Problem:
On one specific machine, BaseLib is detected and initialized, but it seems to stop after the early init stage.
The log consistently shows:

  • BaseLib.json found
  • BaseLib.dll loaded
  • BaseLib.pck loaded
  • BaseLib.BaseLibMain called
  • Created node factory for Control / NCreatureVisuals / NMerchantCharacter / NEnergyCounter
  • Finished mod initialization for 'BaseLib'

But on this machine I do NOT get the later BaseLib log lines that another machine gets, such as:

  • Patching act types for custom encounters ...
  • Generating interop methods and properties
  • Registered 0 SavedSpireFields

As a result, multiplayer fails with ModelDb hash mismatch.

What I already tested:

  • Same game version and branch
  • Same mod files distributed from my copy to other players
  • Cleared AppData/user data
  • Reinstalled to a new path
  • Created a new Windows local user and tested there
  • Tested with only BaseLib loaded
  • Other machines using the same distributed files do not have this problem

Important result:
On the problematic machine, with ONLY BaseLib loaded, the log shows:

  • Loaded 1 mods (1 total)
  • ModelIdSerializationCache initialized: Categories 19, Entries 1606, Epochs 57, Hash 1902269551

On a normal machine, multiplayer host side previously reported a different ModelDb hash:

  • Hash 869435676

And when joining, the client fails with:

  • ClientConnectionFailedException: ModelDb hash mismatch

This makes me suspect that on this machine BaseLib is loading, but some later patch/model registration path is not taking effect.

I’ve attached logs:

  1. problematic machine, BaseLib only, new Windows user
  2. problematic machine join failure showing ModelDb hash mismatch

Please let me know if there is any extra diagnostic build / verbose logging option I can enable.

补充:
这个问题只出现在我一台机器上。相同的 BaseLib 三件套是从我这里分发给其他人的,其他机器能正常联机或至少不会跑出同样的 BaseLib 行为差异。

godot.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions