Kris G's Bug-testing thread

[NottheKrisyi]

Well, imma start experimenting with bugs, specially crash bugs, why? Well, ive seen many bug reports of stuff that happens to a lot of people but not to me, so i kind of wanna test the bugs to see where the thing crosses the line for it to execute.

Ill write down my findings in this topic post, of course, other people of the forums are free to comment bugs that annoy them, i can maybe test em out

Heres what i found until now

• The Bug that makes old worlds crash constanly appears to begin to show itself around day 600, the second most young long term server that i have is around day 615, and the youngest is around 250 days old, the 600 days old world showed the bug persisting in it, meanwhile the 200 days old did not, however...
• The Bug that makes the game crash meanwhile in the ocean. In the 200 day old world everything was working perfectly until i stepped into the ocean, the game did not crash inmediately at all instead the world started behaving like if it was a 600+ days old world, the game doesnt crash inmediately but it becomes a time bomb and it can crash at any time without reason, the most common crash time being every 2 days. This as far as i have checked does not aply to very young worlds like year 1 worlds because i have been in The Ocean in public servers since late October (which is where these bugs started appearing for me) and the game didnt behave like a old world, however this may be due to me not being the owner? But perhaps not, ill test if the game not being unstable meanwhile in the ocean correlates to me being ot not the owner of the server ot the world being very young soon. Aditionally i was Wortox in the 200 days old world and Wurt in the 600, I have seen people mention the ocean bug is more common/only exists when playing as Wortox, ill check if Wortox also has correlation w the bug soon

 This is everything that u have checked for now, i will update my findings in this thread, aditionally i invite yall to tell me bugs to test and discuss about them, maybe find how to avoid them, or make things easier for Klei if they decide to patch these, among other stuff

[InaGaZ]

hi I allow myself to be included in your approach. I also did a set of specific tests described below:

- Situation(s) tested:

Game on Switch 2 with an online server in 2-player split-screen mode (common point to all situations). Some worlds used (goes from the virgin world 0d to the world 300d, some hosted locally by player 1, some by player 2, all on the same console. Some worlds came from the transfer of switch 1, others were created exclusively on switch 2). practically all the characters have been played at least 10/20 days each on all my tests
 

- fault report(s):

• Brutal crash of the game during the automatic save at the beginning of the day, forcing to restart the game. Reconnection to the world always generates an identical crash preventing a return to the world as it is.

---> frequency of breakdown: non-existent in the first 50 days (approximately), very frequent from day 100 onwards. Special cases observed: I have already had the crash once at the beginning of day 21, during the visual transition of winter. An occurrence of rain/frogs is particularly penalizing. Even if the event at the moment does not crash the server, we can expect to have this crash during the backup of the beginning of the next day.

 

• Various random crashes during "new" server events: discovery of zones/objects, opening the magic chest, adding an info in the album, new recipe.

