Monday, 2025-07-07, 3:18 PM
Welcome Guest | RSS
HL/AG Europe
Main | Downloads | Sign Up | Login
Site menu
:.mini chat.:
Our poll
Rate my site
Total of answers: 44
Statistics

Total online: 1
Guests: 1
Users: 0
Main » Files » other

Bugfixed and improved HL release 0.1.795
2014-06-23, 0:15 AM

sVersion: 0.1.795

Info:

  • Bugfixed and improved HLSDK release.
    This was started in a purpose to replace bugged hl.dll on a server to prevent frequent server crashes.
    Now it's a lot of fixes and improvements to server and client sides.
    Based on HLSDK version 2.3-p3 patched by metamod team.
    Binaries for Half-Life Windows client and Windows/Linux server, single and multiplayer.



  •  
  •  


Thanks:

  • Valve for HLSDK release.
    Willday for his HLSDK patch.
    BubbleMod and Bigguy from hlpp.thewavelength.net for parts of spectator code.
    Uncle Mike from hlfx.ru for his Xash3D engine which was very helpful in hard moments.
    KORD_12.7 for constant helping and nice suggestions.
    AGHL.RU community for bug reporting and suggestions.



  •  
  •  


Sources:


Installation:
Copy all files from archive valve folder to server/client valve folder replacing all.
For Steam copy to Steam\steamapps\common\Half-Life folder.

Server side cvars and commands:

  • allow_spectators 1
    values: 0/1
    meaning: Allow players to go into spectator mode.

    spectator_cmd_delay 5
    values: double equal or above 1.0
    meaning: Specify a minimal delay between adjacent "spectate" client commands in seconds.

    mp_welcomecam 1
    values: 1/0
    meaning: Enable/disable welcome cam.

    mp_notify_player_status 7
    values: 1-7
    meaning: Selects notifications for player join/leave/spectate events in chat. Bits value.
    1 bit - leave notification.
    2 bit - join notification.
    3 bit - enter/leave spectate notifications.
    To be said easy: 0 means "no notifications", 1 - default HL "player leave notification", 3 - join and leave notifications, 7 - all notifications.

    mp_bunnyhop 1
    values: 1/0
    meaning: Enable/disable bunnyhop.
    0 max speed is clamped to 350 to prevent bunnyhop. This is default HL behaviour.
    1 max speed is clamped to 2000, thus allowing bunnyhop.



  •  
  •  



Screenshots:

  • Srcreenshot on client are now saved by default in valve/results/year-month/ folder. Look following cvars for more details: snapshot_jpeg, snapshot_jpeg_quality, results_file_format, results_counter_format.



