Welcome to City Life RPG

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customise your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

ArMaTeC

Administrators
  • Content count

    24,079
  • Joined

  • Last visited

Everything posted by ArMaTeC

  1. wip ← Older revision Revision as of 18:50, 27 April 2017 Line 65: Line 65: #include <iterator> #include <iterator> #include <sstream> #include <sstream> + + #define CURRENT_VERSION "1.0.0.1" extern "C" extern "C" { { + //--- Engine called on extension load + __declspec (dllexport) void __stdcall RVExtensionVersion(char *output, int outputSize); //--- STRING callExtension STRING //--- STRING callExtension STRING __declspec (dllexport) void __stdcall RVExtension(char *output, int outputSize, const char *function); __declspec (dllexport) void __stdcall RVExtension(char *output, int outputSize, const char *function); //--- STRING callExtension ARRAY //--- STRING callExtension ARRAY __declspec (dllexport) int __stdcall RVExtensionArgs(char *output, int outputSize, const char *function, const char **args, int argsCnt); __declspec (dllexport) int __stdcall RVExtensionArgs(char *output, int outputSize, const char *function, const char **args, int argsCnt); + } + + //--- Extension version information shown in .rpt file + void __stdcall RVExtensionVersion(char *output, int outputSize) + { + //--- max outputSize is 32 bytes + strncpy_s(output, outputSize, CURRENT_VERSION, _TRUNCATE); } } View the full article
  2. format ← Older revision Revision as of 17:21, 27 April 2017 Line 4: Line 4: | ofp |= Game name | ofp |= Game name |1.00|= Game version |1.00|= Game version − |arg= global |= Arguments in MP + ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Returns the position of a given marker. [x,y,z] + | Returns the position of a given marker in format [x,y,0]. Array element 3 (height above ground) is always zero. If a non-existing marker is referenced the values returned are [0,0,0].|= Description − + − Argument 3 (height above ground) is always zero. + − + − If a non-existing marker is referenced the values returned are [0,0,0]. + − |= Description + ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | [[Array]] <nowiki>=</nowiki> '''getMarkerPos''' markerName |= Syntax + | '''getMarkerPos''' markerName |= Syntax |p1= markerName: [[String]] |= Parameter 1 |p1= markerName: [[String]] |= Parameter 1 − | [[Array]] - (format [[Position3D]]) |= Return value + | [[Array]] - position in format [x,y,0] |= Return value ____________________________________________________________________________________________ ____________________________________________________________________________________________ − |x1= <pre>"MarkerOne" setMarkerPos [200,100] + |x1= <code>"MarkerOne" [[setMarkerPos]] [200,100]; − + _pos = [[getMarkerPos]] "MarkerOne"</code> − _pos = getMarkerPos "MarkerOne"</pre> + − returns [200,100,0] |= Example 1 + _pos is [200,100,0] |= Example 1 ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  3. ‎EntityKilled: detecting road kills ← Older revision Revision as of 15:35, 27 April 2017 (2 intermediate revisions by the same user not shown) Line 50: Line 50: ==== Loaded ==== ==== Loaded ==== | <!-- Description --> | <!-- Description --> − Triggered when mission is loaded from save. + Triggered when mission is loaded from save. <br> + '''NOTE''': "Loaded" event handler should be added <u>BEFORE</u> the mission is loaded from save. Placing it in a [[Functions_Library_(Arma_3)|function]] with preInit = 1; usually does the trick. | <!-- Arguments --> | <!-- Arguments --> * saveType: [[String]] - save type, can be have following values: * saveType: [[String]] - save type, can be have following values: Line 61: Line 62: |- |- | <!-- Title --> | <!-- Title --> + ==== Map ==== ==== Map ==== | <!-- Description --> | <!-- Description --> Line 99: Line 101: ==== EntityKilled ==== ==== EntityKilled ==== | <!-- Description --> | <!-- Description --> − Triggered when an entity is killed. + Triggered when an entity is killed. Worth noting that ''instigator'' param is [[objNull]] during road kill. To work around this issue try: + <code>[[addMissionEventHandler]] ["EntityKilled", + { + [[params]] ["_killed", "_killer", "_instigator"]; + [[if]] ([[isNull]] _instigator) [[then]] {_instigator = [[UAVControl]] [[vehicle]] _killer [[select]] 0}; // UAV/UGV player operated road kill + [[if]] ([[isNull]] _instigator) [[then]] {_instigator = _killer}; // player driven vehicle road kill + [[hint]] [[format]] ["Killed By %1", [[name]] _instigator]; + }];</code> | <!-- Arguments --> | <!-- Arguments --> * killed: [[Object]] - entity that was killed * killed: [[Object]] - entity that was killed View the full article
  4. ‎Loaded ← Older revision Revision as of 14:33, 27 April 2017 (One intermediate revision by the same user not shown) Line 50: Line 50: ==== Loaded ==== ==== Loaded ==== | <!-- Description --> | <!-- Description --> − Triggered when mission is loaded from save. + Triggered when mission is loaded from save. <br> + '''NOTE''': "Loaded" event handler should be added <u>BEFORE</u> the mission is loaded from save. Placing it in a [[Functions_Library_(Arma_3)|function]] with preInit = 1; usually does the trick. | <!-- Arguments --> | <!-- Arguments --> * saveType: [[String]] - save type, can be have following values: * saveType: [[String]] - save type, can be have following values: Line 61: Line 62: |- |- | <!-- Title --> | <!-- Title --> + ==== Map ==== ==== Map ==== | <!-- Description --> | <!-- Description --> View the full article
  5. ‎Loaded: add in preinit ← Older revision Revision as of 14:32, 27 April 2017 Line 50: Line 50: ==== Loaded ==== ==== Loaded ==== | <!-- Description --> | <!-- Description --> − Triggered when mission is loaded from save. + Triggered when mission is loaded from save. <br> + '''NOTE''' this event handler has to be added BEFORE the mission is loaded from save. Placing it in a [[Functions_Library_(Arma_3)|function]] with preInit = 1; usually does the trick. | <!-- Arguments --> | <!-- Arguments --> * saveType: [[String]] - save type, can be have following values: * saveType: [[String]] - save type, can be have following values: Line 61: Line 62: |- |- | <!-- Title --> | <!-- Title --> + ==== Map ==== ==== Map ==== | <!-- Description --> | <!-- Description --> View the full article
  6. (29) (RSS generated with FetchRss)View the full article
  7. VeteranMod by VTN Team (RSS generated with FetchRss)View the full article
  8. (0)

    (0) (RSS generated with FetchRss)View the full article
  9. Wyatt's grenade script by wyattwic (RSS generated with FetchRss)View the full article
  10. Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code Code 

    1. DeathWatchPaul

      DeathWatchPaul

      boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies boobies

  11. ‎Magazine and weapon ← Older revision Revision as of 22:28, 26 April 2017 Line 45: Line 45: model = "\A3\Weapons_F\DynamicLoadout\PylonPod_1x_Missile_AGM_02_F.p3d"; model = "\A3\Weapons_F\DynamicLoadout\PylonPod_1x_Missile_AGM_02_F.p3d"; count = 1; count = 1; − hardpoint[] = {"SUU_63_PYLON","BRU_32_EJECTOR","US_BOMB"}; + hardpoints[] = {"SUU_63_PYLON","BRU_32_EJECTOR","US_BOMB"}; pylonWeapon = "Missile_AGM_02_Plane_CAS_01_F"; pylonWeapon = "Missile_AGM_02_Plane_CAS_01_F"; }; }; View the full article
  12. ← Older revision Revision as of 21:43, 26 April 2017 Line 7: Line 7: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Get array with unit connected to vehicle and position in that vehicle. |= Description + | Returns array with current operator of UAV and his vehicle role in UAV. |= Description ____________________________________________________________________________________________ ____________________________________________________________________________________________ Line 14: Line 14: |p1= uav: [[Object]] |= Parameter 1 |p1= uav: [[Object]] |= Parameter 1 − | [[Array]] - in format: [unit_object,position_string]|= RETURNVALUE + | [[Array]] - in format [unit, vehicleRole], where: + * unit: [[Object]] - UAV operator + * vehicleRole: [[String]] - vehicle role of the operator in UAV, for example: "DRIVER" or "GUNNER" |= RETURNVALUE ____________________________________________________________________________________________ ____________________________________________________________________________________________ − |x1= <code></code>|= EXAMPLE1 + |x1= <code>[[UAVControl]] uav;</code>|= EXAMPLE1 ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  13. ← Older revision Revision as of 20:52, 26 April 2017 (One intermediate revision by the same user not shown) Line 23: Line 23: |p2= minDist (Optional): [[Number]] - minimum distance from the center position. Default: 0|= Parameter 1 |p2= minDist (Optional): [[Number]] - minimum distance from the center position. Default: 0|= Parameter 1 |p3= maxDist (Optional): [[Number]] - maximum distance from the center position. If -1, the world's "safePositionRadius" entry will be used. Default: -1|= Parameter 1 |p3= maxDist (Optional): [[Number]] - maximum distance from the center position. If -1, the world's "safePositionRadius" entry will be used. Default: -1|= Parameter 1 − |p4= objDist (Optional): [[Number]] - minimum distance from the resulting position to the center of nearest object. Default: 0|= Parameter 1 + |p4= objDist (Optional): [[Number]] - minimum distance from the resulting position to the center of nearest object. Specifying quite large distance here will slow the function and might often fail to find suitable position. Recommended value: 0 - 10. Default: 0|= Parameter 1 |p5= waterMode (Optional): [[Number]] - water mode. Could be one of: |p5= waterMode (Optional): [[Number]] - water mode. Could be one of: * 0 - cannot be in water (Default: 0) * 0 - cannot be in water (Default: 0) * 1 - can either be in water or not * 1 - can either be in water or not * 2 - must be in water|= Parameter 1 * 2 - must be in water|= Parameter 1 − |p6= maxGrad (Optional): [[Number]] - maximum terrain gradient (hill steepness). Default: 0 |= Parameter 1 + |p6= maxGrad (Optional): [[Number]] - maximum terrain gradient (hill steepness). A quite small non-zero value could result in failure to find suitable position. Recommended: 0.1+ Default: 0 |= Parameter 1 |p7= shoreMode (Optional): [[Number]] - shore mode. Could be one of: |p7= shoreMode (Optional): [[Number]] - shore mode. Could be one of: * 0 - does not have to be at a shore (Default: 0) * 0 - does not have to be at a shore (Default: 0) * 1 - must be at a shore|= Parameter 1 * 1 - must be at a shore|= Parameter 1 − |p8= blacklistPos (Optional): blacklisted area. Could be one of: + |p8= blacklistPos (Optional): List of blacklisted areas in format [area1, area2, area3... areaN] (Default: []). Area could be one of: − * [[Array]] - in format [topLeftCorner, bottomRightCorner] (Default: []) - top and bottom coordinates of blacklisted area + * [[Array]] - in format [topLeftCorner, bottomRightCorner] - top and bottom coordinates of blacklisted area * [[Object]] - trigger area * [[Object]] - trigger area * [[String]] - marker area * [[String]] - marker area View the full article
  14. some recommended values ← Older revision Revision as of 20:34, 26 April 2017 Line 23: Line 23: |p2= minDist (Optional): [[Number]] - minimum distance from the center position. Default: 0|= Parameter 1 |p2= minDist (Optional): [[Number]] - minimum distance from the center position. Default: 0|= Parameter 1 |p3= maxDist (Optional): [[Number]] - maximum distance from the center position. If -1, the world's "safePositionRadius" entry will be used. Default: -1|= Parameter 1 |p3= maxDist (Optional): [[Number]] - maximum distance from the center position. If -1, the world's "safePositionRadius" entry will be used. Default: -1|= Parameter 1 − |p4= objDist (Optional): [[Number]] - minimum distance from the resulting position to the center of nearest object. Default: 0|= Parameter 1 + |p4= objDist (Optional): [[Number]] - minimum distance from the resulting position to the center of nearest object. Specifying quite large distance here will slow the function and might often fail to find suitable position. Recommended value: 0 - 10. Default: 0|= Parameter 1 |p5= waterMode (Optional): [[Number]] - water mode. Could be one of: |p5= waterMode (Optional): [[Number]] - water mode. Could be one of: * 0 - cannot be in water (Default: 0) * 0 - cannot be in water (Default: 0) * 1 - can either be in water or not * 1 - can either be in water or not * 2 - must be in water|= Parameter 1 * 2 - must be in water|= Parameter 1 − |p6= maxGrad (Optional): [[Number]] - maximum terrain gradient (hill steepness). Default: 0 |= Parameter 1 + |p6= maxGrad (Optional): [[Number]] - maximum terrain gradient (hill steepness). A quite small non-zero value could result in failure to find suitable position. Recommended: 0.1+ Default: 0 |= Parameter 1 |p7= shoreMode (Optional): [[Number]] - shore mode. Could be one of: |p7= shoreMode (Optional): [[Number]] - shore mode. Could be one of: * 0 - does not have to be at a shore (Default: 0) * 0 - does not have to be at a shore (Default: 0) View the full article
  15. Created page with "EUTW Developer Wiki contributions: https://community.bistudio.com/wiki/Special:Contributions/Gippo" New page EUTW Developer Wiki contributions: https://community.bistudio.com/wiki/Special:Contributions/Gippo View the full article
  16. ← Older revision Revision as of 20:03, 26 April 2017 Line 70: Line 70: <dd class="note"> <dd class="note"> This command returns always true if the falling object is attached to some other object with the command attachTo, like for vehicle air drop with parachute. This command returns always true if the falling object is attached to some other object with the command attachTo, like for vehicle air drop with parachute. + </dd> + </dl> + <!-- DISCONTINUE Notes --> + + <!-- CONTINUE Notes --> + <dl class="command_description"> + <dd class="notedate">Posted on April 26, 2017 - 20:02 (UTC)</dd> + <dt class="note">[[User:Gippo|Gippo]]</dt> + <dd class="note"> + Be aware: it's not reliable on remote objects. </dd> </dd> </dl> </dl> <!-- DISCONTINUE Notes --> <!-- DISCONTINUE Notes --> View the full article
  17. ← Older revision Revision as of 19:24, 26 April 2017 Line 28: Line 28: { { type = rotation; type = rotation; − source = Door_1_source; + source = Door_1_sound_source; selection = Door_1; selection = Door_1; axis = Door_1_axis; axis = Door_1_axis; Line 40: Line 40: { { type = rotation; type = rotation; − source = Door_1_source; + source = Door_1_noSound_source; selection = Door_Handle_1; selection = Door_Handle_1; axis = Door_Handle_1_axis; axis = Door_Handle_1_axis; View the full article
  18. User account SimZor was created by Dwarden and password was sent by email View the full article
  19. ← Older revision Revision as of 13:31, 26 April 2017 Line 56: Line 56: class AnimationSources class AnimationSources { { − class Door_1_source + class Door_1_sound_source − { + { − source = "user"; + source = "user"; − animPeriod = 2; + initPhase = 0; − initPhase = 0; + animPeriod = 1; − }; + sound = "GenericDoorsSound"; + soundPosition = "Door_1_trigger"; + }; }; }; ...</syntaxhighlight> ...</syntaxhighlight> View the full article
  20. (0)

    (0) (RSS generated with FetchRss)View the full article
  21. LYTHIUM by Green_Beret ©FFAAMOD (RSS generated with FetchRss)View the full article
  22. AttachTo Finder by 7erra (RSS generated with FetchRss)View the full article
  23. ← Older revision Revision as of 23:01, 25 April 2017 (3 intermediate revisions by the same user not shown) Line 7: Line 7: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Returns a list of nearest objects of the given types to the given position or object, within the specified distance. If more than one object is found they will be ordered according to [[distance2D]] to the object (i.e. the closest one will be first in the array). Alternatively, you use [[nearObjects]] command, which doesn't sort results. <br><br> + | Returns a list of nearest objects of the given types to the given position or object, within the specified distance. If more than one object is found they will be ordered by proximity, the closest one will be first in the array. Alternatively, you use [[nearObjects]] command, which doesn't sort results. <br><br> ''position'' can use the format: ''position'' can use the format: Line 29: Line 29: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − |'''nearestObjects''' [position, types, radius, 3Dmode] + |'''nearestObjects''' [position, types, radius, 2Dmode] − |p1= [position, types, radius, 3Dmode]: [[Array]] |=Parameter 1 + |p1= [position, types, radius, 2Dmode]: [[Array]] |=Parameter 1 |p2= position: [[Object]] or [[Array]] in format [[PositionAGL]] or [[Position2D]] - where to find objects, center position. |=Parameter 2 |p2= position: [[Object]] or [[Array]] in format [[PositionAGL]] or [[Position2D]] - where to find objects, center position. |=Parameter 2 |p3= types: [[Array]] - list of class name of the objects to search for. |=Parameter 3 |p3= types: [[Array]] - list of class name of the objects to search for. |=Parameter 3 |p4= radius: [[Number]] - range from center position to search for objects. |=Parameter 4 |p4= radius: [[Number]] - range from center position to search for objects. |=Parameter 4 − |p5= 3Dmode (Optional): [[Boolean]] - The object search and sorting mode: [[false]] - 3D, [[true]] - 2D. Default: [[false]] - 3D (''Available since Arma 3 v1.65.138818'') |=Parameter 5 + |p5= 2Dmode (Optional): [[Boolean]] - The object search and sorting mode: [[true]] - 2D, [[false]] - 3D. Default: [[false]] - 3D (''Available since Arma 3 v1.65.138818'') |=Parameter 5 − | [[Array]] - array of objects sorted according to [[distance2D]] |= Return value + | [[Array]] - array of objects |= Return value ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  24. values of 4th argument were mixed up ← Older revision Revision as of 22:09, 25 April 2017 Line 35: Line 35: |p3= types: [[Array]] - list of class name of the objects to search for. |=Parameter 3 |p3= types: [[Array]] - list of class name of the objects to search for. |=Parameter 3 |p4= radius: [[Number]] - range from center position to search for objects. |=Parameter 4 |p4= radius: [[Number]] - range from center position to search for objects. |=Parameter 4 − |p5= 3Dmode (Optional): [[Boolean]] - The object search and sorting mode: [[true]] - 3D, [[false]] - 2D. Default: [[true]] - 3D (''Available since Arma 3 v1.65.138818'') |=Parameter 5 + |p5= 3Dmode (Optional): [[Boolean]] - The object search and sorting mode: [[false]] - 3D, [[true]] - 2D. Default: [[false]] - 3D (''Available since Arma 3 v1.65.138818'') |=Parameter 5 | [[Array]] - array of objects sorted according to [[distance2D]] |= Return value | [[Array]] - array of objects sorted according to [[distance2D]] |= Return value View the full article
  25. Undo revision 99596 by Will (talk) see discussion ← Older revision Revision as of 22:02, 25 April 2017 Line 96: Line 96: <dd class="note"> <dd class="note"> Regarding execution in the middle of a session, the post of [[User:MulleDK13|MulleDK13]] is not entirely true. If you don't change the year, you are perfectly fine when executing the command on the server only. However, the server does not sync the year. Hence, if you do change the year, you have to execute the command on the server, clients and JIP to account for the missing sync. e.g.<br> Regarding execution in the middle of a session, the post of [[User:MulleDK13|MulleDK13]] is not entirely true. If you don't change the year, you are perfectly fine when executing the command on the server only. However, the server does not sync the year. Hence, if you do change the year, you have to execute the command on the server, clients and JIP to account for the missing sync. e.g.<br> − <code>[1986, 2, 25, 16, 0] [[remoteExecCall]] ["[[setDate]]",0,"JIP_id_setDate"];</code> + <code>[[], {[[setDate]] [1986, 2, 25, 16, 0]}] [[remoteExec]] ["[[call]]",0,"JIP_id_setDate"];</code> </dd> </dd> </dl> </dl> <!-- DISCONTINUE Notes --> <!-- DISCONTINUE Notes --> View the full article