Difference between revisions of "hint"

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - " <dd class="notedate">" to " <dt><dt> <dd class="notedate">")
 
(67 intermediate revisions by 24 users not shown)
Line 1: Line 1:
{{Command|= Comments
+
{{RV|type=command
____________________________________________________________________________________________
 
  
| ofp |= Game name
+
| ofp
  
|1.00|= Game version
+
|1.00
  
|eff= local |= Effects in MP
+
|eff= local
____________________________________________________________________________________________
 
  
| Outputs a hint message on the left upper corner of the screen together with a clinging sound. The text may contain several lines. |= Description
+
|gr1= Interaction
____________________________________________________________________________________________
 
  
| '''hint''' text |= Syntax
+
|gr2= Structured Text
  
|p1= text: [[String]] - the message to write on the screen may consist of any characters. \n indicates a line break. |= Parameter 1
+
|gr3= Strings
  
| [[Nothing]] |= Return value
+
| Outputs a hint message to the right of the screen (left of the screen in {{ofp}}) with a sound (except in {{arma1}}). Use [[hintSilent]] for soundless hint. To split message in multiple lines either use [[Structured Text]] or <tt>\n</tt> (in lower case).
____________________________________________________________________________________________
+
 
 +
| [[hint]] message
 +
 
 +
|p1= message: [[String]] or [[Structured Text]] - the message to display.
 +
 
 +
| [[Nothing]]
 
   
 
   
|x1= <pre>hint "Press W to move forward. \nPress S to move backwards. \n\nUse the mouse to turn right or left."</pre>
+
|x1= <code>{{codecomment|// outputs the following:
 +
// Press W to move forward.
 +
// Press S to move backwards.}}
 +
[[hint]] "Press W to move forward.\nPress S to move backwards."</code>
  
outputs the following message:
+
|x2= <code>[[hint]] [[format]] ["Hello, %1!", [[name]] [[player]]];</code>
  
<pre>Press W to move forward.
+
|x3= <code>[[hint]] [[str]] [[count]] [[allPlayers]];
Press S to move backwards.
+
[[sleep]] 10;
 +
[[hintSilent]] ""; {{cc|hides the previous hint display}}</code>
  
Use the mouse to turn right or left.</pre>
+
|x4= <code>[[hint]] [[parseText]] "<t size='2.0'>Large text</t>"; {{cc|Displays text twice as large as the default one}}</code>
  
Known Problems Avoid hint messages that exceed the screen, as this may lead to crashes. |= Example 1
+
|pr= {{GVI|ofp|1.00}} {{GVI|arma1|1.00}} {{GVI|arma2|1.00}} Hint messages that exceed the screen may lead to crashes.<br>
____________________________________________________________________________________________
+
{{GVI|arma3|1.00}} The game would not crash but suffer FPS drop / temporary freezing.
 
 
| [[hintC]], [[hintCadet]] |= See also
 
  
 +
|seealso= [[hintC]], [[hintCadet]], [[hintSilent]], [[diag_log]]
 
}}
 
}}
  
<h3 style="display:none">Notes</h3>
 
 
<dl class="command_description">
 
<dl class="command_description">
<!-- Note Section BEGIN -->
+
<dt></dt>
 
+
<dd class="notedate">Posted on October 20, 2014 - 19:27 (UTC)</dd>
<!-- Note Section END -->
+
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt>
 +
<dd class="note">
 +
Be careful when using hints to visualize the effects of commands using the Debug Console. Hint can accept an undefined variable and neither the error nor the hint is shown, the command simply fails. Also notice how the hint command should be {{ic|[[hint]] [[str]] _i;}}:
 +
<code>[[for]] "_i" [[from]] 0 [[to]] 50 [[do]] {
 +
[[hint]] _i;
 +
};</code>
 +
'''tested in A3 1.32.127785'''<br>
 +
<br>
 +
In a script, an "undefined variable" error will be shown as expected.
 +
</dd>
 +
<dt><dt>
 +
<dd class="notedate">Posted on October 21, 2014 - 23:07 (UTC)</dd>
 +
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt>
 +
<dd class="note">
 +
Contrary to previous games, Arma 3 will happily display hints that far exceed screen space.<br>
 +
However, as hints get longer, FPS suffers tremendously.<br>
 +
'''tested in Debug Console, A3 1.32.127785 with the following:'''
 +
<code>[[hint]] [[str]] (([[nearestObjects]] [<nowiki/>[[player]], ["BUILDING"],  100]) - [<nowiki/>[[player]]]); [] [[spawn]] { [[sleep]] 5; [[systemChat]] [[str]] [[diag_fps]]; };
 +
[[sleep]] 10;
 +
[[hint]] [[str]] (([[nearestObjects]] [<nowiki/>[[player]], ["BUILDING"], 1000]) - [<nowiki/>[[player]]]); [] [[spawn]] { [[sleep]] 5; [[systemChat]] [[str]] [[diag_fps]]; };</code>
 +
Results were: '''59.7015''' and '''5.17297''', respectively. Drawing a hint even longer than this, such as [[nearestObjects]] with a radius of 10,000 or 100,000 reduces your FPS so much Arma 3 '''appears''' to crash, though it doesn't.<br>
 +
<br>
 +
Unrelated: Hints will stay on screen for 30 seconds, then fade away over the course of 5 seconds. '''Tested with: A3 1.32.127785'''
 +
</dd>
 +
<dt><dt>
 +
<dd class="notedate">Posted on February 17, 2015 - 23:14 (UTC)</dd>
 +
<dt class="note">[[User:DreadedEntity|DreadedEntity]]</dt>
 +
<dd class="note">
 +
An open dialog will pause the 30-second hint fade timer.
 +
'''(A3 1.38.128937)'''
 +
</dd>
 +
<dt><dt>
 +
<dd class="notedate">Posted on March 25, 2017 - 20:47 (UTC)</dd>
 +
<dt class="note">[[User:Feint|Feint]]</dt>
 +
<dd class="note">
 +
The [[hint]] sound is audible only when you have the music volume turned up above 0 in the audio settings.
 +
Otherwise, it seems to act the same as [[hintSilent]].<br>
 +
<br>
 +
This is important because if you are running a [[hint]] that fires at 30 fps or more, the [[hint]] will slow down machines that have the music volume turned up but won't slow down machines that have the music volume turned off.<br>
 +
<br>
 +
Best practice is to use [[hint]] for an alert to the player and use [[hintSilent]] for a makeshift display of data to the player that is updated fairly often.
 +
</dd>
 
</dl>
 
</dl>
  
<h3 style="display:none">Bottom Section</h3>
+
[[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands|HINT]]
+
{{GameCategory|arma1|Scripting Commands}}
[[Category:Scripting Commands OFP 1.96|HINT]]
+
{{GameCategory|arma2|Scripting Commands}}
[[Category:Scripting Commands OFP 1.46|HINT]]
+
{{GameCategory|tkoh|Scripting Commands}}
[[Category:Scripting Commands ArmA|HINT]]
+
{{GameCategory|arma3|Scripting Commands}}

Latest revision as of 01:09, 6 April 2021

Hover & click on the images for descriptions

Description

Description:
Outputs a hint message to the right of the screen (left of the screen in Operation Flashpoint) with a sound (except in Armed Assault). Use hintSilent for soundless hint. To split message in multiple lines either use Structured Text or \n (in lower case).
Problems:
Logo A0.png1.00 Logo A1 black.png1.00 Logo A2.png1.00 Hint messages that exceed the screen may lead to crashes.
Arma 3 logo black.png1.00 The game would not crash but suffer FPS drop / temporary freezing.

Syntax

Syntax:
hint message
Parameters:
message: String or Structured Text - the message to display.
Return Value:
Nothing

Examples

Example 1:
// outputs the following: // Press W to move forward. // Press S to move backwards. hint "Press W to move forward.\nPress S to move backwards."
Example 2:
hint format ["Hello, %1!", name player];
Example 3:
hint str count allPlayers; sleep 10; hintSilent ""; // hides the previous hint display
Example 4:
hint parseText "<t size='2.0'>Large text</t>"; // Displays text twice as large as the default one

Additional Information

See also:
hintChintCadethintSilentdiag_log
Groups:
InteractionStructured TextStrings

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 October 20, 2014 - 19:27 (UTC)
DreadedEntity
Be careful when using hints to visualize the effects of commands using the Debug Console. Hint can accept an undefined variable and neither the error nor the hint is shown, the command simply fails. Also notice how the hint command should be hint str _i;: for "_i" from 0 to 50 do { hint _i; }; tested in A3 1.32.127785

In a script, an "undefined variable" error will be shown as expected.
Posted on October 21, 2014 - 23:07 (UTC)
DreadedEntity
Contrary to previous games, Arma 3 will happily display hints that far exceed screen space.
However, as hints get longer, FPS suffers tremendously.
tested in Debug Console, A3 1.32.127785 with the following: hint str ((nearestObjects [player, ["BUILDING"], 100]) - [player]); [] spawn { sleep 5; systemChat str diag_fps; }; sleep 10; hint str ((nearestObjects [player, ["BUILDING"], 1000]) - [player]); [] spawn { sleep 5; systemChat str diag_fps; }; Results were: 59.7015 and 5.17297, respectively. Drawing a hint even longer than this, such as nearestObjects with a radius of 10,000 or 100,000 reduces your FPS so much Arma 3 appears to crash, though it doesn't.

Unrelated: Hints will stay on screen for 30 seconds, then fade away over the course of 5 seconds. Tested with: A3 1.32.127785
Posted on February 17, 2015 - 23:14 (UTC)
DreadedEntity
An open dialog will pause the 30-second hint fade timer. (A3 1.38.128937)
Posted on March 25, 2017 - 20:47 (UTC)
Feint
The hint sound is audible only when you have the music volume turned up above 0 in the audio settings. Otherwise, it seems to act the same as hintSilent.

This is important because if you are running a hint that fires at 30 fps or more, the hint will slow down machines that have the music volume turned up but won't slow down machines that have the music volume turned off.

Best practice is to use hint for an alert to the player and use hintSilent for a makeshift display of data to the player that is updated fairly often.