Guidefor players3 min read

Comforts sleeping bags that reset your respawn point to world spawn

The whole point of a Comforts sleeping bag is sleeping without moving your spawn point. Sometimes it does the opposite: your spawn point goes null and you respawn at world spawn instead. What is actually happening and how to protect yourself.

What the bug looks like

Comforts sleeping bags exist for one reason: sleep in one to skip the night without dragging your actual spawn point away from your real bed. Sometimes it does the opposite instead. You sleep in the bag, and later, when you die, you respawn at world spawn rather than anywhere near where you slept.

Players describe it in almost identical terms across separate reports. One CurseForge comment: "they keep resetting my respawn point everytime i use them, so when i die i don't respawn in my bed. i respawn in the world spawn because my spawn object was not found (the sleeping bag)." A second, independent commenter on a different version says the same thing in different words: "comforts sleeping bags seem to reset spawn point (to null), forcing the respawn to be world spawn." Neither mentions a crash or an error screen. The game just quietly forgets where you meant to respawn.

What is actually stored, and how it fails

A Comforts sleeping bag works the way a vanilla bed does for respawn purposes: instead of storing coordinates directly, the game stores a reference to the block itself, then checks that the block is still there and still valid before honoring it as your respawn point. Vanilla beds go through the same check, which is why breaking your bed gets you a chat message that your spawn point is missing or obstructed.

The "spawn object was not found" phrasing from the CurseForge comment reads like that same validation failing, just without vanilla's chat warning to explain it. The stored reference to the sleeping bag goes stale, the game looks for it and cannot find something valid, and it falls back silently to world spawn instead of telling you why.

What is confirmed versus what traces to other mods

Two issues on the Comforts GitHub tracker document this exact symptom two years apart. Issue #124, filed in June 2023 against comforts-forge-6.3.3 on Minecraft 1.20.1, describes a sleeping bag resetting spawn on death. The maintainer replied that they could not reproduce it running Comforts alone. The reporter came back two months later: the actual cause was the Dusk mod.

Issue #180, filed in July 2025 on the same Minecraft version, reports the identical symptom in almost the same words: sleeping bags "setting phantom respawn points causing my players to respawn at world spawn." Two other users confirmed hitting it independently before one of them, B-Wither, dug in far enough to test a completely different mod's portable bed, Sleep Tight's night bag, and got the same ghost spawn point there too. The trail eventually led to Cold Sweat as the actual trigger in that case.

So neither tracked report pins the defect on Comforts' own code in isolation. What is confirmed is that Comforts' stored respawn reference is fragile enough that at least two unrelated mods, in two different years, on the same base version, have been able to corrupt it and produce the identical silent fallback to world spawn. That is a narrower claim than "Comforts is buggy," and a more useful one: this is a recurring failure mode of how portable bed alternatives track respawn state when other mods are also touching player data, not a single bug with a single fix.

The practical takeaway

Both issues got closed as resolved without a documented Comforts-side patch, and the same symptom came back under a different culprit mod the second time. Do not treat either closure as proof this cannot happen to you. Keep a real bed as a backup respawn point rather than depending on the sleeping bag alone, particularly on a long-running server where a temperature or day cycle mod like Cold Sweat might be installed for reasons that have nothing to do with sleep. If your spawn point ever silently reverts to world spawn after using a sleeping bag, sleep in an actual bed once to reset it properly, and if it keeps happening, use the halving method to find out which of your other mods is really responsible.

Frequently asked

Does this affect hammocks too, or only sleeping bags?

Every report that names a specific block names the sleeping bag. Hammocks and sleeping bags in Comforts are both implemented as portable bed alternatives sharing the same respawn logic, so the same failure mode is plausible for hammocks, but nobody has filed a tracked report naming one specifically. Treat this as a risk for both, confirmed for the sleeping bag.

Is this a bug in Comforts itself?

Not cleanly. In both tracked GitHub issues, the maintainer could not reproduce the problem with Comforts running alone, and the reporter eventually traced it to a different mod entirely: Dusk in the 2023 report, Cold Sweat in the 2025 report. Comforts provides the mechanism that breaks, a stored respawn reference, but something else in the modpack is what corrupts it.

So has it actually been fixed?

Both issues are labeled resolved and closed, but neither closure describes a code change inside Comforts. They read more like "identified and not Comforts' fault" than "patched." The same symptom recurred two years later with a different culprit mod, which means whatever makes Comforts vulnerable to this is still present, even though each individual report got closed.

What should I actually do about it?

Keep a real vanilla bed as a backup respawn anchor instead of relying on a sleeping bag alone, especially on a server. If you run Cold Sweat, Dusk, or any other mod that touches player state, temperature, or day and night cycles alongside Comforts, treat this as a known risk rather than a surprise. If it happens to you, sleep in a real bed once to reset your spawn point properly.

How do I find out which mod is actually causing it in my pack?

Remove suspect mods one at a time and repeat the sleeping bag and die cycle, the same halving approach covered in fixing an incompatible mod set. Cold Sweat and Dusk are the two confirmed culprits so far, but the underlying pattern, some other mod interfering with how Comforts validates its stored spawn location, is broader than just those two.

Last reviewed 2026-08-05. Version data on this site updates automatically; this guide is reviewed by hand when the ecosystem changes.