Help needed with frequent crashes on modded server v1.21.1 (Stable)

[Luxie]

I was hoping someone could help me out with reading the crashlog and figureing out what's causing my game to crash.

This is the log from the crash reporter:

Quote

Running on 64 bit Windows 10.0.26100.0 with 32694 MB RAM
Game Version: v1.21.1 (Stable)
08/10/2025 16:12:12: Critical error occurred in the following mod: ndltimetracker@4.0.0
Loaded Mods: ancientarmory@1.1.4, birdseye@0.1.3, chiseltools@1.15.1, claimnavigator@1.1.0, ClaimsRadar@1.1.0, forestsymphony@1.0.6, froghats@1.1.1, immersivelanterns@0.2.0, millwright@1.2.8, moreiconscs@1.1.1, nightskydelights@1.21.0, overhaullib@1.10.2, particlesplus@2.3.1, plumpkins@1.1.3, primitivesurvival@3.9.7, prospecttogether@2.1.1, sortablestorage@2.4.2, tankardsandgoblets@1.3.0, valkyrjahair@2.2.0, game@1.21.1, zoombuttonreborn@2.0.0, apegrapes@1.3.1, attributerenderinglibrary@2.3.0, betterfirepit@1.1.6, betterruins@0.5.0, bloodtrail@1.0.7, carryon@1.10.9, chiselwiz@2.0.0, commonlib@2.8.0, coolergreens@1.0.0, daytrader@1.0.5, enhancedhandbook@1.7.0, extrainfo@1.10.1, hudclockpatch@1.1.2, itempickupnotifier@1.7.3, jebsinventorytweaks@1.1.1, meteoriccrystal@1.0.1, nbcartographer@2.2.1, ndltimetracker@4.0.0, noticeboard@1.1.2, playerlist@2.1.5, playermodellib@1.0.10, rpvoicechat@2.3.23, simpleemotemenu@2.0.0, slowtox@3.0.1, spawnhighlightredux@1.0.2, stepupcontinued@0.0.1, stonebakeoven@1.2.0, versionchecker@1.2.2, vinconomy@5.0.3, vintagesymphony@1.0.4, creative@1.21.1, vsinstrumentsbase@2.0.4, survival@1.21.1, zinkmodautoclay@1.0.3, em@3.3.1, extraoverlays@1.6.0, quiversandsheaths@0.4.1, shearlib@1.2.0, stonequarry@3.5.1, vintagesymphonyassets@1.1.0, vsinstruments_quackpack@1.0.2, tailorsdelight@2.0.0, wool@1.7.1
System.NullReferenceException: Object reference not set to an instance of an object.
   at ndltimetracker.ndltimetrackerModSystem.<>c__DisplayClass12_0.<SavePlaytimeData>b__0() in P:\NDL Mods VS\NDL-TimeTracker\ndltimetracker\ndltimetracker\ndltimetrackerModSystem.cs:line 147
   at Vintagestory.Client.NoObf.ClientMain.ExecuteMainThreadTasks(Single deltaTime) in VintagestoryLib\Client\ClientMain.cs:line 786
   at Vintagestory.Client.GuiScreenRunningGame.RenderToPrimary(Single dt) in VintagestoryLib\Client\MainMenu\Screens\GuiScreenRunningGame.cs:line 172
   at Vintagestory.Client.ScreenManager.Render(Single dt) in VintagestoryLib\Client\ScreenManager.cs:line 719
   at Vintagestory.Client.ScreenManager.OnNewFrame(Single dt) in VintagestoryLib\Client\ScreenManager.cs:line 663
   at Vintagestory.Client.NoObf.ClientPlatformWindows.window_RenderFrame(FrameEventArgs e) in VintagestoryLib\Client\ClientPlatform\GameWindow.cs:line 113
   at OpenTK.Windowing.Desktop.GameWindow.Run()
   at Vintagestory.Client.ClientProgram.Start(ClientProgramArgs args, String[] rawArgs) in VintagestoryLib\Client\ClientProgram.cs:line 338
   at Vintagestory.Client.ClientProgram.<>c__DisplayClass10_0.<.ctor>b__1() in VintagestoryLib\Client\ClientProgram.cs:line 133
   at Vintagestory.ClientNative.CrashReporter.Start(ThreadStart start) in VintagestoryLib\Client\ClientPlatform\ClientNative\CrashReporter.cs:line 95

Event Log entries for Vintagestory.exe, the latest 1
==================================
{ TimeGenerated = 06/10/2025 19:39:37, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.21.1.0, time stamp: 0x67fe0000
Faulting module name: coreclr.dll, version: 8.0.1925.36514, time stamp: 0x68769299
Exception code: 0xc0000005
Fault offset: 0x00000000001d9e2d
Faulting process id: 0x5274
Faulting application start time: 0x1dc36e8194fe493
Faulting application path: C:\Users\kimlo\AppData\Roaming\Vintagestory\Vintagestory.exe
Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\8.0.19\coreclr.dll
Report Id: 52660591-afc1-4bef-9861-d6c07813644d
Faulting package full name: 
Faulting package-relative application ID:  }

I also attached the full crash logs below

crashlogs.zip

[Echo Weaver]

The error is being thrown in NDL Timetracker. Have you tried removing that mod? 

Details on the mod page indicate there was a big change in the most recent release that was not backward-compatible. The page includes details on how to migrate your game to the new version. If you used an automatic mod updater, you might not have seen that. I don't use an auto-updater for that reason. I use Version Checker instead, so I can do the actual update manually and look at what has changed.

[Luxie]

That was exactly it, thank you!