Delay in Disabling Player Movement and Camera Control Using Input Permission Commands

There is a noticeable delay when using the following commands to disable player movement or camera control :

inputpermission set @a movement disabled

inputpermission set @a camera disabled

 

After executing the commands, players are still able to perform limited actions, such as jumping, sneaking, or moving the camera for a short time before the controls are fully disabled. This delay can disrupt gameplay mechanics that rely on immediate control restrictions.

 

 Reproduction Steps:

1. Place a command block in the world

2. Set the command block to execute the following command:

inputpermission set @a movement disabled (or inputpermission set @a camera disabled for camera testing).

3. Place a button next to the command block.

4. Press the button to activate the command.

5. Immediately after pressing the button, attempt to:

Jump or press the sneak button (for movement testing).

Move the screen quickly (for camera control testing).

 

Observed Results:

after pressing the button, there is a delay before the player's movement is fully disabled. During this delay, the player can still jump, sneak, or make minor movements.

 

Similarly, when disabling camera control, there is a short period where the player can still move the camera before the control is completely disabled.

 

Expected Results:

Player movement and camera control should be disabled immediately upon executing the respective commands, with no delay allowing further actions.

 

Note :

You need to perform an action (e.g., jump or move the screen) quickly after activating the command, as the control is disabled after approximately 0.1 to 0.25 seconds