Advertisement
Guest User

Untitled

a guest
Oct 20th, 2016
96
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 15.96 KB | None | 0 0
  1. ==============================================================================
  2. FILE
  3. ==============================================================================
  4.  
  5. Name - Double Doppler's Arma 2 Taser Mod
  6. Date - 23/2/2013
  7. Author - Double Doppler (D.Doppler)
  8. Contact - doubledoppler@live.co.uk
  9. Version - 1.1 (Initial Release)
  10.  
  11. Copyright © 2013 Double Doppler
  12.  
  13. Visit www.youtube.com/user/TheDoubledoppler for more fantastic addons on Arma 2 and GTA IV!
  14.  
  15. ==============================================================================
  16. DESCRIPTION:
  17. ==============================================================================
  18.  
  19. Created and tested on Arma 2 Operation Arrowhead and Combined Operations v1.62
  20. and over. Not intended for stock Arma 2 nor tested on it.
  21.  
  22. All content provided for this addon is purpose built from scratch by the author.
  23. Designed with Life Missions/RP Mods in mind, so you no longer have to use those
  24. Makarov 'Stun pistols'...
  25.  
  26. --------------------
  27. Features:
  28. --------------------
  29.  
  30. - Highly detailed and accurate 3D Models, Textures and Materials, created from
  31. scratch for this mod and optimized for the Arma 2 game engine.
  32. (No ports from other games or conversions.)
  33.  
  34. - Complete configuration. All included weapons feature native animations and most
  35. features that the stock weapons have. (Gear icons, working gunsights etc.)
  36.  
  37. - Realistic ammo and range for each weapon. Drive-Stun option available on handheld
  38. Taser models.
  39.  
  40. - Ability to incapacitate a player/unit for 30 seconds.
  41.  
  42. - Each Taser is equipped with a flashlight, as an additional policing feature.
  43.  
  44. - Red-dot cursor replacement for Tasers, to simulate aiming recticule.
  45.  
  46. - Extra media and custom special effects features - pain screens, Taser shot sparks
  47. and sound effects.
  48.  
  49. - Flexible Taser scripts, designed to have minimal conflict with most Life Missions.
  50. Scripts compatible and tested in Multi-Player with a full RP community server.
  51. (Comes with a userconfig file, to define your own configuration values.)
  52.  
  53. - Scripts are designed to work in all environments, on AI and human players in both
  54. single-player and multi-player.
  55.  
  56. - Minimal latency and load on the multiplayer dedicated-server enviroment.
  57.  
  58. - Addon files signed with the V2 signatures and server-ready, with included .bisign
  59. and .bikey files.
  60.  
  61. --------------------
  62. Classnames:
  63. --------------------
  64.  
  65. Taser X26 (Yellow) - DDOPP_X26
  66. Taser X26 (Black) - DDOPP_X26_b
  67. Taser X26 (Cartridge) - DDOPP_1Rnd_X26
  68.  
  69. Taser X3 (Yellow) - DDOPP_X3
  70. Taser X3 (Black) - DDOPP_X3_b
  71. Taser X3 (Cartridge) - DDOPP_3Rnd_X3
  72.  
  73. Initialization Logic - DDOPP_TaserInit
  74.  
  75. ==============================================================================
  76. CHANGELOG:
  77. ==============================================================================
  78.  
  79. v1.1 (23 February 2013)
  80.  
  81. - Added Taser weapons/ammo box. (Editor: Empty > Ammo > Taser Box.)
  82.  
  83. - Fixed restrain bug. (Victim seemed to "ignore" restrain and reverted to normal
  84. animation after the stun effects were over. Animation strings are CASE SENSITIVE.)
  85.  
  86. v1.0 (17 February 2013)
  87.  
  88. - Initial public release.
  89.  
  90. ==============================================================================
  91. INSTALLATION:
  92. ==============================================================================
  93.  
  94. 1. Copy the following included folders: @DDOPP_Taser and Keys to your Arma 2/OA
  95. folder. (CO uses Arma 2.)
  96.  
  97. 2. Right click the shortcut* you use to launch Arma 2 with and select "properties"
  98. from the menu.
  99.  
  100. 3. In the properties window, highlight the 'Target' text box and at the end of
  101. the directory reference (included in the double quotes ""), add the line:
  102.  
  103. -mod=@DDOPP_Taser
  104.  
  105. *If you are installing this addon on a dedicated server, your admin remote access
  106. software might not give access to the shortcut (esp. if using TCAdmin), but allows
  107. you to add command lines to it. If it is easier, use this feature instead to carry
  108. out step 2 and 3.
  109.  
  110. --------------------
  111. Server Admins:
  112. --------------------
  113.  
  114. Make sure that the "Keys" folder was moved into your servers Arma 2 folder, this is
  115. very IMPORTANT if you dont want players getting kicked all the time when they already
  116. have valid signatures.
  117.  
  118. Any edits you make to the "Userconfig" folder for your server must be redistributed in your
  119. Mod Pack so that the players will notice these effects as well.
  120.  
  121. ~ You may edit the scripts and comment out the external userconfig reference or to change
  122. the path and redistribute in YOUR server's Mod Pack only if this makes it easier.
  123. (To do this you must open then repack the PBO with your edits etc.)
  124.  
  125. --------------------
  126. IMPORTANT
  127. --------------------
  128.  
  129. To make use of the Taser fully you must install the scripts in the mission you will use it
  130. on or join a server that uses the mod with the scripts already setup.
  131.  
  132. If the scripts aren't setup, you will notice no effect when the Taser is fired.
  133.  
  134. ~ The Userconfig installation is REQUIRED for the addon to work correctly, otherwise your
  135. game will crash. You may edit the PBO and repath/disable this feature/initialize the variables
  136. inside the scripts instead if that makes it easier for your server's mod pack.
  137.  
  138. ~ If you are editing the PBO you might need to resign it again to make it work with your server.
  139. (Use your own server keys.)
  140.  
  141. ==============================================================================
  142. INSTALLING THE SCRIPTS
  143. ==============================================================================
  144.  
  145. The scripts included are optional, however it is recommended that you do enable them
  146. if you want full functionality from the mod. The scripts have been designed to intergrate
  147. into most missions and will have minimal effect on performance and latency.
  148.  
  149. To initialize the included scripts:
  150.  
  151. 1. Add the initialization logic to your mission, found under:
  152.  
  153. Side > Game Logic
  154. Class > D.Doppler Taser Mod
  155. Unit > Initialize Taser Scripts
  156.  
  157. (Classname is 'DDOPP_TaserInit')
  158.  
  159. 2. Make sure all the units in your mission that will use the Taser or will be
  160. tased are named.
  161.  
  162. Scripts work in MP and SP, on players and AI alike, however if you are dynamically spawning
  163. new units in your mission (like in warfare/domination/AI etc.), you must make sure that:
  164.  
  165. ~ They are named
  166.  
  167. ~ They have the following code added to their init field on creation:
  168.  
  169. /////////////// Code! cOde! coDe! codE! ///////////////
  170.  
  171. this setVariable ["isTazed",false,true];
  172. this addEventHandler ["HandleDamage",{_this call DDOPP_taser_handleHit}];
  173.  
  174. /////////////// Code! cOde! coDe! codE! ///////////////
  175.  
  176. --------------------
  177. IMPORTANT
  178. --------------------
  179.  
  180. If your mission already features a "HandleDamage" EH then you may need to merge the
  181. included EH with your mission's EH to prevent them conflicting in-game.
  182.  
  183. To do this, you must follow these steps (provided that you know what you are doing):
  184.  
  185. 1. Disable the automatic adding of the EH to all units triggered on script initialization.
  186. To do this you must set the variable "DDOPP_taser_enableEH" to false in the userconfig file.
  187.  
  188. (Userconfig file found in Arma 2\Userconfig\DDOPP_TaserMod\DDOPP_TaserConfig.hpp after installation.)
  189.  
  190. 2. Locate YOUR mission's HandleDamage EH and merge it with the following code:
  191.  
  192. (You may replace the "_this select x" with the local variable names you use in your mission's
  193. EH if you want.)
  194.  
  195. /////////////// Code! cOde! coDe! codE! ///////////////
  196.  
  197.  
  198. if ((_this select 4) in DDOPP_taser_arrBullet) then {
  199. [(_this select 0), (_this select 3), DDOPP_taser_koTime] spawn DDOPP_taser_victimFx;
  200. };
  201.  
  202. /////////////// Code! cOde! coDe! codE! ///////////////
  203.  
  204. The above EH is what triggers off the Taser script effects on each unit. If you
  205. want each unit to be affected by the Taser scripts in your mission, you must ensure
  206. each unit gets your EH added to it.
  207.  
  208. Note the following values passed by the "HandleDamage" EH are used in the code:
  209.  
  210. _this select 0 = Victim hit by Taser
  211. _this select 3 = Shooter who fired the Taser
  212. _this select 4 = Taser projectile/bullet
  213.  
  214. --------------------
  215. Editing the scripts:
  216. --------------------
  217.  
  218. You may edit the included scripts to increase compatibility with your mission/server, however
  219. these edits MUST stay on YOUR server and you may not redistribute your edits elsewhere.
  220.  
  221. ~ If you want to edit the scripts you will need a tool like BinPBO to open up the PBO, then repack
  222. it again. Make sure the binarize option is unchecked - re-binarizing the PBO might damage some of
  223. the included features.
  224.  
  225. All edits you make must feature a comment above the code, with your name followed by the date that
  226. your code was added, like in the following example:
  227.  
  228. // Your Name DD/MM/YY
  229. CODE THAT YOU ADDED;
  230.  
  231. E.g. "Double Doppler" edited the "HandleDamage" EH to delete bullet when hit on 5 February 2013:
  232.  
  233. // Double Doppler 5/Feb/2013
  234. deleteVehicle _bullet; // Generic code add or edit
  235.  
  236. Month should be in text format to avoid confusion if International date format is used. (MM/DD/YY.)
  237.  
  238. ==============================================================================
  239. LICENSE
  240. ==============================================================================
  241.  
  242. Effective since 5 February 2013.
  243.  
  244. THE AUTHOR RESERVES THE RIGHT TO DISTRIBUTE THE ADDON WITH THEIR OWN SET OF TERMS AND CONDITIONS FOR
  245. USAGE, AS STATED IN THE BI TOOLS END USER LICENSE AGREEMENT, AND TO MAKE CLEAR THAT WORKS INTEGRATED INTO
  246. FILES GENERATED BY THE BI TOOLS ARE THE PROPERTY OF THE ORIGINAL AUTHOR, NOT BOHEMIA INTERACTIVE STUDIOS.
  247.  
  248. BI TOOLS EULA LINK: http://community.bistudio.com/wiki/End_User_License_Agreement_for_BI%27s_Tools
  249.  
  250. THE ABOVE STATEMENT IS INTENDED TO PREVENT CONFUSION IN IP RIGHTS TO MODELS, TEXTURES AND OTHER THIRD PARTY MATERIAL
  251. INCORPORATED INTO BIS GAME FILES, AND PLAGIARIZING USERS STATING THAT THE AUTHOR HAS NO LEGAL CONTROL OVER THEIR
  252. OWN CONTENT.
  253.  
  254. ******************************************************************************
  255.  
  256. YOU ARE FREE TO USE THIS ADDON AS LONG AS YOU AGREE AND ABIDE BY THE FOLLOWING TERMS:
  257.  
  258. (Please scroll down to the bottom for the definitions.)
  259.  
  260. §1) Redistribution:
  261.  
  262. ~ You may only redistribute this Addon in your server's mod pack. (E.g. AddonSync or SixUpdater.)
  263.  
  264. ~ You may NOT redistribute this Addon anywhere else. (E.g. Armaholic, Mediafire.)
  265.  
  266. ~ You may NOT externally redistribute individual contents of the Game File (PBO), including but not
  267. limited to: Models (.p3d), Textures (.paa, .pac), Scripts (.sqf), Sound (.wav, .ogg, .wss).
  268.  
  269. ~ You must ensure that the LICENSE.txt is distributed, unedited, inside the .PBO
  270.  
  271. §2) Editing:
  272.  
  273. ~ You may edit the included SCRIPTS to increase compatibility with your mission/server, however
  274. these edits MUST stay on YOUR server and you may not redistribute your edits elsewhere, and in the
  275. manner stated in the installation instructions.
  276.  
  277. ~ You may not make edits to files which are locked such as but not limited to: ODOL .p3d files, by
  278. means of 'tool-using' or illegal 'cracking'.
  279.  
  280. ~ ANY EDITS YOU MAKE MUST STAY ON YOUR OWN SERVER/COMMUNITY FOR COMPATABILITY REASONS ONLY AND MAY
  281. ONLY BE DISTRIBUTED IN YOUR GAME SERVER MOD PACK. YOU MAY NOT MAKE EDITS TO FILES WHICH ARE ALREADY
  282. 'LOCKED' SUCH AS ODOL .P3D FILES BY MEANS OF ILLEGAL 'CRACKING'.
  283.  
  284. §3) Non Profit:
  285.  
  286. You must distribute this Addon free of charge. You may not use this addon in any way to gain profit.
  287. (E.g. using in a project that charges consumers cash for membership or use of included content).
  288.  
  289. §4) Attribution:
  290.  
  291. You may not claim this Addon as your own. When asked, you must refer to the original Author(s).
  292.  
  293. §5) Usage in other games:
  294.  
  295. Using this Addon or any of its included components in other games is prohibited.
  296.  
  297. §6) Trademarks:
  298.  
  299. The "DOUBLE DOPPLER" and "DD" trademark is property of Double Doppler.
  300.  
  301. All other trademarks listed in the used trademarks section (but not limited to) are property of their
  302. respective owners. The use of these trademarks in this Addon serve only as representation of the
  303. actual/real items where indicated and used on a good faith basis with no benefit or profit.
  304.  
  305. §7) Damages:
  306.  
  307. The Author may be not held responsible for the unlikely event that any damages are caused to your
  308. computer or other posessions. You downloaded this Addon free of charge out of your own will therefore
  309. the Author is not responsible for any technical damages or any other damages caused.
  310.  
  311. §8) Sensitive Information:
  312.  
  313. Any information or images depicting possible sensitive information is purely of fiction and imagination
  314. and in no way at all represents any classified information. This Addon, regardless of statement of
  315. accuracy, is no where based off real sensitive information and anything remotely resembling
  316. sensitive material is completely of coincidence and shall not be held accountable by any party.
  317.  
  318. §9) Waiver:
  319.  
  320. Users may waive either of these terms (excluding §7 and §8) IF GIVEN PERMISSION BY THE AUTHOR.
  321.  
  322. THIS ADDON IS PROVIDED WITHOUT COST AND IS FREE AND IS DOWNLOADED AT YOUR OWN FREE WILL, THEREFORE THE
  323. AUTHOR WILL NOT BE HELD ACCOUNTABLE FOR ANY COMPLICATIONS OR LIABILITIES, REGARDLESS.
  324.  
  325. Definitions:
  326.  
  327. a. "Addon" An addon (also reffered to as "Mod") is a user made modification designed to modify (within
  328. legal and practical boundaries) a computer game. The content in this folder or compressed file are
  329. considered components of an addon. The main addon resides in the combination of game files created
  330. in order to coordinate it.
  331.  
  332. b. "Author" The author is the person in the who created and coordinated this addon and holds copyright
  333. for the contents of this addon.
  334.  
  335. c. "Redistribute" means to make available to the public the original and copies of the Addon through sale,
  336. file upload or other transfer of ownership after the original Author.
  337.  
  338. d. "Game File" The main content. These files may include but are not limited to: 3D Meshes, Coordinates,
  339. Scripts, 2D Graphics and so forth. All copyright laws apply to these files. An example of a game file
  340. would be a .PBO file (Arma 2) or .WTD and .WFT files (GTA IV).
  341.  
  342. e. "Licensor" means the individual, individuals, entity or entities that offer(s) the Work under the
  343. terms of this License. In this case the licensor is the same person as the author.
  344.  
  345. f. "You" means an individual or entity exercising rights under this License who has not previously
  346. violated the terms of this License with respect to the Work, or who has received express permission
  347. from the Licensor to exercise rights under this License despite a previous violation.
  348.  
  349. g. "Reproduce" means to make copies of the Work by any means including without limitation by sound or
  350. visual recordings and the right of fixation and reproducing fixations of the Work, including storage
  351. of a protected performance or phonogram in digital form or other electronic medium.
  352.  
  353. h. "Addon Pack" is your clan/community/server's addon pack that contains all the 3rd-party content that is required
  354. to run the game properly. Usually consists of .pbo Addon files and their respective .bisigns, which commonly contain
  355. extra content such as scripts and models.
  356.  
  357. Copyright © 2013 Double Doppler. All rights reserved.
  358.  
  359. ==============================================================================
  360. CREDITS
  361. ==============================================================================
  362.  
  363. This modification and its components were created from scratch by Double Doppler Modding.
  364.  
  365. - 3D Models created and UV Mapped by Double Doppler and ported to Arma 2 via O2.
  366. - Textures created and mapped by Double Doppler.
  367. - RVMATs created by Double Doppler (NOHQ, SMDI etc.).
  368. - Scripts and config created by Double Doppler.
  369. - Special effects ported over by Double Doppler.
  370.  
  371. © 2013 Double Doppler Modding
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement