set3DENMissionAttributes: Difference between revisions
Jump to navigation
Jump to search
Lou Montana (talk | contribs) |
m (Text replacement - " it's" to " it is") |
||
| Line 9: | Line 9: | ||
| Set [[Eden_Editor:_Scenario_Atttributes|scenario attributes]]. | | Set [[Eden_Editor:_Scenario_Atttributes|scenario attributes]]. | ||
<br><br> | <br><br> | ||
An attribute is identified by its <tt>property</tt> (<tt>data</tt> when it | An attribute is identified by its <tt>property</tt> (<tt>data</tt> when it is engine-drive attribute) value in config. For the list of all attributes with their properties, see [[Eden_Editor:_Setting_Attributes#Scenario|Mission Attributes]]. | ||
{{Important|Attributes are available only within the Eden Editor workspace. You cannot access them in scenario preview or exported scenario!}} | {{Important|Attributes are available only within the Eden Editor workspace. You cannot access them in scenario preview or exported scenario!}} | ||
| Line 52: | Line 52: | ||
<dd class="note"> | <dd class="note"> | ||
Usually, the attributes value can be recieved by <code>_sectionName [[get3DENMissionAttribute]] _attributeName;//See example above</code> | Usually, the attributes value can be recieved by <code>_sectionName [[get3DENMissionAttribute]] _attributeName;//See example above</code> | ||
However, if the attribute was not changed and it | However, if the attribute was not changed and it is default value is used [[get3DENMissionAttribute]] might return [[Nothing]], even though in [[Eden Editor]] the attribute has got a value. In that case the attribute's config name is not identical to the 'property' or 'data' config value. To get the right values in these cases one has to do:<br> | ||
<code>_sectionName [[get3DENMissionAttribute]] _propertyName;</code> or | <code>_sectionName [[get3DENMissionAttribute]] _propertyName;</code> or | ||
<code>_sectionName [[get3DENMissionAttribute]] _dataName;</code> | <code>_sectionName [[get3DENMissionAttribute]] _dataName;</code> | ||
Revision as of 09:27, 8 September 2020
Description
- Description:
- Set scenario attributes.
An attribute is identified by its property (data when it is engine-drive attribute) value in config. For the list of all attributes with their properties, see Mission Attributes. - Groups:
- Uncategorised
Syntax
- Syntax:
- set3DENMissionAttributes [[<section>,<class1>,<value1>], ..., [<section >,<classN>,<valueN>]]
- Parameters:
- section: String - attribute section
- class: String - attribute name
- value: Any - new attribute value
- Return Value:
- Boolean - true if the value was set
Examples
- Example 1:
set3DENMissionAttributes [["Multiplayer","respawn",3],["Multiplayer","respawnDelay",10]];Set respawn type to 3 and respawn delay to 10 seconds
Additional Information
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
Notes
Bottom Section
- Posted on January 2, 2019 - 12:09 (UTC)
- R3vo
-
Usually, the attributes value can be recieved by
_sectionName get3DENMissionAttribute _attributeName;//See example aboveHowever, if the attribute was not changed and it is default value is used get3DENMissionAttribute might return Nothing, even though in Eden Editor the attribute has got a value. In that case the attribute's config name is not identical to the 'property' or 'data' config value. To get the right values in these cases one has to do:
_sectionName get3DENMissionAttribute _propertyName;or_sectionName get3DENMissionAttribute _dataName;