addAction: Difference between revisions
Jump to navigation
Jump to search
m (Text replacement - "{{Inline code|" to "{{ic|") |
Lou Montana (talk | contribs) |
||
Line 29: | Line 29: | ||
<dt>script:</dt> | <dt>script:</dt> | ||
<dd>[[String]] or [[Code]] - Either path to the script file, relative to the mission folder or string with code or the actual script code. If the string is a path to script file, the script file '''must''' have extension .[[SQS]] or .[[SQF]]. The script, whether it is a file or a code, will run in [[Scheduler#Scheduled Environment|scheduled environment]], i.e. it is ok to use [[sleep]]. | <dd>[[String]] or [[Code]] - Either path to the script file, relative to the mission folder or string with code or the actual script code. If the string is a path to script file, the script file '''must''' have extension .[[SQS]] or .[[SQF Syntax|SQF]]. The script, whether it is a file or a code, will run in [[Scheduler#Scheduled Environment|scheduled environment]], i.e. it is ok to use [[sleep]]. | ||
<br> | <br> | ||
Parameters array passed to the script upon activation in ''[[Magic Variables#this|_this]]'' variable is: | Parameters array passed to the script upon activation in ''[[Magic Variables#this|_this]]'' variable is: |
Revision as of 22:58, 24 March 2021
Description
- Description:
- Description needed
- Groups:
- Interaction
Syntax
- Syntax:
- Syntax needed
- Parameters:
- object:
- Object - unit, vehicle or static object
- title:
- String - The action name which is displayed in the action menu, may contain Structured Text. Because of that < and > symbols will be interpreted as opening and closing XML tags. To avoid this use < for < and > for >. The title text can be changed with setUserActionText
- script:
- String or Code - Either path to the script file, relative to the mission folder or string with code or the actual script code. If the string is a path to script file, the script file must have extension .SQS or .SQF. The script, whether it is a file or a code, will run in scheduled environment, i.e. it is ok to use sleep.
Parameters array passed to the script upon activation in _this variable is:params ["_target", "_caller", "_actionId", "_arguments"];
- target (_this select 0): Object - the object which the action is assigned to
- caller (_this select 1): Object - the unit that activated the action
- actionId (_this select 2): Number - activated action's ID (same as addAction's return value)
- arguments (_this select 3): Anything - arguments given to the script if you are using the extended syntax
- arguments:
- Anything - (Optional, default nil) arguments to pass to the script (will be _this select 3 inside the script). If Array is used as an argument for example, its first element reference would be
_this select 3 select 0
- priority:
- Number - (Optional, default 1.5) priority value of the action. Actions will be arranged in descending order according to this value. Every game action has a preset priority value. Value can be negative or decimal fraction. Actions with same values will be arranged in order which they were made, newest at the bottom. The bigger the number the higher the action will be positioned on the menu. Typical range is 0 (low priority. Eg: 'Get out') to 6 (high priority. Eg: 'Auto-hover on')
- showWindow:
- Boolean - (Optional, default true) if set to true, players see "Titletext" at mid-lower screen, as they approach the object. Only the title text for the action with highest priority and 'showWindow true' will be shown. Setting it to false disables the feature
- hideOnUse:
- Boolean - (Optional, default true) if set to true, it will hide the action menu after selecting that action. If set to false, it will leave the action menu open and visible after selecting that action, leaving the same action highlighted, for the purpose of allowing you to reselect that same action quickly, or to select another action
- shortcut:
- String - (Optional, default "") one of the key names defined in bin.pbo (e.g. "moveForward"). Adding available shortcut will bind corresponding keyboard key to this action. Shortcut availability can be tested with inputAction command
- condition:
- String - (Optional, default "true") script code that must return true for the action to be shown. Special variables passed to the script code are:
- _target: Object - the object to which action is attached or, if the object is a unit inside of vehicle, the vehicle
- _this: Object - caller person to whom the action is shown (or not shown if condition returns false)
- _originalTarget: Object - the original object to which the action is attached, regardless if the object/unit is in a vehicle or not
- radius:
- Number - (Optional, default 50) maximum 3D distance in meters between the activating unit's eyePos and the object's memoryPoint, selection or position. -1 disables the radius
Template:Since - unconscious:
- Boolean - (Optional, default false) if true will be shown to incapacitated player (see setUnconscious, lifeState)
Template:Since - selection:
- String - (Optional, default "") object Geometry LOD's named selection
Template:Since - memoryPoint:
- String - (Optional, default "") object's memory point. If selection is supplied, memoryPoint is not used
Template:Since
- Return Value:
- Return value needed
Examples
- Example 1:
// short and sweet player addAction ["a useless action that does nothing", {}]; player addAction ["<t color='#FF0000'>This Useless Action Is RED</t>", {hint "RED"}]; player addAction ["Hint Hello!", { hint format ["Hello %1!", name player] }]; player addAction ["String Exec", "hint 'this is also compiled'"];
- Example 2:
_actionID = player addAction ["Exec the file", "scriptFile.sqf"]
scriptFile.sqf:hint str _this;
- Example 3:
// create object on the server and add action to the object on every client if (isServer) then { private _object = "some_obj_class" createVehicle [1234, 1234, 0]; [_object, ["Greetings!", { hint "Hello!"; }]] remoteExec ["addAction"]; // Note: does not return action id };
- Example 4:
- Default parameters:
this addAction [ "title", { params ["_target", "_caller", "_actionId", "_arguments"]; }, nil, 1.5, true, true, "", "true", // _target, _this, _originalTarget 50, false, "", "" ];
- Example 5:
- Default parameters with comments:
this addAction [ "title", // title { params ["_target", "_caller", "_actionId", "_arguments"]; // script }, nil, // arguments 1.5, // priority true, // showWindow true, // hideOnUse "", // shortcut "true", // condition 50, // radius false, // unconscious "", // selection "" // memoryPoint ];
Additional Information
- See also:
- See also needed
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
- Posted on May 02, 2018 - 13:44 (UTC)
- Dedmen
-
If you want to replicate vanilla Actions like "Treat yourself" where the scroll menu only shows text and it displays the icon mid-screen you can use
private _action = player addAction ["Heal", {}]; player setUserActionText [_action , "Heal", "<img size='2' image='\a3\ui_f\data\IGUI\Cfg\Actions\heal_ca'/>"];
- Posted on May 12, 2020 - 10:42 (UTC)
- PierreMGI
- addAction on unit or player stays on corpse after kill. So this action is lost for the new body after respawn. If you want a persistent addAction, you need to add it in the respawn script (onPlayerRespawn.sqf or addMissionEventHandler "entityRespawned" or addMPEventHandler "MPrespawn"... You can use removeAllActions on corpse.