User Inputs and Outputs
fast payday loan young gay free gay muscle currency exchange volunteer state book electorial map 2004 guarana innovation tools barbi twins adult zelda doujinshi bear sex nude girl pics beautiful men hardcore yaoi men in diapers sprint online payment innocent spouse tax relief ky jelly people killing each other work at home on internet be cool hacker empire state college moving to maui refineries line listing poker room jodie marsh scat girl consumer digest water torture saigon office desks mature teacher perfume outlet lisa simpson nude ratemenude sienna guillory cursors relatives word puzzles women suck blowjob h cup sized breasts brigitte bardot kit make theater up girls loving each other famous photographers avs erase bad credit icons gay pron xxx hacked passwords young teen girls modeling head injury attorney cat lovers gifts upskirt oops upskirt office carre otis kitchenaid first blowjob dog crates max orloff slow fuck trade stocks class equal a pound celebs topless dragonball z xxx troybilt nude lola bunny apples caramel gourmet recipe education including college lads mag ice new holland tractors met art free legal redress albert einstein quark express fuji finepix s5100 childrens sermons corporate gift idea picnic basket lucifer engraving air force general officer announcements cartoon kids women sucking toes russian girl sex under age vinocraft mail boxes santa monica california watch night eagle clipart young teen girls nude roll up garage door minneapolis airport chicas bonitas desnudas nasty slut iva wild lesbians x rated shot glasses denim karin taylor chicago police department The FireUser1-4 inputs and OnUser1-4 outputs are available on every entity that can receive Inputs and Outputs. This set of controls are specially linked to work together. Although they are not used very commonly, User inputs and outputs can be very powerful and make certain tasks far easier to accomplish.
The FireUserN input simply causes the corresponding OnUserN output on the same entity to fire. These are useful for forwarding messages through an entity where the desired target is known to the forwarding entity, but not to the firing entity.
For example, say you have three trains moving along the same set of path_tracks. Each train has a glowing env_sprite parented to it, and on one path_track you want to turn off the sprite on whatever train has just passed. The problem is that the path_track doesn't know which train has just passed, so you can't connect the "OnPass" output to the right one. So, you solve this by connecting the path_track's "OnPass" output to the !activator (the train) FireUser1 input, and then connect each train's OnUser1 input to turn off their parented sprite.
In the past, you could hack around this kind of thing by putting a trigger_multiple for every train on the path_track, set them to only trigger when the matching train touches them, and use the "StartTouch" output to turn off the sprite. Unfortunately, that method doesn't scale to large numbers of trains (as seen in the Citadel section of Half-Life 2).