Hooks are functions that are "hooked up" to an event. Lua responds to an event by running hooks.
CLIENT SIDE ADDONS FOR GMOD MOD
Whenever an event occurs, Garry's Mod tells Lua that the event has happened. For example, if a player died, then the event might also carry information about which player died. Sometimes, events even carry associated information. There are even some events for non-game world things, such as drawing graphics on the Heads Up Display (or HUD, for short). More examples are when a player spawns, takes damage, or disconnects. One example of an event is when a player dies. This article will teach you the basics of a couple important concepts in Garry's Mod Lua scripting: events and hooks.Įvents are specific happenings in the game world.
Sv_a Makes corrections to the seat network?Ĭl_a Caches fonts and prevents them from being overwritten without changes.Ĭl_blink_gc.lua "This addon will check your client's current LUA memory and if too much memory is being used, will manually call for a collection of unused memory." BlinkGC Some idiot wrote this, but it seems to work. Sv_run_a Runs a bunch of commands to optimize the client and its graphics. Sv_a Disables server-side movement of the mouth and ears. Sh_umsg_to_net.lua Forces the obsolete umsg library to use the new net.
Disables the unnecessary depth display hook after death.Starts a timer to delete all ragdolls and objects on the client side.I think it's worth checking if you're using any of the list. Sh_remove_a Deletes entities that are not normally used. Sh_nw_to_nw2.lua "I don't think this is a good idea for now, NWVars2 have some problems right now which need fixing before this can be even considered."
Sh_limit_a Changes the physics of objects, both for the server and for the client. Sh_disable_a Disables unnecessary widget hooks that no one ever uses. If not otherwise stated differently all tests have been done on a gmod server on linux. Some of those benchmarks, if possible, were also tested in a LUA5.3 console on Debian 10.