Home

Welcome to the Half-Life-Scripts wiki!

Performance Issues / Tips

For the use of scripts (and running this game in general), the computer must be running stable at a given frame rate at all times. This is hard to maintain ideally, however certain measures can help to achieve such thing. Note for AMD/Intel graphics users: OpenGL support on AMD is noticeably bad compared to NVIDIA's, and Bunnymod XT relies on this backend. Therefore... sorry to tell you that.

• For Windows 7/Vista, you may set hl.exe priority to "High" using the Task Manager (CTRL+ESC+SHIFT).
• Using the console "~" set r_dynamic 0 and r_decals 1, the first command disables dynamic lighting such as explosions, flashlight and environment, the second will limit the amount of decals like blood and dust.
• Launch the game at a lower resolution like 800x600
• If your Half-Life build dates from 2013 or later, you may enable "Low video quality" under video options.
• Certain Half-Life builds may run better on your hardware, you can try using latest from your steam account, GoldSource Package 2.1 (2009) link or Half-Life 2005 link
• If you're capable of setting thread affinity for Half-Life, you may notice improvements, somehow on more than capable machines the game can't run properly.

cmd name / _special

Half-Life's client.dll between release and pre-steam (WON patches) has cmd name, and from Steam port circa 2003 up until 2013 has _special, both work as a way of parsing stuff into the end of the command buffer from within a script, which allows looping scripts and receiving player inputs at the same time. Valve in 2013 decided to patch these altogether at engine level¹ so no cmd name nor _special can be used. That's why BunnymodXT's bxt_append is the best way to get this functionality everywhere. ¹citation needed

Common scripting console commands

wait stops command parsing until the next frame.

TODO