BIS fnc respawnTickets: Difference between revisions
Jump to navigation
Jump to search
tickets: Number - added respawn tickets. When missing or set to 0, number of tickets won't be affected, which means you can use the function to simply get amount of tickets.
dynamicTarget: Boolean - when true, set/get tickets based on the target. target must be an Object. Return Value:
Number - remaining tickets after adjustment
m (Generated by BIS_fnc_exportFunctionsToWiki) |
(Created page with "{{Function|= Comments ____________________________________________________________________________________________ | arma3 |= Game name |0.74|= Game version |eff= global |= __...") |
||
Line 1: | Line 1: | ||
{{Function|= Comments | {{Function|= Comments | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
Line 5: | Line 4: | ||
| arma3 |= Game name | | arma3 |= Game name | ||
| | |0.74|= Game version | ||
|eff= global |= | |||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| | | Manage respawn tickets used by ''[[Arma_3_Respawn#Respawn_Templates|Tickets]]'' respawn template. | ||
When player respawns, number of tickets is decreased by 1. The most local tickets are always used. Example: When you first add tickets to player's side, they will be affected. If you later define tickets also to player's group, they will completely replace the side tickets. | |||
When player runs out of the tickets, his respawn is disabled. If you use also ''EndMission'' respawn template, the mission will automatically end once tickets in all name spaces are exhausted. | |||
|= Description | |||
____________________________________________________________________________________________ | |||
| [<target>,(<tickets>,<dynamicTarget>)] spawn BIS_fnc_respawnTickets; |= Syntax | |||
|p1= '''target''': Receiver of the respawn loadout | |||
: [[Namespace]] - use [[missionNamespace]] to set/get global tickets available for everyone | |||
: [[Side]] | |||
: [[Group]] | |||
: [[Object]]|= | |||
|p2= '''tickets''': [[Number]] - added respawn tickets. When missing or set to 0, number of tickets won't be affected, which means you can use the function to simply get amount of tickets. | |||
|p3= '''dynamicTarget''': [[Boolean]] - when [[true]], set/get tickets based on the target. '''target''' must be an [[Object]]. | |||
| | | [[Number]] - remaining tickets after adjustment |= Return value | ||
| | ____________________________________________________________________________________________ | ||
|s2= [] spawn BIS_fnc_respawnTickets; |= Syntax 2 | |||
| |= Return value | |r2= [[Number]] - remaining tickets in all name spaces |= Return value 2 | ||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
|x1= Add 5 tickets for BLUFOR | |||
<code><nowiki>[</nowiki>[[west]], 5] call BIS_fnc_respawnTickets;</code> |= | |||
| | |x2= Return number of global tickets | ||
<code><nowiki>[</nowiki>[[missionNamespace]]] call BIS_fnc_respawnTickets;</code> |= | |||
____________________________________________________________________________________________ | ____________________________________________________________________________________________ | ||
| |= See also | | [[Arma 3 Respawn]] |= See also | ||
}} | }} | ||
Line 52: | Line 54: | ||
<h3 style="display:none">Bottom Section</h3> | <h3 style="display:none">Bottom Section</h3> | ||
[[Category:Arma 3:_Functions|respawnTickets]] | |||
[[Category: |
Revision as of 07:53, 31 July 2013
Description
- Description:
- Manage respawn tickets used by Tickets respawn template. When player respawns, number of tickets is decreased by 1. The most local tickets are always used. Example: When you first add tickets to player's side, they will be affected. If you later define tickets also to player's group, they will completely replace the side tickets. When player runs out of the tickets, his respawn is disabled. If you use also EndMission respawn template, the mission will automatically end once tickets in all name spaces are exhausted.
- Execution:
- call
- Groups:
- Uncategorised
Syntax
- Syntax:
- [<target>,(<tickets>,<dynamicTarget>)] spawn BIS_fnc_respawnTickets;
- Parameters:
- target: Receiver of the respawn loadout
- Namespace - use missionNamespace to set/get global tickets available for everyone
- Side
- Group
- Object
Alternative Syntax
- Syntax:
- [] spawn BIS_fnc_respawnTickets;
- Return Value:
- Number - remaining tickets in all name spaces
Examples
- Example 1:
- Add 5 tickets for BLUFOR
[west, 5] call BIS_fnc_respawnTickets;
- Example 2:
- Return number of global tickets
[missionNamespace] call BIS_fnc_respawnTickets;
Additional Information
- See also:
- Arma 3 Respawn
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