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

    23,962
  • Joined

  • Last visited

Community Reputation

4,397 Reputable Resident

About ArMaTeC

  • Rank
    Head Programmer
  • Birthday 30/06/83

Contact Methods

  • AIM
    karllawrence2002
  • MSN
    [email protected]
  • Website URL
    http://cityliferpg.com
  • ICQ
    702479548
  • Yahoo
    karllawrence2002
  • Skype
    armatec2
  • Steam ID
    76561198011018463

Profile Information

  • Gender
    Male
  • Location
    Tanoa
  • Interests
    Im a keen coder and have put my life on hold so i can create the next gen of RPG's

Home address

  • Country
    United Kingdom

Recent Profile Visitors

54,290 profile views
  1. ‎getVehicleCargo ← Older revision Revision as of 23:29, 23 April 2017 (2 intermediate revisions by the same user not shown) Line 8: Line 8: == Scripting commands== == Scripting commands== − ==== [[setVehicleCargo]] ==== − Load cargo vehicle inside vehicle if possible, returns bool based on whether the vehicle was able to be loaded ==== [[enableVehicleCargo]] ==== ==== [[enableVehicleCargo]] ==== − Enable/disable option to transport other vehicles (if configured) or be transported. + Enable/disable option to transport other vehicles (if configured) or be transported. + ==== [[vehicleCargoEnabled]] ==== + Check if the vehicle has enabled transporting other vehicles or not. + ==== [[isVehicleCargo]] ==== ==== [[isVehicleCargo]] ==== Return transporting vehicle if vehicle is loaded in one. Return transporting vehicle if vehicle is loaded in one. Line 17: Line 18: Returns bool array if it is possible to load cargo inside vehicle and if possible to load cargo into empty vehicle Returns bool array if it is possible to load cargo inside vehicle and if possible to load cargo into empty vehicle ==== [[getVehicleCargo]] ==== ==== [[getVehicleCargo]] ==== − Gets a list of vehicles loaded as cargo inside this vehicle. The returned array is in the order the cargo vehicles were added to containing vehicle. + Gets a list of vehicles loaded as cargo inside this vehicle. The returned array is in the order the cargo vehicles were added to containing vehicle. + ==== [[setVehicleCargo]] ==== + Load cargo vehicle inside vehicle if possible, returns bool based on whether the vehicle was able to be loaded ==Transport/transported vehicles and parameters == ==Transport/transported vehicles and parameters == View the full article
  2. Remove duplicate setVehicleCargo ← Older revision Revision as of 19:51, 23 April 2017 Line 18: Line 18: ==== [[getVehicleCargo]] ==== ==== [[getVehicleCargo]] ==== Gets a list of vehicles loaded as cargo inside this vehicle. The returned array is in the order the cargo vehicles were added to containing vehicle. Gets a list of vehicles loaded as cargo inside this vehicle. The returned array is in the order the cargo vehicles were added to containing vehicle. − ==== [[setVehicleCargo]] ==== − Load cargo vehicle inside vehicle if possible, returns bool based on whether the vehicle was able to be loaded ==Transport/transported vehicles and parameters == ==Transport/transported vehicles and parameters == View the full article
  3. doubl typo ← Older revision Revision as of 16:13, 23 April 2017 Line 590: Line 590: magazineGroup[] = {"test_mag_group"}; /// all magazines in the same group may be used in weapon that has the group defined as compatible magazineGroup[] = {"test_mag_group"}; /// all magazines in the same group may be used in weapon that has the group defined as compatible }; }; − class 30Rnd_test_mag_Tracer: 30Rnd_test_mag {}; /// this magazine inherits the group and is useable in the test weapon + class 30Rnd_test_mag_Tracer: 30Rnd_test_mag {}; /// this magazine inherits the group and is usable in the test weapon }; }; View the full article
  4. ‎Magazine compatibility groups: typo ← Older revision Revision as of 14:28, 23 April 2017 Line 580: Line 580: class Test_weapon_01_Base_F: Rifle_Base_F class Test_weapon_01_Base_F: Rifle_Base_F { { − magazines[] = {"30Rnd_test_mag", "MyMagGroup"}; /// original custom made magazines and a group of several standardized mags + magazines[] = {"30Rnd_test_mag", "test_mag_group"}; /// original custom made magazines and a group of several standardized mags }; }; }; }; Line 590: Line 590: magazineGroup[] = {"test_mag_group"}; /// all magazines in the same group may be used in weapon that has the group defined as compatible magazineGroup[] = {"test_mag_group"}; /// all magazines in the same group may be used in weapon that has the group defined as compatible }; }; − class 30Rnd_test_mag_Tracer: 30Rnd_test_mag {}; /// this magazine ingerits the group and is use-able in the test weapon + class 30Rnd_test_mag_Tracer: 30Rnd_test_mag {}; /// this magazine inherits the group and is useable in the test weapon }; }; View the full article
  5. ← Older revision Revision as of 03:24, 23 April 2017 (4 intermediate revisions by the same user not shown) Line 86: Line 86: Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. [http://feedback.arma3.com/view.php?id=22583 Feedback_Link] [http://feedback.arma3.com/view.php?id=22583 Feedback_Link] + </dd> + </dl> + <!-- DISCONTINUE Notes --> + + <!-- CONTINUE Notes --> + <dl class="command_description"> + <dd class="notedate">Posted on April 23, 2017 - 02:58 (UTC)</dd> + <dt class="note">[[User:OOKexOo|OOKexOo]]</dt> + <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> + <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. ← Older revision Revision as of 03:03, 23 April 2017 (One intermediate revision by the same user not shown) Line 86: Line 86: Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. [http://feedback.arma3.com/view.php?id=22583 Feedback_Link] [http://feedback.arma3.com/view.php?id=22583 Feedback_Link] + </dd> + </dl> + <!-- DISCONTINUE Notes --> + + <!-- CONTINUE Notes --> + <dl class="command_description"> + <dd class="notedate">Posted on April 23, 2017 - 02:58 (UTC)</dd> + <dt class="note">[[User:OOKexOo|OOKexOo]]</dt> + <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:<br> + <code>[1986, 2, 25, 16, 0] [[remoteExec]] ["[[setDate]]", 0, true];</code> </dd> </dd> </dl> </dl> <!-- DISCONTINUE Notes --> <!-- DISCONTINUE Notes --> View the full article
  7. ← Older revision Revision as of 02:58, 23 April 2017 Line 86: Line 86: Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. [http://feedback.arma3.com/view.php?id=22583 Feedback_Link] [http://feedback.arma3.com/view.php?id=22583 Feedback_Link] + </dd> + </dl> + <!-- DISCONTINUE Notes --> + + <!-- CONTINUE Notes --> + <dl class="command_description"> + <dd class="notedate">Posted on April 23, 2017 - 02:58 (UTC)</dd> + <dt class="note">[[User:OOKexOo|OOKexOo]]</dt> + <dd class="note"> + 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:<br> + <code>[1986, 2, 25, 16, 0] [[remoteExec]] ["[[setDate]]", 0, true];</code> </dd> </dd> </dl> </dl> <!-- DISCONTINUE Notes --> <!-- DISCONTINUE Notes --> View the full article
  8. (0)

    (0) (RSS generated with FetchRss)View the full article
  9. Underdogs by Undeceived (RSS generated with FetchRss)View the full article
  10. Undo revision 99557 by Commy2 (talk) Not working properly =/= not implemented. Reverting until the decision about its future is made. ← Older revision Revision as of 21:59, 22 April 2017 Line 569: Line 569: icon = "\A3\MyAddon\Rifles\MyRifle\Data\MyRifle_X_CA.paa" /// this stays the same as before and is used as a base layer icon = "\A3\MyAddon\Rifles\MyRifle\Data\MyRifle_X_CA.paa" /// this stays the same as before and is used as a base layer }; }; + }; + + === Magazine compatibility groups === + + * Update 1.42 adds a new functionality for magazines and their compatibility - modders are now able to define groups for magazines and don't need to write down all the compatible magazines in a weapon class. Property '''magazineGroup''' in magazine class is used to create such groups. Weapon then checks its ''magazines'' array for both magazine class name and possibility of having a compatible magazine by a group. + + class CfgWeapons + { + class Rifle_Base_F; + class Test_weapon_01_Base_F: Rifle_Base_F + { + magazines[] = {"30Rnd_test_mag", "MyMagGroup"}; /// original custom made magazines and a group of several standardized mags + }; + }; + class cfgMagazines + { + class CA_Magazine; + class 30Rnd_test_mag: CA_Magazine + { + magazineGroup[] = {"test_mag_group"}; /// all magazines in the same group may be used in weapon that has the group defined as compatible + }; + class 30Rnd_test_mag_Tracer: 30Rnd_test_mag {}; /// this magazine ingerits the group and is use-able in the test weapon }; }; View the full article
  11. Removed incorrect assumption that STR_ is some sort of special prefix - it is not ← Older revision Revision as of 21:52, 22 April 2017 Line 42: Line 42: </code> </code> − *The key ID MUST start with "STR_" *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 Line 79: Line 78: ====Dialogs==== ====Dialogs==== − As with Description.ext, the entry must start by "$STR_" to work, and the preprocessor will replace the values in configs as long as the key name is formatted correctly (see above) : + As with Description.ext, the preprocessor will replace the values in configs as long as the key name is formatted correctly (see above) : <code>class RscText_1012: RscText <code>class RscText_1012: RscText View the full article
  12. ‎Example Format: ← Older revision Revision as of 14:50, 22 April 2017 (3 intermediate revisions by the same user not shown) Line 42: Line 42: </code> </code> + *The key ID MUST start with "STR_" *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 Line 78: Line 79: ====Dialogs==== ====Dialogs==== − As with Description.ext, the preprocessor will replace the values in configs as long as the key name is formatted correctly (see above) : + As with Description.ext, the entry must start by "$STR_" to work, and the preprocessor will replace the values in configs as long as the key name is formatted correctly (see above) : <code>class RscText_1012: RscText <code>class RscText_1012: RscText Line 86: Line 87: tooltip = $STR_myTag_someTip; tooltip = $STR_myTag_someTip; ...</code> ...</code> − ====CfgRadio==== ====CfgRadio==== View the full article
  13. ‎Dialogs ← Older revision Revision as of 14:46, 22 April 2017 (One intermediate revision by the same user not shown) Line 78: Line 78: ====Dialogs==== ====Dialogs==== − As with Description.ext, the preprocessor will replace the values in configs as long as the key name is formatted correctly (see above) : + As with Description.ext, the entry must start by "$STR_" to work, and the preprocessor will replace the values in configs as long as the key name is formatted correctly (see above) : <code>class RscText_1012: RscText <code>class RscText_1012: RscText Line 86: Line 86: tooltip = $STR_myTag_someTip; tooltip = $STR_myTag_someTip; ...</code> ...</code> − ====CfgRadio==== ====CfgRadio==== View the full article
  14. ← Older revision Revision as of 22:47, 21 April 2017 Line 10: Line 10: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Asks server to execute given scripted function or script command. The environment chosen for the execution is as follows:<br><br> + | Asks server to execute given scripted function or script command on given target PC. The environment chosen for the execution is as follows:<br><br> * Scripted function - ''unscheduled'' environment ([[canSuspend|suspension]] is NOT allowed). * Scripted function - ''unscheduled'' environment ([[canSuspend|suspension]] is NOT allowed). * Script command - ''unscheduled'' environment ([[canSuspend|suspension]] is NOT allowed). <br><br> * Script command - ''unscheduled'' environment ([[canSuspend|suspension]] is NOT allowed). <br><br> View the full article
  15. ← Older revision Revision as of 22:47, 21 April 2017 Line 10: Line 10: ____________________________________________________________________________________________ ____________________________________________________________________________________________ − | Asks server to execute given scripted function or script command. The environment chosen for the execution is as follows:<br><br> + | Asks server to execute given scripted function or script command on given target PC. The environment chosen for the execution is as follows:<br><br> * Scripted function - ''scheduled'' environment ([[canSuspend|suspension]] is allowed, i.e. [[spawn]], [[execVM]]). * Scripted function - ''scheduled'' environment ([[canSuspend|suspension]] is allowed, i.e. [[spawn]], [[execVM]]). * Script command - ''unscheduled'' environment ([[canSuspend|suspension]] is NOT allowed). <br><br> * Script command - ''unscheduled'' environment ([[canSuspend|suspension]] is NOT allowed). <br><br> View the full article