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.

All Activity

This stream auto-updates   

  1. Today
  2. Yesterday
  3. ← 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
  4. 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
  5. 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
  6. Justification of proposed code ← Older revision Revision as of 22:00, 25 April 2017 Line 2: Line 2: Why is this being global on a server a bad thing? Would it be any different if you execute it on the client, I'll try myself later, but in the meantime? Also dont say unknown version of arma, atleast say the version it was tested on for future reference. --[[User:Benargee|Benargee]] ([[User talk:Benargee|talk]]) 20:01, 4 October 2014 (CEST) Why is this being global on a server a bad thing? Would it be any different if you execute it on the client, I'll try myself later, but in the meantime? Also dont say unknown version of arma, atleast say the version it was tested on for future reference. --[[User:Benargee|Benargee]] ([[User talk:Benargee|talk]]) 20:01, 4 October 2014 (CEST) + + == [[user:OOKexOo|OOKexOo]]: Justification of proposed code in comment == + The direct use of setDate in combination with remoteExec would be the optimal solution. + However, it did't work when I executed the code with Zeus on a dedicated server. + Thus, the code I propose is a workaround which I can tell for sure that it works fine. View the full article
  7. Undo revision 99602 by Lucian (talk) ← Older revision Revision as of 18:04, 25 April 2017 (One intermediate revision by the same user not shown) (No difference) View the full article
  8. Added - tool tip window to shops and trunk menus. Added - a production multiplier to factory. Added - 26 new items that can be made at factory. Added - New WIP chat system. Fixed - AI mission system. Fixed - vehicle xfer system. Fixed - gear being deleted when using the crate option. Fixed - RP names not showing on some systems. Fixed - error with AI air taxi. changed - fixed wing aircraft trunk sizes.
  9. ADAM by Pwner Actual (RSS generated with FetchRss)View the full article
  10. (0)

    (0) (RSS generated with FetchRss)View the full article
  11. [EVO] Dan's Small Objects Mod - Oil Barrels by [evo] dan (RSS generated with FetchRss)View the full article
  12. (8)

    (8) (RSS generated with FetchRss)View the full article
  13. Last week
  14. ‎vehicle config - CfgVehicles ← Older revision Revision as of 22:03, 24 April 2017 Line 116: Line 116: class Components:Components class Components:Components { { − class TransportPylonComponent + class TransportPylonsComponent { { class pylons class pylons Line 170: Line 170: </syntaxhighlight> </syntaxhighlight> * pylons:hardpoint: if one or more matches with magazine:hardpoints then magazine can be attached, setPylonLoadOut with force = true will ignore this check. * pylons:hardpoint: if one or more matches with magazine:hardpoints then magazine can be attached, setPylonLoadOut with force = true will ignore this check. + =Scripting= =Scripting= vehicle setPylonLoadOut [pylonID, magazine name, forced = false, turret path = []] vehicle setPylonLoadOut [pylonID, magazine name, forced = false, turret path = []] View the full article
  15. note ← Older revision Revision as of 21:27, 24 April 2017 (One intermediate revision by the same user not shown) Line 48: Line 48: [[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] [[Category:Scripting Commands Arma 3|{{uc:{{PAGENAME}}}}]] [[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] [[Category:Scripting Commands|{{uc:{{PAGENAME}}}}]] + + <!-- CONTINUE Notes --> + <dl class="command_description"> + <dd class="notedate">Posted on April 24, 2017 - 21:25 (UTC)</dd> + <dt class="note">[[User:Killzone Kid|Killzone Kid]]</dt> + <dd class="note">This command used to spam .[[rpt]] when queried mod didn't exist, making it little awkward to use for testing if mod is active. For example: + <code>_superDuperModEnabled = [[modParams]] ["super_duper", ["active"]] param [0, false];</code> + Since v1.69 the command would fail silently if mod doesn't exist. + </dd> + </dl> + <!-- DISCONTINUE Notes --> View the full article
  16. Listbox in CtrlGrp note added ← Older revision Revision as of 20:30, 24 April 2017 Line 209: Line 209: | class="event" | onLBDrop | class="event" | onLBDrop | class="fired" | Drag & drop operation finished. | class="fired" | Drag & drop operation finished. − | class="notes" | Returns the control and the x and y coordinates. + | class="notes" | Returns the control and the x and y coordinates.When the Listbox is inside a ctrlGroup the eventhandler need to be added to the ctrlGroup | class="scope" | Listbox, Combobox, Textbox, ActiveText, Button | class="scope" | Listbox, Combobox, Textbox, ActiveText, Button |- |- View the full article
  17. Changed order to make it clearer. ← Older revision Revision as of 19:57, 24 April 2017 Line 24: Line 24: <br> <br> <br> <br> − Possible type names:<tt>"TREE", "SMALL TREE", "BUSH", "BUILDING", "HOUSE", "FOREST BORDER", "FOREST TRIANGLE", "FOREST SQUARE", "CHURCH", "CHAPEL", "CROSS", "ROCK", "BUNKER", "FORTRESS", "FOUNTAIN", "VIEW-TOWER", "LIGHTHOUSE", "QUAY", "FUELSTATION", "HOSPITAL", "FENCE", "WALL", "HIDE", "BUSSTOP", "ROAD", "FOREST", "TRANSMITTER", "STACK", "RUIN", "TOURISM", "WATERTOWER", "TRACK", "MAIN ROAD", "ROCKS", "POWER LINES", "RAILWAY", "POWERSOLAR", "POWERWAVE", "POWERWIND", "SHIPWRECK", "TRAIL"</tt> + Possible type names:<tt>"TREE", "SMALL TREE", "BUSH", "BUILDING", "HOUSE", "FOREST BORDER", "FOREST TRIANGLE", "FOREST SQUARE", "CHURCH", "CHAPEL", "CROSS", "BUNKER", "FORTRESS", "FOUNTAIN", "VIEW-TOWER", "LIGHTHOUSE", "QUAY", "FUELSTATION", "HOSPITAL", "FENCE", "WALL", "HIDE", "BUSSTOP", "ROAD", "FOREST", "TRANSMITTER", "STACK", "RUIN", "TOURISM", "WATERTOWER", "TRACK", "MAIN ROAD", "ROCK", "ROCKS", "POWER LINES", "RAILWAY", "POWERSOLAR", "POWERWAVE", "POWERWIND", "SHIPWRECK", "TRAIL"</tt> <br><br> <br><br> Since Arma 3 v1.61.136035 it is possible to switch the sorting algorithm off by providing optional param, which significantly increases the performance of this command, especially if the search is performed with large radius. Since Arma 3 v1.61.136035 it is possible to switch the sorting algorithm off by providing optional param, which significantly increases the performance of this command, especially if the search is performed with large radius. View the full article
  18. optimized OOKexOo code example ← Older revision Revision as of 19:45, 24 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>[[], {[[setDate]] [1986, 2, 25, 16, 0]}] [[remoteExec]] ["[[call]]",0,"JIP_id_setDate"];</code> + <code>[1986, 2, 25, 16, 0] [[remoteExecCall]] ["[[setDate]]",0,"JIP_id_setDate"];</code> </dd> </dd> </dl> </dl> <!-- DISCONTINUE Notes --> <!-- DISCONTINUE Notes --> View the full article
  19. ← Older revision Revision as of 19:38, 24 April 2017 Line 9: Line 9: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Attach type to the simple task. See [[Arma_3_Tasks_Overhaul#Default_Task_Types:_Actions]] for default task types. |= Description + | Attach type to the simple task. See [[Arma_3_Tasks_Overhaul#Default_Task_Types:_Actions|Default Task Types]]. |= Description ____________________________________________________________________________________________ ____________________________________________________________________________________________ Line 25: Line 25: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | [[taskType]], [[currentTask]], [[setSimpleTaskCustomData]], [[taskCustomData]], [[Arma_3_Tasks_Overhaul#Default_Task_Types:_Actions]] |= SEEALSO + | [[taskType]], [[currentTask]], [[setSimpleTaskCustomData]], [[taskCustomData]], [[Arma_3_Tasks_Overhaul#Default_Task_Types:_Actions|Default Task Types]] |= SEEALSO | |= MPBEHAVIOUR | |= MPBEHAVIOUR View the full article
  20. ‎STR_: new section New page == STR_ == You are partially right, $STR is indeed required for configs, anywhere else it doesn't matter. I have summarised it here: https://community.bistudio.com/wiki/Stringtable.xml#Naming_Key_IDs [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 21:09, 24 April 2017 (CEST) View the full article
  21. ‎Example Format:: added Key ID naming rules ← Older revision Revision as of 19:07, 24 April 2017 Line 5: Line 5: =====Example Format:===== =====Example Format:===== − <code><?xml version="1.0" encoding="utf-8" ?> + <syntaxhighlight lang=cpp> + <?xml version="1.0" encoding="utf-8" ?> <Project name="Any Name"> <Project name="Any Name"> <Package name="Mission One"> <Package name="Mission One"> Line 40: Line 41: </Package> </Package> </Project> </Project> − </code> + </syntaxhighlight> *Replace ''myTag'' in str_myTag_someKey with your OFPEC tag or other means of personal identification so other addon and mission string names won't collide, potentially breaking your mission - this is just good practice *Replace ''myTag'' in str_myTag_someKey with your OFPEC tag or other means of personal identification so other addon and mission string names won't collide, potentially breaking your mission - this is just good practice *Package and container names appear to only be for organizational use; use them for your own sanity *Package and container names appear to only be for organizational use; use them for your own sanity {{Important|Stringtable.xml must be saved with UTF-8 Encoding for international characters to display and save correctly}} {{Important|Stringtable.xml must be saved with UTF-8 Encoding for international characters to display and save correctly}} + + =====Naming Key IDs===== + If you are planning to use your <tt>stringtable.xml</tt> with scripts only, there are no rules in regards to naming format of Key IDs. [[localize]] and [[isLocalized]] will work with any name, as long as it matches Key ID name in <tt>stringtable.xml</tt>. For example: + + <syntaxhighlight lang=cpp> + // stringtable.xml + <?xml version="1.0" encoding="utf-8" ?> + <Project name="Any Name"> + <Package name="Mission One"> + <Container name="Some Words"> + <Key ID="myCrazyNameTag"> + <Original>wuga wuga</Original> + </Key> + </Container> + </Package> + </Project> + </syntaxhighlight> + + <code>// some script + [[hint]] [[str]] [[isLocalized]] "myCrazyNameTag"; // true; + [[hint]] [[str]] [[localize]] "myCrazyNameTag"; // "wuga wuga";</code> + + However, if you are also going to use <tt>stringtable.xml</tt> with configs, you '''must''' use special prefix <tt>$STR</tt> (dollar sign $ followed by uppercase STR) to reference Key ID in config. The Key IDs in <tt>stringtable.xml</tt> will have to start with "str" or "STR" accordingly, case doesn't matter here. For example: + + <syntaxhighlight lang=cpp> + // stringtable.xml + <?xml version="1.0" encoding="utf-8" ?> + <Project name="Any Name"> + <Package name="Mission One"> + <Container name="Some Words"> + <Key ID="STRblahblah"> + <Original>blah</Original> + </Key> + </Container> + </Package> + </Project> + </syntaxhighlight> + + <syntaxhighlight lang=cpp> + // some config + class Test + { + word = $STRblahblah; + }; + </syntaxhighlight> + <code>[[hint]] [[str]] [[getText]] ([[configFile]] >> "Test" >> "word"); // "blah"</code> + + By convention, an underscore <tt>_</tt> is added to the prefix <tt>STR_</tt> (<tt>$STR_</tt>). It provides clarity and makes <tt>stringtable.xml</tt> universally compatible with both scripts and configs. ==Usage== ==Usage== View the full article
  22. ‎ROCK vs ROCKS: new section ← Older revision Revision as of 18:13, 24 April 2017 Line 1: Line 1: I have reverted your edit for [[nearestTerrainObjects]]. Please do not change it, values are exported from the game engine [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 00:25, 22 April 2016 (CEST) I have reverted your edit for [[nearestTerrainObjects]]. Please do not change it, values are exported from the game engine [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 00:25, 22 April 2016 (CEST) + + == ROCK vs ROCKS == + + They both are filters. Please look more carefully at the list of possible names, both ROCK and ROCKS are there [[User:Killzone Kid|Killzone Kid]] ([[User talk:Killzone Kid|talk]]) 20:13, 24 April 2017 (CEST) View the full article
  23. Undo revision 99580 by ShadowRanger (talk) Warning removed as it is not helpful. ← Older revision Revision as of 18:11, 24 April 2017 Line 7: Line 7: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Checks if given object can be stored into soldier's backpack. + | Checks if given object can be stored into soldier's backpack. |= Description − <br><br> + − '''Warning:''' This command does not work as expected under unknown circumstances|= Description + ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  24. Undo revision 99579 by ShadowRanger (talk) Warning removed as it is not helpful. ← Older revision Revision as of 18:11, 24 April 2017 Line 7: Line 7: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Checks if given object can be stored in inventory of given object or any inventory container ([[uniform]], [[vest]], [[backpack]]) of given unit. + | Checks if given object can be stored in inventory of given object or any inventory container ([[uniform]], [[vest]], [[backpack]]) of given unit. |= Description − <br><br> + − '''Warning:''' This command does not work as expected under unknown circumstances|= Description + ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  25. Undo revision 99578 by ShadowRanger (talk) Warning removed as it is not helpful. ← Older revision Revision as of 18:11, 24 April 2017 Line 7: Line 7: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Checks if given object can be stored into soldier's uniform. + | Checks if given object can be stored into soldier's uniform. |= Description − <br><br> + − '''Warning:''' This command does not work as expected under unknown circumstances|= Description + ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  26. Undo revision 99577 by ShadowRanger (talk) Warning removed as it is not helpful. ← Older revision Revision as of 18:10, 24 April 2017 Line 7: Line 7: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Checks if given object can be stored into soldier's vest. + | Checks if given object can be stored into soldier's vest. |= Description − <br><br> + − '''Warning:''' This command does not work as expected under unknown circumstances|= Description + ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  27. ← Older revision Revision as of 15:59, 24 April 2017 Line 18: Line 18: With [[animateSource]] this would require only 1 (provided everything is configured correctly): With [[animateSource]] this would require only 1 (provided everything is configured correctly): <br><br> <br><br> − <tt>house [[animateSource]] ["Door_1_source", 1];</tt> + <tt>house [[animateSource]] ["Door_1_sound_source", 1];</tt> <br><br> <br><br> <syntaxhighlight lang="cpp"> <syntaxhighlight lang="cpp"> View the full article
  28. ← Older revision Revision as of 15:41, 24 April 2017 Line 13: Line 13: | Set the zoom level ('''F'''ield '''O'''f '''V'''iew) of the given camera. | Set the zoom level ('''F'''ield '''O'''f '''V'''iew) of the given camera. <br> <br> − The zoom level is from ''<tt>0.01</tt>'' for the nearest and ''<tt>2</tt>'' for the furthest zoom value, with a default zoom level of ''<tt>0.7</tt>'' + The zoom level is from ''<tt>0.01</tt>'' for the nearest and ''<tt>2</tt>'' for the furthest zoom value, with a default zoom level of ''<tt>0.75</tt>'' <br> <br> The angle of the field of view is ''<tt>atan(FOV)*2</tt>'' radians when in 4:3 aspect ratio. The angle of the field of view is ''<tt>atan(FOV)*2</tt>'' radians when in 4:3 aspect ratio. Line 28: Line 28: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − |x1= <code>_cam [[camSetFov]] 0.7;</code> |= Example 1 + |x1= <code>_cam [[camSetFov]] 0.75;</code> |= Example 1 ____________________________________________________________________________________________ ____________________________________________________________________________________________ View the full article
  1. Load more activity