Host overloaded or crashed in single player ?

[Veronica Hohenheim]

My game stutters time to time,especially while exlporing new chunks.I have never seen that warning tho.Is it a bug or vs just plays on a local sv in singleplayer ?

[Broccoli Clock]

When you say never seen that warning, what warning? The title of the thread? If so, then like you, I've never encountered it.

The stuttering does suggest something is going on. The obvious question would be do you use mods and is it possible that's the conflict?

If you are on Windows, check your <boot drive>/users/<your username>/AppData/Roaming/VintagestoryData/Logs. In there you should find a selection of logs related to both client and server, with some granularity. These files seem to be refreshed each time you start a new session, so if you see any errors you know they are related directly to the session that is (or last was) active.

Aside from that, I'll chuck in this link.. https://wiki.vintagestory.at/Framerate_and_Performance ..which you may or may not find useful, but as you mention stuttering, it seems a fairly obvious first place to look.

 

Edited October 8, 2025 by Broccoli Clock

[Veronica Hohenheim]

1 hour ago, Broccoli Clock said:

When you say never seen that warning, what warning? The title of the thread? If so, then like you, I've never encountered it.

The stuttering does suggest something is going on. The obvious question would be do you use mods and is it possible that's the conflict?

If you are on Windows, check your <boot drive>/users/<your username>/AppData/Roaming/VintagestoryData/Logs. In there you should find a selection of logs related to both client and server, with some granularity. These files seem to be refreshed each time you start a new session, so if you see any errors you know they are related directly to the session that is (or last was) active.

Aside from that, I'll chuck in this link.. https://wiki.vintagestory.at/Framerate_and_Performance ..which you may or may not find useful, but as you mention stuttering, it seems a fairly obvious first place to look.

 

I use mods and I did see warning when I checked server main log.Tho idk what to do with those.

8.10.2025 10:39:21 [Warning] Failed resolving crafting recipe ingredient with code game:dirtyclaypot-empty in barrel recipe pemmican:recipes/barrel/cleanpot.json
8.10.2025 10:39:21 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code game:claypot-burned in barrel recipe pemmican:recipes/barrel/cleanpot.json
8.10.2025 10:39:21 [Warning] Failed to find vanilla classes: commoner, hunter, malefactor, clockmaker, blackguard, tailor, dont remove vanilla classes (set 'enabled' attribute to 'false' instead), it will cause incompatibility with other mods that change classes, that can result in crashes.

this is a small sample.I wasnt doing anything related,I already chose my class at the start of the game and didnt touch it again and I never crafted a pemmican yet.

[Veronica Hohenheim]

1 hour ago, Broccoli Clock said:

When you say never seen that warning, what warning? The title of the thread? If so, then like you, I've never encountered it.

The stuttering does suggest something is going on. The obvious question would be do you use mods and is it possible that's the conflict?

If you are on Windows, check your <boot drive>/users/<your username>/AppData/Roaming/VintagestoryData/Logs. In there you should find a selection of logs related to both client and server, with some granularity. These files seem to be refreshed each time you start a new session, so if you see any errors you know they are related directly to the session that is (or last was) active.

Aside from that, I'll chuck in this link.. https://wiki.vintagestory.at/Framerate_and_Performance ..which you may or may not find useful, but as you mention stuttering, it seems a fairly obvious first place to look.

 

8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code wolftaming:creature-dog-wolf-pup in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code wolftaming:creature-dog-hunting-pup in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code petai:petcookie-meat-perfect in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-orange in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code game:hay-normal-ud in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-black in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-red in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-plain in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-pink in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code petai:petcookie-veggie-perfect in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-yellow in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-blue in tradeItem resolver

like what is this even mean ? 

[Broccoli Clock]

51 minutes ago, Veronica Hohenheim said:

8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code wolftaming:creature-dog-wolf-pup in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code wolftaming:creature-dog-hunting-pup in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code petai:petcookie-meat-perfect in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-orange in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code game:hay-normal-ud in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-black in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-red in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-plain in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-pink in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks itemdrop or smeltedstack with code petai:petcookie-veggie-perfect in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-yellow in tradeItem resolver
8.10.2025 11:34:07 [Warning] Failed resolving a blocks blockdrop or smeltedstack with code petai:petnest-small-blue in tradeItem resolver

like what is this even mean ? 

I'm going to be honest with you, I would take from that the same that you would. I've never heard of "petcookie" or "petnest-small-black". Looking through the mod database that seems to tie up with https://mods.vintagestory.at/wolftaming, in which case it relies on the PetAI to be installed, and PetAI is currently only officially working on 1.20.x (not the newer 1.21).

As for the previous log snippet, it looks much worse with it warning you about it not being able to load in (or configure) the base classes. That is a pretty major red flag to me, simply because that is core to how the game works.

Ultimately, if you are suffering issues, the first thing to do is remove all the mods and see if vanilla still has those issues. Slowly re-add one by one in order to see which one is causing the issue. You can do this in a brute force manner, or base what you re-add on the log files.

 

Edited October 8, 2025 by Broccoli Clock

[Veronica Hohenheim]

21 minutes ago, Broccoli Clock said:

I'm going to be honest with you, I would take from that the same that you would. I've never heard of "petcookie" or "petnest-small-black". Looking through the mod database that seems to tie up with https://mods.vintagestory.at/wolftaming, in which case it relies on the PetAI to be installed, and PetAI is currently only officially working on 1.20.x (not the newer 1.21).

As for the previous log snippet, it looks much worse with it warning you about it not being able to load in (or configure) the base classes. That is a pretty major red flag to me, simply because that is core to how the game works.

Ultimately, if you are suffering issues, the first thing to do is remove all the mods and see if vanilla still has those issues. Slowly re-add one by one in order to see which one is causing the issue. You can do this in a brute force manner, or base what you re-add on the log files.

 

tbh I dont wanna do all that.I am just gonna hope this wont become frequent cuz I am already invested in a save and I dont want to go trough a long process of troubleshooting and then mess my save too.Its not unbearable.Its just annoying.

[Veronica Hohenheim]

Just now, Veronica Hohenheim said:

Its not unbearable.Its just annoying.

the stutters*

[Broccoli Clock]

28 minutes ago, Veronica Hohenheim said:

tbh I dont wanna do all that.

Not sure what other choice you have. If the game with mods was working before (I presume it was), and update happened which broke things, it's likely going to be the mods that are causing it. The devs will be testing the vanilla branch solidly, they won't be testing for all the possible mod combinations. That's up to the mod authors. Now I have a mod, it's a very simple one, built for 1.20, it works in 1.21 without change (and I presume <1.20 too, but never tested), but I still need to test it against a new build then go into the mod database and update the mod to show it is compatible with the latest version. The "modding echosystem" seems really tight in VS, but modders need to keep their mods active/up to date otherwise you can end up in situations similar to yours.

Of course this could be something different but from the limited log snippets you have pasted, I'd be looking at the mods.

If you know what version ran well for you with your mod configuration (was it a 1.21.x or 1.20.x), then one solution could be running that. Go to the client area and install a previous version that was working for you.. https://account.vintagestory.at/downloads (there is a Show all versions trigger below the main download link). 

Edited October 8, 2025 by Broccoli Clock

[Veronica Hohenheim]

15 minutes ago, Broccoli Clock said:

Not sure what other choice you have. If the game with mods was working before (I presume it was), and update happened which broke things, it's likely going to be the mods that are causing it. The devs will be testing the vanilla branch solidly, they won't be testing for all the possible mod combinations. That's up to the mod authors. Now I have a mod, it's a very simple one, built for 1.20, it works in 1.21 without change (and I presume <1.20 too, but never tested), but I still need to test it against a new build then go into the mod database and update the mod to show it is compatible with the latest version. The "modding echosystem" seems really tight in VS, but modders need to keep their mods active/up to date otherwise you can end up in situations similar to yours.

