Prop-Hunt is a gamemode in TF2 that has some kind of "hide and seek" gameplay. RED team are disguised as "props" (common objects in TF2 maps, like trees, tables, barrels, and so much more) while BLU team are a group of pyros and heavies trying to find and eliminate them. To find a Prop-Hunt server use this page.
Anyone who played this mode knows that when you're on RED, you can freeze yourself by holding mouse2 (right-click). Unfortunately, as a RED player you will find yourself freezing most of the time. Here comes my simple scripts- right-click once to freeze, right-click again to unfreeze.
Put the following in the autoexec.cfg file:
//Prop Freeze
alias propi "propon";
alias propon "+attack2; alias propi propoff;"
alias propoff "-attack2; alias propi propon;"
bind mouse2 +attack2
alias propih "prophon";
alias prophon "say_team Prop bind is ON; bind mouse2 propi; alias propih prophoff"
alias prophoff "say_team Prop bind is OFF; bind mouse2 +attack2; alias propih prophon; propoff;"
bind "'" "propih";
In the last line, change the bind to a free key anywhere on your keyboard. When you join a Prop-Hunt server, hit it to turn on the mouse2 toggle. When you want to disable it, hit that key again.
When "prop bind is on", you can use mouse2 to toggle between freezing and unfreezing.
23.11.09
Managing Scripts in Team Fortress 2
Whether you never used a single script for TF2 yet, or you already have some, I fully recommend that your "cfg" directory will contain the following files:
scout.cfg
soldier.cfg
pyro.cfg
demoman.cfg
heavyweapons.cfg
engineer.cfg
medic.cfg
sniper.cfg
spy.cfg
back.cfg
autoexec.cfg
The file config.cfg should already be there.
1. Any class config file should start with the line "exec back.cfg".
2. Basically, any class-specific script will go to its class config file. Any binds that are effected by that script, should be redefined in back.cfg. For example, if the soldier config file binds the mouse2 (right-click) button to a rocket jump script, then you should write the line "bind 'mouse2' +attack2" in "back.cfg".
This is kind of a must-do before you read any of my other scripts related posts.
scout.cfg
soldier.cfg
pyro.cfg
demoman.cfg
heavyweapons.cfg
engineer.cfg
medic.cfg
sniper.cfg
spy.cfg
back.cfg
autoexec.cfg
The file config.cfg should already be there.
1. Any class config file should start with the line "exec back.cfg".
2. Basically, any class-specific script will go to its class config file. Any binds that are effected by that script, should be redefined in back.cfg. For example, if the soldier config file binds the mouse2 (right-click) button to a rocket jump script, then you should write the line "bind 'mouse2' +attack2" in "back.cfg".
This is kind of a must-do before you read any of my other scripts related posts.
Labels:
TF2 Scripts
How To Use Google Chrome Search Engines
I'm using Google Chrome for about a year now. Besides the obvious advantages of speed, clearness and lightness, the best thing I like in Google Chrome is the way it handles search engines.
Sadly, the small matter I'm going to explain isn't well realized by many. I hope I will change it a bit.
If you configure Chrome right, you can search in any site you like faster than in any other browser. All you need to do is to hit ALT+D while browsing to get to the address bar, type two or three letters that represent your search site (e.g. "yt" for YouTube), type space, your search term, and Enter. You get your results.
Some more examples, to make it clear: When I want to check the quality of a movie, I will probably hit ALT+D, type "imdb movie name", and later perhaps "yt movie name trailer". If I want to search for subtitles, all I need is to type in the address bar "sc movie name" (www.SubCenter.org). To go to an article in Wikipedia I just type "we Article Name" ('we' stands for Wikipedia English). For Hebrew Wikipedia I will type "וק שם ערך". You get the point.
Getting it done is easy. If your search site is popular enough, just open the site and go to the Search Engines Manager (ALT+D, Menu Key [the key between WinKey and Ctrl], "Edit search engines..."), you will find it there. All you need to do is to define a new keyword for it, and probably a better name.
On the other hand, if Chrome doesn't recognize your site, things are getting a bit trickier. In your search site, search for a simple term like "hello". Now copy the URL, and replace the simple term with %s. Copy the URL to the Search Engines Manager, assign a keyword (two-three letters), a good name and you're done.
This is how I use Google Chrome. To give you a feeling of how useful this feature is, here are my search engines:
For some cases, I use Hebrew keywords to search for terms in Hebrew, for convenient.
Subscribe to:
Posts (Atom)