disableUserInput: Difference between revisions

Latest revision as of 16:35, 13 April 2025

1.00

Hover & click on the images for description

Description

Description:: Disables or enables the keyboard and mouse input. Usually used during cutscenes.
⚠
Be careful and responsible with the usage of this command. Once the user input is disabled, the only option left is to restart the game. Make sure you provide scripted mechanics to resolve this, should you need to disable user input for any reason.
Groups:: Interaction

Syntax

Syntax:: disableUserInput state
Parameters:: state: Boolean - true to disable, false to enable
Return Value:: Nothing

Examples

Example 1:: disableUserInput true; // cutscene disableUserInput false;
Example 2:: Reset user input if a key was pressed:
disableUserInput true; // here e.g W was pressed sleep 2; // the user releases keys disableUserInput false; // the game considers W is still pressed as it did not listen to a "KeyUp" event disableUserInput true; disableUserInput false; // this resets released keys making the issue invisible // this workaround does not fix the mouse input that may get stuck on disableUserInput call

Additional Information

See also:: userInputDisabled enableSimulation enableSimulationGlobal

Notes

: Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note

@@ Line 34: / Line 34: @@
 |r1= [[Nothing]]
-|x1= <sqf>disableUserInput true;
+|x1= <sqf>
+disableUserInput true;
 // cutscene
-disableUserInput false;</sqf>
+disableUserInput false;
+</sqf>
+|x2= Reset user input if a key was pressed:
+<sqf>
+disableUserInput true;	// here e.g W was pressed
+sleep 2;				// the user releases keys
+disableUserInput false;	// the game considers W is still pressed as it did not listen to a "KeyUp" event
+disableUserInput true;
+disableUserInput false;	// this resets released keys making the issue invisible
+// this workaround does not fix the mouse input that may get stuck on [[disableUserInput]] call
+</sqf>
 |seealso= [[userInputDisabled]] [[enableSimulation]] [[enableSimulationGlobal]]
 }}
-<dl class="command_description">
-<dt></dt>
-<dd class="notedate">Posted on 14 March 2014</dd>
-<dt class="note">[[User:Killzone_Kid|Killzone_Kid]]</dt>
-<dd class="note">
-Sometimes, when [[disableUserInput]] [[true]] command is invoked while the user is holding a button, when [[disableUserInput]] [[false]] is called and the user is no longer holding the button, the input will resume as if the user is still holding the button. To reset this behaviour, disable and enable user input again in the same frame:
-<sqf>disableUserInput true;
-//do something
-disableUserInput false;
-disableUserInput true;
-disableUserInput false;</sqf>
-Unfortunately, if the user is moving mouse when [[disableUserInput]] [[true]] command is invoked, the mouse input will get stuck for the whole duration of disabled user input but will reset as soon as [[disableUserInput]] [[false]] is called. I was unable to find workaround for this one.
-<br><br>
-UPDATE: There is now [[userInputDisabled]] command, which allows one to check if user input is still disabled after enabling it, so that one can retry until enabling is successful.
-</dl>