Of course this could be something different but from the limited log snippets you have pasted, I'd be looking at the mods.

If you know what version ran well for you with your mod configuration (was it a 1.21.x or 1.20.x), then one solution could be running that. Go to the client area and install a previous version that was working for you.. https://account.vintagestory.at/downloads (there is a Show all versions trigger below the main download link). 

I installed the game at 1.21 and didnt update it since cuz I was afraid the compability with the mods.This did happen with additional mods,the error message I mean but even in the first save with far fewer mods it was still stuttering time to time.It is not a huge deal as I said,it mostly happens while exploring and I just wait for a few seconds and keep going on.Idk.I am also afraid that I might need to delete mods I dont want to so I am staying away from it.

[Broccoli Clock]

12 minutes ago, Veronica Hohenheim said:

I installed the game at 1.21 and didnt update it since cuz I was afraid the compability with the mods.This did happen with additional mods,the error message I mean but even in the first save with far fewer mods it was still stuttering time to time.It is not a huge deal as I said,it mostly happens while exploring and I just wait for a few seconds and keep going on.Idk.I am also afraid that I might need to delete mods I dont want to so I am staying away from it.

If it worked before with the mods, then I see no issue going back to the version that the mods worked with. I know players still on their 1.20 world because they don't want to lose mods that haven't been updated. If you installed a load of mods that hadn't been updated to 1.21 I'm not saying they won't work but it's going to be a toss up as to whether they error (or cause slow down/stuttering) or are fine. 

If vanilla runs fine without error, and removing the mods is as simple as deselecting them rather than physically deleting them - unless you have manually added the mod in specific folder locations rather than use the 1-click-install method, then it really does point to the mods. You can make a backup of your world if you are worried about testing without mods, but in the end running a modded world with the mods disabled tends to leave "broken blocks" in your game rather than your game failing outright. That's a generalisation as I don't know the mods, their versions, or their configurations, that you are using.

Edit: One of the main reasons to test with a no modded vanilla (hell, you could just create a new test world without mods for this, rather than hit your current world) is to make sure that the stuttering is directly related to the game having issues with mods, rather than something on your OS (just for example sake, your virus checker gets really annoyed at programs updating data in the user/AppData folder, and VS regularly updates the save file in that folder).

I am no expert in debugging VS, btw. I have tech skills, and I'm a C# Dev (the platform VS runs on) so you might find posting this in the support section -  https://www.vintagestory.at/forums/forum/15-vintarian-support/ - or checking out the modding section to see if mods are supported or being updated for a specific version - https://www.vintagestory.at/forums/forum/17-mod-releases/ - may result in people with more knowledge than I seeing your issue.

 

Edited October 8, 2025 by Broccoli Clock

[LadyWYT]

1 hour ago, Broccoli Clock said:

If it worked before with the mods, then I see no issue going back to the version that the mods worked with. I know players still on their 1.20 world because they don't want to lose mods that haven't been updated. If you installed a load of mods that hadn't been updated to 1.21 I'm not saying they won't work but it's going to be a toss up as to whether they error (or cause slow down/stuttering) or are fine. 

I do agree that the mods are almost certainly the culprit regarding the stutters, but I'm not sure about rolling back game versions or uninstalling the mods and continuing on the same world. Generally, uninstalling mods mid-playthrough isn't recommended, but in my experience it's safe in VS, for the most part, and most mods will list whether or not it's safe to do so on the mod page. As for rolling back the world to a previous version...that I'm not sure. I would absolutely make a backup of the world in case something goes wrong.

In any case, removing the offending mods should fix the stutter, and probably the "host not responding" bit as well. However, I have seen "host not responding" occasionally in vanilla singleplayer, so it's not limited to multiplayer. I've not noticed it causing issues the few times it occurs, and it generally crops up when new chunks are being generated, or when the game is otherwise putting a heavier workload on the pc.