---> frequency of failure: quite rare. was on the other hand very common during update 1220. since 1230, became very rare (but I haven’t really recreated a virgin world since then so no "new" discoveries on these worlds since

- temporary solutions found:

• for the crash of the beginning of the day:

1. if it’s a crash purely for no reason, we manage to reconnect by insisting 2/3/4 times
2. if it’s a crash related to a graphic event (rain, change of season, new scenery): impossible to reconnect (even after 10/20 tries) without changing the situation. The one that works best is to reconnect in solo, then isolate the player on another zone, the opposite server (cave/surface) to player 2 is the best. Then reconnect in split-screen mode and despite a final crash, the game starts again.

• for the random crash:

1. return to a previous backup. Most of the time, the same action redone no longer reproduces the crash

• for all the problems mentioned above:

1. None of these crashes are observed in solo mode, including if I replay my worlds on my old switch 1. Which gave me an idea that works!!! if my partner plays on my TV/switch 2 and me on my switch 1 (portable mode), we no longer have any crashes at all. But that it’s penalizing (in addition to having to buy a 2nd version of the game, which I didn’t need without this test, you see Klei I’m not resentful but well ...)

- PS : Unlike many, I have never encountered any issues at sea, including in shared mode, but I would like to note that I have never really played on important servers during the day (Max 350j) and I never really fully discover this area of the game. (but I still discover the important areas, islands and crab)

[CrimsonStrider]

I've already been testing this. Right now I'm working with Winona and Walter.

I don't know if it's day related. I think day count is just the most obvious thing.

My thoughts:

1. Something related to rifts. 

2. Something related to the amount of people that have played on the server. 

3. Something related to being on the ocean.

4. Something more common with Wortox. 

5. Something related to CC.

My Walter world is less than 200 and everything is done. So far I've had 2 crashes. The first was while doing CC a second time. The second was shortly after while on the ocean.

My Winona world has had one or two crashes on the ocean. 

Walter world has been completely private and Winona world hasn't had more than a couple join.

By far both times I had a Wortox world I crashed the most. On my more recent Wortox world a lot of the crashing stopped after switching characters but still happens more than fresh worlds. That world has also had 20-40 different people join at some point.

CC is also also a consistent crashing spot.

 

@InaGaZ

 

Split screen shouldn't really be mentioned in the same way these bugs occur. Split screen is its own issue and is incredibly buggy and laggy. It should either be removed or fixed but I understand your frustration and it's a very poor way to experience this game on Switch.

[InaGaZ]

I agree with the fact that the split screen problems are not the same as those that may concern specific situations like the sea with Wortox.

I mention it because I have made it my battle horse against KLEI and that I deeply believe it has a more global link with the other random issues and especially since its setup is less random, the developers could perhaps start with this bug  (I am even surprised that they have never communicated on this subject but well they are not very talkative regarding the Switch experience, leaving us orphans).

It is not a selfish approach but logical (debug the biggest problems to refine towards the most precise ones). Normally I should echo myself by telling myself that insisting on such a bug is not necessary because developers, whose job it is, are necessarily aware and act in the shadows, but KLEI has never once communicated about these issues, so when in doubt... we insist

I also think that the split screen mode is more popular than we think and makes DST a very 'compatible couple' game, and above all it worked more or less very well until before 1220

[JoePorter]

So, Since these bugs probably won't be fixed anytime soon, the only thing you can do is save your game at each section while at sea—I mean, quit and re-enter the game every four minutes. 

[NottheKrisyi]

4 hours ago, JoePorter said:

So, Since these bugs probably won't be fixed anytime soon, the only thing you can do is save your game at each section while at sea—I mean, quit and re-enter the game every four minutes. 

For me a lot of the time the game doesnt save using that method, but that may have been fixed?

[CrimsonStrider]

In my Winona world I've started crashing.

Began happening fairly frequently yesterday. 

Post Cave Rifts around day 150.

Going into and out of caves would sometimes cause the game to get stuck on the loading screen and require exiting software. Other times it gave me a message "Authentication failed" and brought me to the login menu.

Going into/out of caves is noticeably slower, and going quickly into/out of 3 times or so is usually when I have an issue. Such as when forgetting something. 

I just started exploring the sea. Have crashed multiple times. Some prior to CC. Currently post rift. Didn't crash during CC but expect to crash during my 2nd kill.

 

@NottheKrisyi

If you disconnect it usually correctly creates a save point at that time.

Sometimes, it doesnt correctly save and x patches ago it was more often reloading at the start of the day, but that hasn't been happening much if at all to me for a while.

So best practice is to manually disconnect while on the ocean if you want to create a save point. At least after every important event (any Pearl tasks, CK, treasure, etc).

Edited January 11 by CrimsonStrider

[NottheKrisyi]

On 1/10/2026 at 5:55 PM, CrimsonStrider said:

In my Winona world I've started crashing.

Began happening fairly frequently yesterday. 

Post Cave Rifts around day 150.

Going into and out of caves would sometimes cause the game to get stuck on the loading screen and require exiting software. Other times it gave me a message "Authentication failed" and brought me to the login menu.

Going into/out of caves is noticeably slower, and going quickly into/out of 3 times or so is usually when I have an issue. Such as when forgetting something. 

I just started exploring the sea. Have crashed multiple times. Some prior to CC. Currently post rift. Didn't crash during CC but expect to crash during my 2nd kill.

 

@NottheKrisyi

If you disconnect it usually correctly creates a save point at that time.

Sometimes, it doesnt correctly save and x patches ago it was more often reloading at the start of the day, but that hasn't been happening much if at all to me for a while.

So best practice is to manually disconnect while on the ocean if you want to create a save point. At least after every important event (any Pearl tasks, CK, treasure, etc).

Im starting to think day count doesnt really have anything to do with **** and its hust uf you activated rifts the world is cooked. My worlds that crashed were all after i killed CC and had rifts, i have a 1000+ days old world without rifts i should test sh there

[NottheKrisyi]

On 1/13/2026 at 10:51 AM, NottheKrisyi said:

Im starting to think day count doesnt really have anything to do with **** and its hust uf you activated rifts the world is cooked. My worlds that crashed were all after i killed CC and had rifts, i have a 1000+ days old world without rifts i should test sh there

I seem to be right.

My riftless 1300 days old world seems to be working perfectly

But all my worlds post-rifts crash

Desactivating rifts on the settings doesnt seem to fix anything

So it seems when you kill a final boss/activate rifts naturally the world is permanently f*cked

The issue looks to connect to the code that identifies if a world has their rifts activated naturally? 

[Herrenhauser]

Hello. I am a player from South Korea who plays Don’t Starve on the Nintendo Switch 2.

While playing the Switch version of Don’t Starve, I have experienced several crash issues similar to those reported by others, so I wanted to share my experience here.

 

This is a very long post, so you don’t need to read everything. I summarize what I believe to be the core cause of the crashes in the final paragraph.

 

I started playing Don’t Starve in split-screen mode with my girlfriend around September last year. At first, we played entirely offline, and during that period, we did not experience any errors at all.

 

The crashes seemed to start after I subscribed to Nintendo Switch Online and began playing in online mode. The first crashes could be fixed simply by rebooting the Switch, so I didn’t think much of them at the time.

 

However, the crashes began occurring much more frequently after I linked my Klei account to the Nintendo Switch. Since I had previous progress on the PC version, I installed a Wardrobe to apply skins I had earned on PC. When I interacted with the Wardrobe to change outfits, the game crashed. At that time, I assumed the crash was caused by a conflict while referencing skin data, so I stopped using wardrobe-related content entirely.

 

This was the first major crash issue on my first world, which occurred at around day 200.

 

The second world did not last nearly as long. After the Winter update, I purchased a new character on Steam and applied skins to that character. Then I continued playing on the Nintendo Switch. (For reference, I played Wormwood, and my girlfriend played Wurt.) Initially, the game ran without issues.

 

Later, I returned to the main menu to open the Winter event reward chest I had earned during gameplay. While there, I opened the Winter chest and changed skins, character portraits, loading screens, and player icons. From that point on, crashes started occurring during gameplay.

 

I attempted to reconnect multiple times, but almost every connection attempt in split-screen mode failed, even after rebooting the Switch. While investigating the issue, I noticed that the second player’s loading screen had reverted to the default one, despite having been changed earlier. This led me to suspect that the client was detecting mismatched data between my current settings and the world data, resulting in an error.

 

After changing various settings and retrying, I was able to play again, but only for a few days. Eventually, the same crash occurred again, and we abandoned the world on day 21.

 

Now I will describe what happened in the third world. Initially, this world progressed smoothly without any crashes. However, crashes started occurring after we began using boats. When a crash happened, it was difficult to re-enter the world in split-screen mode, and when we did manage to reconnect, the world progress was always rolled back to the previous morning.

 

To resolve this, I tried a workaround shared by other players: entering the world in single-player mode, moving Player 1 into the Caves, and then reconnecting in split-screen mode. This temporarily resolved the issue, allowing us to continue playing.

 

However, after a few days (about three days, I believe), the same crash occurred again, and progress was rolled back once more. Sometimes entering the caves fixed it, but eventually that method stopped working as well.

 

At that point, I suspected a data conflict between the skins set in the main menu and the skins applied in-game. Using the Celestial Portal, I changed the in-game skins to match the main menu settings. After doing this, the issue did not occur for several days—but eventually, it returned.

 

Currently, when a crash occurs, I repeatedly switch between single-player and multiplayer until the crash stops happening. In many cases, Player 2 successfully loads into the world, but the game crashes while Player 1 is still loading. In those situations, I found that repeatedly pressing the A button as Player 2 to perform actions like picking up items sometimes allows the world to finish loading. This is only my speculation.

 

After experiencing these crashes multiple times, I noticed one common pattern: crashes almost always occur when world conditions change, such as when the in-game day advances. The game always saves at that moment, and that is when the crash happens.

 

Based on this, my hypothesis is that during the saving process, the game performs data validation, and if mismatched data is detected, it throws an error. I’m not sure whether the conflict is between Steam and Switch data, main menu settings and in-game settings, or Player 1 and Player 2 data. However, what is clear is that crashes occur far more frequently in split-screen mode than in single-player, and that the issue has become much more noticeable since the Winter update.

 

I sincerely hope Klei can address and fix this issue soon.

Thank you very much for reading this long post.

 

 

 

P.S. This post was translated from Korean using AI, so there may be some awkward expressions or misunderstandings. Thank you for your understanding.

[InaGaZ]

Do you confirm our feelings about the 'daily bug/backup'
I am doing a feedback in class but which already gives conclusions:
- I took up almost all my games and those of my wife (account 1 and account 2) and played almost 30/40 days on each one, changing nothing other than the use of 2 game consoles instead of the shared mode. 
- I want to specify that I had to buy the game a second time so it’s really perseverance
- I no longer have any crashes at all during backups, nor have I encountered crashes.
- I am mixed about this gaming experience because we have regained the pleasure of playing with 2 players but my personal pleasure (I spared my wife who keeps the TV) is greatly degraded because I play on the screen of the Switch 1 and we no longer see each other’s lives like that.

We must therefore consider that the shared mode remains something useful and I would not want it to end up abandoned.

[NottheKrisyi]

On 1/20/2026 at 10:50 AM, InaGaZ said:

Do you confirm our feelings about the 'daily bug/backup'
I am doing a feedback in class but which already gives conclusions:
- I took up almost all my games and those of my wife (account 1 and account 2) and played almost 30/40 days on each one, changing nothing other than the use of 2 game consoles instead of the shared mode. 
- I want to specify that I had to buy the game a second time so it’s really perseverance
- I no longer have any crashes at all during backups, nor have I encountered crashes.
- I am mixed about this gaming experience because we have regained the pleasure of playing with 2 players but my personal pleasure (I spared my wife who keeps the TV) is greatly degraded because I play on the screen of the Switch 1 and we no longer see each other’s lives like that.

We must therefore consider that the shared mode remains something useful and I would not want it to end up abandoned.

I dont use it myself

But i really agree with the sentiment, this stuff really shouldnt be left in the dark, Klei should put more attention to DST Switch in gen, like adding chat among other stuff, fixing the split-screen mode being beneath this umbrella of making DST Switch an overall better port