Client side cvars and commands:


  • cl_bunnyhop 1
    values: 0/1
    meaning: Enable/disable client-side bunnyhop prediction. Remember that this is only prediction, real speed clamping is decided by server. This setting is needed to prevent jerks that happen when prediction doesn't match the server.
    0 max speed is clamped to 350 to prevent bunnyhop. This is default HL behaviour.
    1 max speed is clamped to 2000, thus allowing bunnyhop.

    m_input 1
    values: 1/2
    meaning: Selects mouse input method.
    1 mouse movement will be read from Windows cursor movement. This is default HL behavior.
    2 mouse movement will be read via DirectInput. This way Windows cursor acceleration feature will not affect mouse input, i.e. acceleration is ALWAYS OFF by this way.

    hud_draw 1
    values: 0.0-1.0
    meaning: Now it can accept values from 0 to 1 (i.e. 0.5, etc), this regulates hud transparency.

    hud_dim 1
    values: 0/1
    meaning: Enable/disable dimming of health, armor, ammo and other elements when they are inactive (not changing).

    hud_color "255 160 0"
    values: "R G B"
    meaning: Color of hud elements in RGB format. Used for all elements, but health and armor.

    hud_color1 "0 255 0"
    hud_color2 "255 160 0"
    hud_color3 "255 96 0"
    values: "R G B"
    meaning: Colors of health and armor in RGB format.
    hud_color1 used for value >= 90, hud_color2 for 50 <= value < 90 and hud_color3 for 25 < value < 50.
    Also hud_color3 is used for armor value <= 25. Health for values <= 25 draws in red (can't be changed via cvars).

    hud_colortext
    values: 0/1/2
    meaning: Configure color codes processing in hud, chat, death list, spectator panel, scoreboard, status bar.
    0 turn off color codes processing.
    1 colorize text acording to color codes in chat, death list, status bar and remove color codes in hud, spectator panel, scoreboard.
    2 remove color codes, but do not colorize text.

    hud_shownextmapinscore 1
    values: 0/1
    meaning: Controls whether or not to show nextmap in scoreboard table.

    hud_showlossinscore 1
    values: 0/1
    meaning: Controls whether or not to show loss in scoreboard table.

    hud_showsteamidinscore 1
    values: 0/1
    meaning: Controls whether or not to show SteamIds in scoreboard table.

    hud_nextmap 1
    values: 0/1/2
    meaning: Enable/disable nextmap show in the hud on the map end.
    0 turn off nextmap show in hud.
    1 show nextmap for about 30 seconds starting from 60 till the end.
    2 show nextmap last 60 seconds of the map.

    hud_timer 1
    values: 0/1/2/3
    meaning: Enable/disable show of timer in hud.
    Timer has three modes:
    0 will turn timer off,
    1 will show time left on current map,
    2 will show time passed on current map,
    3 will show your PC local time.
    Timer will get map time limit directly from server rules, so it will work on most servers.
    It will not work on some servers where paranoid admins removed server rules.
    Also it will not display left time if there is no time limit on server.

    hud_weapon 0
    values: 0/1
    meaning: Enable/disable displaying sprite of currently selected weapon.

    customtimer <interval in seconds> [timer number 1|2]
    This command will start countdown of custom timer from specified second to zero and will emit sound "bell" when timer will reach 0.
    There are two undependent custom timers. If timer number isn't specified it is assumed 1.

    cl_forceemenymodels ""
    values: List of models split with ";", for example "red;zombie".
    meaning: List of models for replacing enemy models.
    If you don't like various custom player models that servers likes to upload you can use
    cl_forceemenymodels "zombie;scientist;robo;recon;hgrunt;helmet;gordon;gman;gina;barney"
    to force using of default model.

    cl_forceemenycolors ""
    values: Top and bottom colors split by a space, for example "90 30".
    meaning: Top and bottom colors for enemy colors replacing.

    cl_forceteammatesmodel ""
    values: List of models split with ";", for example "blue;hgrunt".
    meaning: List of models for replacing teammates models.

    cl_forceteammatescolors ""
    values: Top and bottom colors split by a space, for example "90 30".
    meaning: Top and bottom colors for teammates colors replacing.

    forcemodel <slot number or player name> [model name]
    Slot number (can be seen in status command output in first column, range is from 1 to 32.
    Model name, if specified, will be used for model replacement on given player. If empty, will reset model replacement.

    forcecolors <slot number or player name> [top and bottom colors]
    Slot number (can be seen in status command output in first column, range is from 1 to 32.
    Top and bottom colors, if specified, will be used for colors replacement on given player. If empty, will reset colors replacement.

    engine_fix_fpsbug 1
    values: 0/1
    meaning: Enable/disable fix of FPS bug in the engine. This will fix moving slowdown on certain FPS values.

    engine_snapshot_hook 1
    values: 0/1
    meaning: Enable/disable intercepting of "snapshot" command and perfom custom processing (saving to jpeg format and with custom names).

    snapshot
    If engine_snapshot_hook is 1 this command creates snapshots with customizable names and formats. By default screenshots are placed in /results/year-month/ folder in jpeg format.

    snapshot_jpeg 1
    values: 0/1
    meaning: Enable/disable saving screenshots to jpeg format.
    If 1 will save as jpeg, if 0 will save as bmp. Custom naming rules still apply to bmp screenshots.
    Requires engine_snapshot_hook 1 to work.

    snapshot_jpeg_quality 95
    values: 1-100
    meaning: Quality of jpeg compression. Changes size and quality of a picture. On 95 image almost the same as bmp, but takes 10 times less space.

    results_file_format "results\%Y-%m\%l-%Y%m%d-%H%M%S"
    values: Format string for C++ function strftime. You can see description of it on http://www.cplusplus.com/reference/clib ... /strftime/
    meaning: This string is used to construct results file name. It is used currently for screenshots.
    You can specify subfolders (under mod directory) via adding "\" symbol.

    results_counter_format "-%03d"
    values: Format string for C++ function sprintf which receive also integer counter from 1 to 1000.
    meaning: It is used to construct unique results file name when there is alredy file with such name exists.
    This conuter is added to file name.
    Actually you can/need only variate splitter symbols and counter width.

    cl_autowepswitch 1
    values: 0/1
    meaning: If 1 weapon will automatically switch to picked one if it is more powerful. Requires server-side support.

    cl_messages_log 0
    values: 0/1
    meaning: If 1 client will log user messages in console when it will receive them from server. Mostly needed for developers.

    cl_messages_dump
    Dumps currently registered user messages with their ids and lengths. Mostly needed for developers.

    con_say_color "30 230 50"
    values: "R G B"
    meaning: Color for say messages displayed in console in RGB format.



  •  
  •  

 

Category: other | Added by: PheX
Views: 1289 | Downloads: 5 | Rating: 0.0/0
Total comments: 0
Only registered users can add comments.
[ Sign Up | Login ]
Login Panel
Search
Site friends
  • HL/AG Europe Facebook group
  • AMX Banlist
  • HLstatsX
  • PheX youtube channel
  • Copyright by PheX © 2025