[Share]Hltv commands

[JigSAW^^]

Hi MaxCheaters i am here to share with u some hltv commands that i have found

                         

   Content

-------------------------------------------------------------------------------

 

   1. Overview

   2. Spectating Games

   3. HLTV Basics

   4. Broadcasting Games

   5. Recording HLTV demos

   6. Larger Broadcasts

   7. HLTV Configuration

 

 

 

1. Overview

-------------------------------------------------------------------------------

 

   Half-Life TV offers the ability to have an unlimited number of spectators

   watching online games. They can follow the game just like they would as

   a spectator on the game server. Spectators are invisible to players and

   can't interact with the running game in any way. Each spectator can choose

   any view position or choose any player to track individually. To have the

   most enjoyable spectating experience, spectators can enable the

   Auto-Director mode. Then the camera is changed automatically so that only

   interesting scenes are shown from a suitable viewpoint. Thus the spectator

   can lean back and won't miss any relevant action. All the time, spectators

   may communicate between each other using the standard HL chat system.

 

   Most popular Half-Life MODs are supported like Counter-Strike, Team

   Fortress Classic, Day of Defeat and many others. HLTV providers have full

   control over their HLTV system, may change number of spectator slots, add

   text messages or change the HLTV logo. The broadcast is delayed by a

   customizable amount of time, by default 30 seconds. This ensures that the

   playing teams can't use HLTV to get any usable information about their

   opponents. Providing a single HLTV server for up to 100 spectators is an

   easy task and doesn't need any changes in default configurations.

 

   Installing a larger HLTV network for thousands of spectators needs some

   more planning time and experience about required bandwidth and CPU/RAM

   demands (see chapter 6).

 

 

 

2. Spectating Games

-------------------------------------------------------------------------------

 

   To watch a HLTV game, start Half-Life, open the Multiplayer menu and select

   'Find Servers'. To search for currently broadcasted games, choose the

   'Spectate' section and hit 'Refresh All'. After the list has been updated,

   double click on the server you want to spectate and you'll be connected.

 

   If computer game leagues announce important matches to be broadcasted via

   HLTV, they often provide IP:Port addresses of their HLTV servers. Instead

   of searching them via the server browser, you can also go to the

   'Favorites' folder and add the HLTV address to your server list by pressing

   the right mouse button. Otherwise, you can also open the console window and

   use the 'connect' command to spectate a certain game.

   

   For example:

 

       connect 192.168.130.42:27020

 

   The default HLTV port number is 27020, but may be changed. It should always

   be included in the given address, since commonly this port number is

   different from the default port number 27015.

 

   You can spectate the game in different modes: Chase Cam, First Person, Free

   Look, Map Overview and Map Chase. The easiest way to change modes is to

   press the JUMP key (default SPACE). Alternatively you can use the spectator

   menu, which can be enabled by pressing the DUCK key (default CTRL). Here

   you can customize your personal view style and enable the Auto-Director

   Mode. Press USE (default E) to cycle through the different

   Picture-In-Picture modes.

 

   The following HL console commands can be used to customize spectator

   settings:

 

   spec_autodirector <0|1> - turns Auto Director mode on or off

   spec_drawcone <0|1>     - shows your view cone in map overview mode

   spec_drawnames <0|1>    - shows player names under their icons

   spec_drawstatus <0|1>   - shows game information (time, map etc)

   spec_pip <0|1>          - turns Picture-In-Picture mode on or off

   spec_menu               - opens the spectator menu

   spec_help               - shows a help screen

   spec_mode <1-6> [<0-4>] - set the main view mode, seconds parameter is

                             the PIP mode. Not all combinations are valid.

                             Main modes are:

                               1 : Locked Chase        2 : Free Chase

                               3 : Free Roaming        4 : First Person

                               5 : Map Overview        6 : Chase Map Overview

                             PIP modes are:

                               0 : PIP off             1 : Free Chase

                               2 : First Person        3 : Map Overview

                               4 : Chase Map Overview

 

 

 

3. HLTV Basics

