When using a repeat command block that is always active, entering the command /kill @e or /kill @a will result in soft-locking your own world, which can be very frustrating if you've invested a lot of time into it. My recommended solution to this is when the player spawns, they remain alive unless they input an action, like moving, turning their camera, shifting or jumping. But if they open the chat, they can execute a command to fix the command block in question. They can either teleport to it and edit it there (as long as they teleport facing the command block), or they can replace the block where the command block is with another block. This keeps the functionality of any map creators who want a player to stop playing the game if they're under a certain condition, but allows a solution to accidentally soft locking your world.
Thank you for reading!
Please sign in to leave a comment.
1 Comments