Javelin_F61 Posted August 23, 2025 Report Posted August 23, 2025 The title is the question, every time i try and load into the server it will immediately crash my game, most of the times with no crash report, the one time it showed a crash report the log was the file attached to this. Sometimes it would also end up causing other players to crash as well when i try to join. My drivers are fully updated and everyone + myself were able to play on the server fine for a couple hours before randomly encountering any issues. the mod list we were playing with is also attached as a screenshot. I tried a full redownload of my game and it still didn't fix anything, if anyone has any ideas on how to fix this that would be great, thank you. message.txt
Javelin_F61 Posted August 23, 2025 Author Report Posted August 23, 2025 My bad the text file is kinda weird, this is the crash log i got Running on 64 bit Windows 10.0.26100.0 with 15713 MB RAM Game Version: v1.20.12 (Stable) 8/23/2025 12:25:05 AM: Critical error occurred Loaded Mods: System.Exception: Coding error: Mods must not get assets before AssetsLoaded stage - do not load assets in a Start() method! at Vintagestory.Client.NoObf.TextureAtlasManager.LoadBitmap(ClientMain game, AssetLocationAndSource textureLoc) in VintagestoryLib\Client\Render\Atlas\TextureAtlasManager.cs:line 841 at Vintagestory.Client.NoObf.TextureAtlasManager.LoadBitmapPixels(ClientMain game, AssetLocationAndSource source, Int32 rot, Int32 alpha, Dictionary`2 cache, Int32& readWidth, Int32& readHeight) in VintagestoryLib\Client\Render\Atlas\TextureAtlasManager.cs:line 792 at Vintagestory.Client.NoObf.TextureAtlasManager.LoadCompositeBitmap(ClientMain game, AssetLocationAndSource compositeTextureLocation, Dictionary`2 cache) in VintagestoryLib\Client\Render\Atlas\TextureAtlasManager.cs:line 712 at Vintagestory.Client.NoObf.TextureAtlasManager.LoadBitmaps(BakedBitmap[] bitmaps) in VintagestoryLib\Client\Render\Atlas\TextureAtlasManager.cs:line 492 at Vintagestory.Client.NoObf.TextureAtlasManager.<>c__DisplayClass58_0.<PopulateTextureAtlassesFromTextures>b__0() in VintagestoryLib\Client\Render\Atlas\TextureAtlasManager.cs:line 446 at Vintagestory.API.Util.AsyncHelper.Multithreaded.OnWorkerThread(Action task) in VintagestoryApi\Util\AsyncHelper.cs:line 52 at Vintagestory.API.Util.AsyncHelper.Multithreaded.<>c__DisplayClass3_0.<StartWorkerThread>b__0() in VintagestoryApi\Util\AsyncHelper.cs:line 44 at Vintagestory.API.Common.TyronThreadPool.<>c__DisplayClass13_0.<QueueTask>b__0(Object a) in VintagestoryApi\Common\TyronThreadPool.cs:line 122 at System.Threading.QueueUserWorkItemCallback.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.PortableThreadPool.WorkerThread.WorkerThreadStart() Event Log entries for Vintagestory.exe, the latest 3 ================================== { TimeGenerated = 8/23/2025 12:00:25 AM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.12.0, time stamp: 0x66470000 Faulting module name: coreclr.dll, version: 7.0.1023.36312, time stamp: 0x64b06d6c Exception code: 0xc0000005 Fault offset: 0x00000000001c98a6 Faulting process id: 0x11f68 Faulting application start time: 0x1dc13e2546f9a1b Faulting application path: D:\Vintagestory\Vintagestory.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll Report Id: e24b7c60-93d1-4d62-b95f-36f4c8d00c53 Faulting package full name: Faulting package-relative application ID: } -------------- { TimeGenerated = 8/22/2025 11:59:04 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.12.0, time stamp: 0x66470000 Faulting module name: coreclr.dll, version: 7.0.1023.36312, time stamp: 0x64b06d6c Exception code: 0xc0000005 Fault offset: 0x00000000001c98a6 Faulting process id: 0xb604 Faulting application start time: 0x1dc13e230f98eb2 Faulting application path: D:\Vintagestory\Vintagestory.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\7.0.10\coreclr.dll Report Id: cc4a5f69-e928-44b1-9b68-a58476bdd78b Faulting package full name: Faulting package-relative application ID: } -------------- { TimeGenerated = 8/22/2025 11:58:25 PM, Site = , Source = Application Error, Message = Faulting application name: Vintagestory.exe, version: 1.20.12.0, time stamp: 0x66470000 Faulting module name: nvapi64.dll, version: 32.0.15.8088, time stamp: 0x6885c44f Exception code: 0xc0000005 Fault offset: 0x00000000002c17c9 Faulting process id: 0x117e0 Faulting application start time: 0x1dc13e2074d2795 Faulting application path: D:\Vintagestory\Vintagestory.exe Faulting module path: C:\WINDOWS\SYSTEM32\nvapi64.dll Report Id: 880768fb-0fa9-4f0b-9d71-65c5b1366f7b Faulting package full name: Faulting package-relative application ID: }
LadyWYT Posted August 23, 2025 Report Posted August 23, 2025 Welcome to the forums! As best I can tell, this seems to be caused by a coding error in one of the mods...at least that's my best guess. I'm not sure which mod though. I would check to make sure that the mods are all the appropriate version for 1.20.12, just in case there's one that's perhaps made for 1.21, or otherwise out-of-date. Out-of-date mods do sometimes work on newer versions of the game, but not always. Aside from that, you could test each mod individually(or each mod + any other mods it may require) in singleplayer and see if you can reproduce the issue. If the issue happens again, then you know exactly which mod is responsible.
Javelin_F61 Posted August 24, 2025 Author Report Posted August 24, 2025 1 hour ago, LadyWYT said: Welcome to the forums! As best I can tell, this seems to be caused by a coding error in one of the mods...at least that's my best guess. I'm not sure which mod though. I would check to make sure that the mods are all the appropriate version for 1.20.12, just in case there's one that's perhaps made for 1.21, or otherwise out-of-date. Out-of-date mods do sometimes work on newer versions of the game, but not always. Aside from that, you could test each mod individually(or each mod + any other mods it may require) in singleplayer and see if you can reproduce the issue. If the issue happens again, then you know exactly which mod is responsible. We figured out the issue, the combat overhaul mods were all just out of date and when we removed them the crashes stopped
Javelin_F61 Posted August 24, 2025 Author Report Posted August 24, 2025 Thank you for the welcome as well
Recommended Posts