UPDATED 4/11/08 - 2:15pm CDTrnrnThis is another parachute plugin. I feel this one provides a lot more realism than most other parachute plugins I've seen.rn-------------------------------------------------------------------rnPrimary differences:rn1) You must use the command ripcord to deploy your parachute (not the USE key). Most players bind a key to the command (ex: bind "x" "ripcord").rn2) Its a one shot parachute. Once you pull the ripcord, you're committed. No more detaching, repacking redeploying etc.rn3) You must be 'catching air' for the chute to deploy. Otherwise it will malfunction.rn4) It uses a model named realchute.mdl. The model must be in the dod/models/ folder. The model provided is common one. But I scribbled out the gayass 'Whee I'm flying'.rnrnSee THIS THREAD for more info.rnrnUser Commnads:rnripcord - starts the parachute deploymentrnsay /chute - reports the status of YOUR chuternsay /chutes - reports the status of the pluginrnrnAdmin Command:rnamx_realchute <0|1|2|?> (command access level 'h' required)rn 0 - Plugin disabledrn 1 - Plugin enabled, 1 chute per life (default)rn 2 - Plugin enabled, unlimited chutesrn ? - Command helprnrnCVar:rnrealchute_ctrl <0|1|2> (see above)rn---------------------------------------------------------------------rnps, it also runs on CSrnrnEnjoyrnrnUPDATED 4/11/08 - 2:15pm CDTrnAdded fullupdate command protection (Thanx Wilson).

Ya, I DO use your chute model on the plugin we use on our server. Your chute is definately more realistic for DOD. I have another version of this plugin that gives the player a different chute depending on what team your on. Kinda neat, and only takes a few more lines of code.rnrnI'm not familiar with 'fullupdate' at all. Guess I'll have to do a little research.rnrnI used the older spawn detect method mainly so it would work with other mods (like CS). Maybe I should just do a separate plugin for each.rnrnThanks for the input.

Good idea. I can't believe that after all this time of writing plugins that I didn't know anything about the fullupdate exploit. Guess I got some work to do.

BTW, using the HamSandwich forward:rnRegisterHam(Ham_Spawn, "player", "player_spawn", 1)rnto detect player spawning seems to work pretty well. I noticed that when using a simple 'fullupdate block', it affects demos somewhat. So maybe Ham is a better alternative.

It could be done without too much trouble. If anything, I thought about freezing the player (unable to move or shoot) for 30 sec. while he was repacking.rnrnBut when you think about it, many times, players don't get the opporitunity to use their chute at all, let alone multiple times. And, in the interest of preserving some degree of realism, I figure the typical soldier wouldn't have a clue as to HOW to repack a chute. So for now, I plan on leaving it like it is. But you're certainly welcome to modify the code to do that.