The reverse flag seems to be used when destructing a bed so that it isn’t removed twice (since there are two bed nodes “top” and “bottom”). The actual spawn point is set/reset in beds.set_spawns() which is called just after laying down, but it affects all people who are in bed. I don’t see where it would delete a spawn point, except when destroying the bed. I think this may be what happened:
- Dug minekid’s bed (resets to world spawn)
- Place protected bed
- Sleep in protected bed (doesn’t affect spawn)
- Die (spawn at world spawn)
If minekid had slept in a diggable (not protected or with minekid on the protection block) bed prior to sleeping in the protected bed, I think things would have been different:
- Dug minekid’s bed (resets to world spawn)
- Place protected bed
- Sleep in other bed (sets spawn)
- Sleep in protected bed (doesn’t affect spawn)
- Die (spawn at other bed)