-------------------------------------------------------------------------------

                                       

   The core of the HLTV broadcasting system is the HLTV server, also called

   HLTV proxy. The HLTV executable is a console application that works much

   like a HL dedicated server. To broadcast a game running on a certain game

   server, the HLTV proxy connects to this server just like a normal player.

   Spectators connect themselves to the HLTV proxy and the game data stream is

   relayed through the HLTV proxy to all connected spectator clients. The next

   figure shows a basic HLTV configuration:

 

       HL Game Server -> HLTV Proxy => Spectator Clients

 

   The number of clients that one HLTV proxy can serve depends on available

   hardware and network resources. Theoretically, a single proxy can hold a

   maximum of 255 spectator clients. But be careful, even a proxy with 100

   spectator clients needs a full 2 MBit line to run smoothly. If more

   spectator slots are needed, the required network load must be distributed

   over multiple HLTV proxies.

     

   The first HLTV proxy connected to the game server is called the Master

   proxy, which sets the general broadcast settings like game stream delay or

   packet rate. All other HLTV proxies linked to this proxy are the Relay

   proxies. Their total number and link order is not restricted, they may form

   a chain or tree of proxies. Most important is that their location is in

   different networks to ensure a balanced bandwidth usage.

 

                                  -> HLTV Relay Proxy 1 => Spectator Clients

    HL Game Server -> HLTV Master -> HLTV Relay Proxy 2 => Spectator Clients

                                  -> HLTV Relay Proxy 3 => Spectator Clients

 

 

       

4. Broadcasting Games

-------------------------------------------------------------------------------

 

   Let's assume the most simple configuration, a single HLTV proxy in a LAN

   environment. This is a very common situation and the default HLTV settings

   doesn't need to be changed. Choose a dedicated computer as your HLTV proxy

   and install the Half-Life Dedicated Server, which also includes all files

   needed by a HLTV proxy. This isn't needed if Half-Life is already

   installed.

 

   Start the HLTV application (HL icon with a small camera) and the HLTV

   console will open, showing some initialization messages (if that takes a

   long time, HLTV maybe can't resolve some IP addresses, then start HLTV

   with the '-nodns' command line option). Then the console is ready to accept

   your commands, here we use '>' as the console prompt. First give your HLTV

   proxy an unique name:

 

   >name "My HLTV Proxy"

 

   Let's assume you have started the proxy on host 192.168.1.2 and the game

   server, you want to spectate is running on host 192.168.1.3:27015. Then

   connect the HLTV proxy to this game server by typing:

 

   >connect 192.168.1.3:27015

 

   After a few seconds HLTV will be fully connected and ready to serve

   spectator clients. Use the 'status' command to verify that the HLTV proxy

   has connected properly :

 

   >status

    --- HLTV Status ---

    Local IP 192.168.1.2:27020, FPS 72.8, Network In 0.8 Out 0.9

    Local Slots 128, Spectators 0, Proxies 0

    Source: Server "Half-Life" (192.168.1.3:27015)

    Total Slots 128, Spectators 0, Proxies 1

    Time 01:02, Game "valve", Map "maps/frenzy.bsp", Players 1

 

   The 'status' command shows your own IP address, HLTV system cycles per

   second, total incoming and outgoing network traffic in kB/sec. Local slot

   and spectator numbers your HLTV proxy is providing, total numbers are the

   sum of all slots & spectators on all proxies broadcasting this game. The

   game source can be a game server, another HLTV proxy or a demo file.

 

 

 

5. Recording HLTV demos

-------------------------------------------------------------------------------

 

   HLTV demo files are like normal recorded games in Half-Life, but you can

   choose any view point, view mode or player to chase during replay. To play

   back a HLTV demo, a HLTV proxy is not needed. Just start Half-Life and type

   in console "playdemo <demoname>" or "viewdemo <demoname>" (viewdemo offers

   more options during playback like fast forward/backward, pause &

   slowmotion). To record a HLTV demo, connect the proxy to a game server (see

   last chapter) and type in console:

     

   >record <name>

 

   All games will be recorded after issuing this command. The demo files will

   be saved in the current Mod directory, e.g. \cstrike. All demo files have a

   special naming convention <name>-<YYMMDDhhmm>-<map>.dem, including the

   given name, date/time and map name. Demo files record the same data as send

   to spectator clients. That means also, the demo file records the game with

   the same delay as used for spectators. To verify, that a demo file is

   recorded use the "status" command. The recording may be stopped with

   "stoprecording".

 

   Sometimes a HLTV broadcast is not wanted and the HLTV proxy is only used

   to record a demo file. In this case, some HLTV settings should be made to

   gain optimal recording results:

 

   >maxclients 0   // don't allow any spectator clients

   >delay 10       // smallest possible delay

   >rate 10000     // maximum data rate

   >updaterate 20  // standard update rate

   >nomaster 1     // don't register at master servers

 

 

 

6. Larger broadcasts

-------------------------------------------------------------------------------

 

   Setting up a HLTV network that can handle a larger number of spectators

   (>1000) is a difficult and time consuming task. The following guide should

   help to configure and run such a HLTV network. One of the most important

   rule should be "Quality, not Quantity". It's better to offer a smaller

   number of spectator slots, than operating at the maximum bandwidth limit,

   thus all spectators would suffer from lags and timeouts. Check carefully

   your available bandwidth capacity and calculate how many spectators can

   be handled by your HLTV servers. The average bandwidth demand per spectator

   is between 2 and 3 KB/sec and depends on the current mod, map and number of

   players. CPU and RAM shouldn't be a bottleneck on modern PC systems.

   

   This list for common Internet connection types gives a feeling, how

   bandwidth demanding HLTV can be:

         

       -   ISDN         64 Kbps            :      2 spectators

       -   DSL         128 Kbps (upstream) :      5 spectators

       -   T1          1.5 Mbps            :     75 spectators

       -   LAN          10 Mbps            :    500 spectators

       -   T3           75 Mbps            :   4000 spectators

 

   Use the "maxclients" command to set how many clients should be accepted by

   a HLTV proxy. Make sure that the "maxrate" variable is set too a reasonable

   value, e.g. 3500 kB/sec. Lower values are possible, but make sure spectators

   don't get too much "choke" during a running game. The "maxrate" command

   doesn't effect the bandwidth limit between HLTV proxies, only for spectator

   clients. To lower the general bandwidth demand, you can turn off the

   internal HLTV chat ("chatmode 0") or decrease the game update rate from the

   default value 20 to 10 ("updaterate 10"). A lower update rate may save up

   to 25% network traffic and is an acceptable tradeoff in this case since

   spectators doesn't need a high update rate like real players does.

     

   A very common setup for large broadcasts is to use 2 dedicated HLTV servers

   to create a private and a public HLTV segment. Let's assume the game server

   is in a closed LAN and not accessible from outside. This ensures a maximum

   security against attacks (DOS etc) from outside. The HLTV master server is

   started within the LAN and it's IP address should be kept secret. The

   second HLTV server is started outside the LAN with a global IP and is

   connected to the HLTV master server. This second HLTV server is the public

   HLTV dispatcher, which IP address is given to the audience. Any relay

   proxies are connected to this HLTV dispatcher. Thus the HLTV master server

   is in a secure LAN environment and can be used for demo recording or for

   HL clients serving video projectors. Spectators connect to the HLTV

   dispatcher and are relayed through the HLTV network to a relay proxy with

   a low usage. Thus the total network load is balanced between all connected

   HLTV proxies.

 

   +----   Private LAN -----+  +------ Public Internet --------+

                                                -> HLTV Proxy 1

    HL Server -> HLTV Master -> HLTV Dispatcher -> HLTV Proxy 2

                                                -> HLTV Proxy 3

 

   The configuration files of HLTV master and HLTV dispatcher are different:

 

   master.cfg:

 

    nomaster      1        // don't register at WON master servers

    proxypassword MyPWD    // protect HLTV server

    publicgame    0        // don't show game server IP

    dispatchmode  0        // don't dispatch spectators

   

   dispatcher.cfg:

 

    forcemaster  1         // register at WON master servers

    publicgame   0         // don't show game server IP

    dispatchmode 2         // dispatch all clients to other proxies

    hostname     MyGame    // public HLTV server name

   

 

   If you're running 3 or more HLTV servers in total, it's a good idea to

   use RCON to manage them via a single server admin tool. To enable RCON

   on a HLTV server an "adminpassword" must been set. Also "proxypassword"

   should be set to ensure only known HLTV providers can connect to your

   HLTV network. Otherwise anybody can connect with slow HLTV proxies and

   disturb your network load balancing.

                     

 

 

hope i helped

source : http://www.slipgate.de/download/HLTV-Readme.txt

[koukos13]

Nc Share man!! Thx a lot!! I couldnt understand sth about broadcasting games but now i am ok :)

[JigSAW^^]

Nc Share man!! Thx a lot!! I couldnt understand sth about broadcasting games but now i am ok :)

thats why i shared it with u ;) so u can understand hltv  better ;D