I understand that this is a feature built into the respawn anchor and as such is not a bug, however as a programmer and map creator if I might offer a suggestion: adding a lock function onto the respawn anchor would allow creators to use this block safely in adventure maps and as decorations without the fear of total catastrophe. I am currently using Java edition and there are several workarounds (like actually using it in the nether) but none are really viable in regards to the overworld. Having a lock function that prevents both the explosion from triggering and players from setting their respawn in the overworld using the respawn anchor. This would allow more flexibility with the block without undoing the original design. I was thinking about this while trying to come up with some workarounds and thought I would share. Let me know what you think and keep up all the good work you guys do!
coldtyrann000
I understand that this is a feature built into the respawn anchor and as such is not a bug, however as a programmer and map creator if I might offer a suggestion: adding a lock function onto the respawn anchor would allow creators to use this block safely in adventure maps and as decorations without the fear of total catastrophe. I am currently using Java edition and there are several workarounds (like actually using it in the nether) but none are really viable in regards to the overworld. Having a lock function that prevents both the explosion from triggering and players from setting their respawn in the overworld using the respawn anchor. This would allow more flexibility with the block without undoing the original design. I was thinking about this while trying to come up with some workarounds and thought I would share. Let me know what you think and keep up all the good work you guys do!