When extinguishing the campfire or removing it, restore the spawn point to the previous one, or to the player's bed.

This could be configurable:

• With setting previous respawn point, you can place a campfire, then another one in another place, then remove the second one and your spawn pont reverts to the previous one. To avoid storing an absurd amount of previous spawn points, this could be configurable to a maximun of perhaps 5 or 10 spawn points.
• With setting previous respawn to bed, every new campfire makes itself your spawn point, but if it is removed or extinguished, your previous spawn point is your bed.
• Combination of the two? up to 5 or 10 spawn points on top of your bed, as a list, and whenever one of the campfires or bed is removed, that spawn point is removed from the list.

Should not work across dimensions.

Distance config option: The campfire will work as your respawn point as long as you die within a configurable radius. Might add a chat alert to tell the player they are outside of the latest campfire radius. Revert to standard spawn point if death occurs outside the radius.

Hey!

I appreciate the suggestion! While I'd love to add all features submitted on the issue-tracker, I've got to prioritize working on them due to having limited time. In order to see which features users would like to see most, I've created https://serilum.com/mods/requests, which shows a table with all feature request submitted.

I'm aware that this is not the reaction you were looking for, but the reality is that I can't keep up with the demand. I try to do as much as I can.

Users are able to upvote requests by reacting to the first issue comment on this GitHub page with one of the 👍 😀 🎉 ❤️ 🚀 👀 emoji's. The request with the most unique reactions, will be shown at the top. You can of course add the reactions yourself too, but don't have to :). The author of the feature is already counted as +1.

I won't only focus on popular features in the upcoming years, but it does help with prioritizing. I'll probably work on a combination of popular and interesting/needed/fun submissions.

I'll close this issue with "not planned" as a way to separate an open feature request from an actual completed issue. This does not actually mean it's not planned! Incompatibilities and bug reports will still remain open.

When the feature is implemented, I'll again post a comment and close it as "completed".

Thank you for taking the time to submit the suggestion! ❤️