Upload 28 files

Correct use of certain Events.txt

@@ -0,0 +1,153 @@
+Intro
+
+I posting this because i saw so numerous mistakes/questions at this area of srcipting. This is the one of the common problems amongst the coders and even not only beginners! New Round / Player Spawn / Round Start / Round End is a different things so read the below explanations and do not mess them.
+
+Usual call order of the events is listed below:
+New Round
+Player Spawn
+Round Start
+Round End
+
+1. New Round
+
+The "New Round" is happen at the "Freeze Time" start. The "Freeze Time" is a time in Counter-Strike when all players are "freezed" which means that they can't walk and do a primary attacks.
+
+In the past years the most common way that was used to determine this event was the use of the "RoundTime" event with a "Time" message argument check, but there was a certain issues which makes this metod inefficient:
+this event is specified, i.e. is sent to every player, so if there are no players no a server then it's not possible to detect the "New Round" with this method;
+this event is also can be the same for the "Round Start" because the value of the "mp_freezetime" server CVar can be equal to the value of the "Time" argument of the "RoundTime" message, so it is not accurate enough.
+Of course i haven't like that method so i had to think of something more efficient. So some months ago after a little research i've discovered the new method which does not have the issues that is listed above:
+PHP Code:
+register_event("HLTV", "event_new_round", "a", "1=0", "2=0") 
+Notice the two conditions.
+
+Note that this event is not called for very first round, i.e. on map start. If you need to catch that moment as well then in the most cases it's enough to use the plugin_init() or plugin_cfg() forward functions.
+
+Also i was amazed at how many mistakes was made even by the "expirienced" coders in try to detect the "New Round"! The most common mistake was:
+PHP Code:
+register_event("ResetHUD", "newRound", "b") 
+which is completely incorrect. The "ResetHUD" is a specified event which is called under many circumstances for every player. So sometimes you can get more than even one hundred such "newRound" function calls per a single round!
+
+
+2. Player Spawn
+
+I think no need to explain what the "Player Spawn" is. But many of the coders still do not know how to detect this event correctly.
+
+If you are using AMX Mod X v1.8 or higher, or if you have the "Ham Sandwich" module installed the most simple and efficient way of the "Player Spawn" detection is a hook of the "Spawn" function itself:
+PHP Code:
+RegisterHam(Ham_Spawn, "player", "fwHamPlayerSpawnPost", 1) 
+The last parameter means that the registered function will be called right after player spawn (post variant of the hook) and not right before player spawn (pre variant of the hook). At least for Counter-Strike it's also necessary to skip registered function call for a dead players. This call is happen when a player enters a server. The most common example is shown below:
+PHP Code:
+#include <amxmodx>
+#include <hamsandwich>
+ 
+public plugin_init() {
+        RegisterHam(Ham_Spawn, "player", "fwHamPlayerSpawnPost", 1)
+}
+ 
+public fwHamPlayerSpawnPost(iPlayer) {
+        if (is_user_alive(iPlayer)) {
+                // player spawned
+        }
+} 
+If the above method isn't suitable for you for some reasons, it's possible to use the different more "famous" method of the "ResetHUD" event hook that doesn't require an additional module but is more complex.
+
+You should note that the use of that method may even lead to a server crash. It could happen because the plugin actions is performed on a player in the middle of his spawn process. The example of such "dangerous" action is a call of the strip_user_weapons() fun module's function.
+
+Many of plugin writers does know that the "ResetHUD" event is called on a player spawn but not all of them does know that this event is also called when a player is enter a server (at least in Counter-Strike), on "fullupdate" client command execution, demo recording and round restart attempt (on Counter-Strike's "sv_restartround" / "sv_restart" CVar change for alive players). So to use the "ResetHUD" to detect the "Player Spawn" we will need to filter out all that actions.
+
+The moment when a player is joined a server can be filtered out by registering the "ResetHUD" event with a "e" flag which means that the registered function will be called on alive players. Note that sometimes that "e" flag will also allow a calls of the registered function on a dead players as well (this is a bug of the AMX Mod X core that has been fixed in version 1.80). So it's recommended to do the "alive" check inside of the registered function itself.
+
+The execution of the "fullupdate" client command and the start of a demo recording can be filtered out by blocking the command:
+PHP Code:
+// ...
+register_clcmd("fullupdate", "clcmd_fullupdate")
+// ...
+ 
+public clcmd_fullupdate() {
+    // stops the command but allows to "catch" it by any other running plugin
+    return PLUGIN_HANDLED_MAIN
+} 
+Though that method is simple it's recommended to not block the "fullupdate" command since it is used (automatically) on a client side on demo recording to properly update the HUD display and pass a proper data to a demo file on a beginning of a record process. Instead of "fullupdate" command block it's enough to just skip a call of the registered (to the "ResetHUD" event) function at the time when that command is issued on a client side.
+
+As for round restart attempt, probably some of you does think that it's not necessary to filter this event out because it's always called right before "New Round". This is incorrect - not always, it's possible to set "sv_restartround" / "sv_restart" CVar value for example to 60 so new round will be delayed for one full minute! Therefore to filter this out as well on round restart attempt for every alive player we will have to skip the call of the registered to the "ResetHUD" event function.
+
+The result code that is able to detect the "Player Spawn" is shown below:
+PHP Code:
+#include <amxmodx>
+#include <fakemeta>
+ 
+#define MAX_CLIENTS 32
+ 
+new bool:g_bPlayerNonSpawnEvent[MAX_CLIENTS + 1]
+ 
+new g_iFwFmClientCommandPost
+ 
+public plugin_init() {
+        register_event("ResetHUD", "fwEvResetHUD", "b")
+        register_event("TextMsg", "fwEvGameWillRestartIn", "a", "2=#Game_will_restart_in")
+        register_clcmd("fullupdate", "fwCmdClFullupdate")
+}
+ 
+public fwEvResetHUD(iPlayerId) {
+        if (!is_user_alive(iPlayerId))
+                return
+ 
+        if (g_bPlayerNonSpawnEvent[iPlayerId]) {
+                g_bPlayerNonSpawnEvent[iPlayerId] = false
+                return
+        }
+ 
+        fwPlayerSpawn(iPlayerId)
+}
+ 
+public fwEvGameWillRestartIn() {
+        static iPlayers[32], iPlayersNum, i
+        get_players(iPlayers, iPlayersNum, "a")
+        for (i = 0; i < iPlayersNum; ++i)
+                g_bPlayerNonSpawnEvent[iPlayers[i]] = true
+}
+ 
+public fwCmdClFullupdate(iPlayerId) {
+        g_bPlayerNonSpawnEvent[iPlayerId] = true
+        static const szFwFmClientCommandPost[] = "fwFmClientCommandPost"
+        g_iFwFmClientCommandPost = register_forward(FM_ClientCommand, szFwFmClientCommandPost, 1)
+        return PLUGIN_CONTINUE
+}
+ 
+public fwFmClientCommandPost(iPlayerId) {
+        unregister_forward(FM_ClientCommand, g_iFwFmClientCommandPost, 1)
+        g_bPlayerNonSpawnEvent[iPlayerId] = false
+        return FMRES_HANDLED
+}
+ 
+public fwPlayerSpawn(iPlayerId) {
+        // player spawned
+} 
+
+3. Round Start
+
+The "Round Start" is happen at the "Freeze Time" end.
+
+Many of the coders does think that the "Round Start" and "New Round" is the same event and doing a things that is related to the "New Round" in "Round Start" but this is incorrect. Some of the coders especially in the past have used the "RoundTime" event to detect the "Round Start", but again this is inefficient method (the details can be found in the "New Round" section of the article).
+
+The correct method that can be used to detect the "Round Start" is shown below:
+PHP Code:
+register_logevent("logevent_round_start", 2, "1=Round_Start") 
+
+4. Round End
+
+The "Round End" is happen right at the moment when one of the teams is completed objectives: all players in the opposite team is killed, all hostages is rescued, time of the round is up, etc.
+
+Some of the coders does think that the "Round End" and "New Round" is the same event and doing a things that is related to the "New Round" in the "Round End" but this is incorrect.
+
+The correct method that can be used to detect the "Round End" is shown below:
+PHP Code:
+register_logevent("logevent_round_end", 2, "1=Round_End") 
+
+Still confused?
+
+Still confused and don't really sure which from the above events should be used in your plugin? Review the below examples that may help you to understand the things better.
+The "New Round" event can be used to move a spawn point entities or to play a music for a players if a freeze time is too long.
+The "Player Spawn" can be used to alter a player's properties like start health, weapons, etc.
+The "Round Start" can be used to create your own "buytime" for a plugins that provide a purchasable items or when you want to create a surprise item.
+The "Round End" can be used to protect a players with a godmode until the "New Round" or to create a quick minigame until the "New Round".

Damaged Soul's Message Logging plugin.txt

@@ -0,0 +1,543 @@
+Message Logging 1.17
+by Damaged Soul
+
+AMX Mod X Version: 1.75 and above
+Supported Mods: All
+
+Description
+This plugin allows for the logging of any or all messages sent by the HL engine or mod (such as DeathMsg, CurWeapon, etc) It also allows these messages to be filtered by entity.
+
+Information that is logged includes:
+Message name
+Number of message arguments
+Message ID
+Message destination (i.e. Broadcast, One, All, etc)
+Message origin
+Entity that received the message
+Entity classname
+Entity netname
+Every argument value and type
+Required Modules
+Fakemeta
+
+Usage
+Console Commands
+amx_msglog <command> [argument]
+Displays help for logging engine/mod messages when no command is given
+Commands:
+start [msg name or id]
+Starts logging given message or all if no argument
+stop [msg name or id]
+Stops logging given message or all if no argument
+list [page]
+Displays list of messages and their logging status
+Cvars
+amx_ml_filter [Default Value: 1]
+Allows for filtering messages by entity index
+Set this to the index of the entity for which you want to log messages
+If this is set to 0, message logging will be done for all entities
+amx_ml_logmode [Default Value: 1]
+Determines where to log message information
+Set this to 0 to log information to the standard AMX Mod X log file
+Set this to 1 to log information to a separate file (messages.log) in the log directory
+Examples
+To log the DeathMsg message:
+amx_msglog start DeathMsg OR amx_msglog start 83
+To stop logging the DeathMsg message:
+amx_msglog stop DeathMsg OR amx_msglog stop 83
+To log all messages except the DeathMsg message:
+amx_msglog start
+amx_msglog stop DeathMsg OR amx_msglog stop 83
+To log messages only sent to third player of the server:
+amx_ml_filter 3
+To log messages sent to all entities:
+amx_ml_filter 0
+
+
+/* Message Logging 1.17 by Damaged Soul
+
+   AMX Mod X Version: 1.75 and above
+   Supported Mods: All
+   
+   This file is provided as is (no warranties).
+  
+   ***************
+   * Description *
+   ***************
+   This plugin allows for the logging of any or all messages sent by the HL engine or mod (such as 
+   DeathMsg, CurWeapon, etc) It also allows these messages to be filtered by entity.
+   
+   Information that is logged includes:
+      - Message name
+      - Number of message arguments
+      - Message ID
+      - Message destination (i.e. Broadcast, One, All, etc)
+      - Message origin
+      - Entity that received the message
+      - Entity classname
+      - Entity netname
+      - Every argument value and type
+   
+   ********************
+   * Required Modules *
+   ********************
+   Fakemeta
+   
+   *********
+   * Usage *
+   *********
+   Console Commands:
+      amx_msglog <command> [argument]
+         - Displays help for logging engine/mod messages when no command is given
+         - Commands:
+              start [msg name or id]
+                 - Starts logging given message or all if no argument
+              stop [msg name or id]
+                 - Stops logging given message or all if no argument
+              list [page]
+                 - Displays list of messages and their logging status
+   
+   Cvars:
+      amx_ml_filter [Default Value: 1]
+         - Allows for filtering messages by entity index
+         - Set this to the index of the entity for which you want to log messages
+         - If this is set to 0, message logging will be done for all entities
+
+      amx_ml_logmode [Default Value: 1]
+         - Determines where to log message information
+         - Set this to 0 to log information to the standard AMX Mod X log file
+         - Set this to 1 to log information to a separate file (messages.log) in the log directory
+
+   Examples:
+      To log the DeathMsg message:
+         amx_msglog start DeathMsg OR amx_msglog start 83
+
+      To stop logging the DeathMsg message:
+         amx_msglog stop DeathMsg OR amx_msglog stop 83
+	
+      To log all messages except the DeathMsg message:
+         amx_msglog start
+         amx_msglog stop DeathMsg OR amx_msglog stop 83
+
+      To log messages only sent to third player of the server:
+         amx_ml_filter 3
+
+      To log messages sent to all entities:
+         amx_ml_filter 0
+
+   *******************
+   * Version History *
+   *******************
+   1.17 [Feb. 11, 2007]
+      - Fixed: Long arguments were being reported as bytes (Thanks XxAvalanchexX)
+      
+   1.16 [Oct. 4, 2006]
+      - Fixed: String arguments of messages that contained format paramaters (such as %s) caused
+               runtime error 25 (thanks sawce :avast:)
+      - Tabs and new-lines in string arguments of messages are now converted to ^t and ^n
+ 
+   1.15 [July 4, 2006]
+      - Now uses the Fakemeta module instead of Engine
+      - Now uses vformat instead of the deprecated format_args when logging information
+      - Very minor optimizations
+
+   1.11 [May 11, 2006]
+      - Fixed: String arguments of messages were being logged as numbers
+
+   1.10 [Apr. 23, 2006]
+      - Minor optimizations including the use of pcvar natives to improve performance a bit
+      - Much of the logged text has been rewritten in an attempt to make it more like the Half-Life
+        log standard
+      - Now when using the start or stop commands on a specified message, both the message name and
+        ID are printed instead of just whatever was given as the argument
+      - Added: amx_ml_logmode cvar for controlling where to log message information
+      - Fixed: When no arguments were given to amx_msglog, usage information was not printed
+
+   1.03 [Oct. 26, 2004]
+      - Public release
+      - Fixed: Entity filter wasn't actually checking for valid entities correctly (thanks JGHG)
+
+   1.02 [Oct. 25, 2004]
+      - Fixed: If logging had been started for a message, stopped, then started again, same message
+               was logged twice.
+      - Fixed: If message name or ID was invalid, started/stopped logging all messages instead
+
+   1.01 [Oct. 23, 2004]
+      - Fixed: List command was not reporting correct logging status
+      - Fixed: Filter was incorrectly filtering messages if amx_ml_filter was 0
+
+   1.00 [Oct. 19, 2004]
+      - Initial version
+*/
+
+#include <amxmodx>
+#include <amxmisc>
+#include <fakemeta>
+
+// Plugin information constants
+new const PLUGIN[] = "Message Logging"
+new const AUTHOR[] = "Damaged Soul"
+new const VERSION[] = "1.16"
+
+#define MAX_ENGINE_MESSAGES   63  // Max messages reserved by engine (DO NOT MODIFY)
+#define MAX_POSSIBLE_MESSAGES 255 // Max possible messages for mod, is 255 really the limit?
+
+#define MSGLOG_STOPPED        0	  // Logging status: Stopped
+#define MSGLOG_STARTED        1	  // Logging status: Started
+
+// Cvar pointers
+new g_cvarFilter, g_cvarLogMode
+
+// Filename of separate log file for message info
+new const LOGFILE_NAME[] = "messages.log"
+
+// Is message currently being hooked for logging?
+new bool:g_msgLogging[MAX_POSSIBLE_MESSAGES + 1] = {false}
+// Is message registered to message_forward?
+new bool:g_msgRegistered[MAX_POSSIBLE_MESSAGES + 1] = {false}
+// Stores the names of messages, indexed by message ID
+new g_msgCache[MAX_POSSIBLE_MESSAGES + 1][32]
+
+// Max messages allowed by mod
+new g_maxMessages = MAX_ENGINE_MESSAGES
+
+new const NULL_STR[] = "<NULL>"
+
+/* Initialize plugin; Register commands and cvars */
+public plugin_init()
+{
+	register_plugin(PLUGIN, VERSION, AUTHOR)
+	
+	g_cvarFilter = register_cvar("amx_ml_filter", "1")
+	g_cvarLogMode = register_cvar("amx_ml_logmode", "1")
+	
+	register_concmd("amx_msglog", "cmd_msglog", ADMIN_ADMIN, 
+			"<command> [argument] - displays help for logging engine/mod messages")
+
+	g_maxMessages = generate_msg_table()
+}
+
+/* Handles command amx_msglog */
+public cmd_msglog(id, level, cid) {
+	if (!cmd_access(id, level, cid, 1))
+		return PLUGIN_HANDLED
+	
+	new argCmd[6]
+	read_argv(1, argCmd, 5)
+	remove_quotes(argCmd)
+	
+	if (equali(argCmd, "start") || equali(argCmd, "stop")) // start or stop commands
+	{
+		new argMsg[32]
+		read_argv(2, argMsg, 31)
+		remove_quotes(argMsg)
+		
+		new msgid = str_to_msgid(argMsg)
+		
+		if (is_msg_valid(msgid))
+		{
+			new status = get_msglog_status(msgid)
+			
+			if (argCmd[2] == 'a') // start <message>
+			{
+				if (status == MSGLOG_STOPPED)
+				{
+					set_msglog_status(msgid, MSGLOG_STARTED)
+					log_msgf("Logging started for message (%s ^"%d^")", g_msgCache[msgid], msgid)
+				}
+				else
+					console_print(id, "Logging has already been started for message (%s ^"%d^")", g_msgCache[msgid], msgid)
+			}
+			else // stop <message>
+			{
+				if (status == MSGLOG_STARTED)
+				{
+					set_msglog_status(msgid, MSGLOG_STOPPED)
+					log_msgf("Logging stopped for message (%s ^"%d^")", g_msgCache[msgid], msgid)
+				}
+				else
+					console_print(id, "Logging has already been stopped for message (%s ^"%d^")", g_msgCache[msgid], msgid)
+			}
+		}
+		else
+		{
+			// If msg name or ID isn't blank, then at this point we have an invalid msg
+			if (argMsg[0])
+			{
+				console_print(id, "%s is not a valid message name or ID", argMsg)
+				return PLUGIN_HANDLED
+			}
+			
+			if (argCmd[2] == 'a') // start
+			{
+				set_msglog_status(0, MSGLOG_STARTED)
+				log_msgf("Logging started for all messages")
+			}
+			else // stop
+			{
+				set_msglog_status(0, MSGLOG_STOPPED)
+				log_msgf("Logging stopped for all messages")
+			}
+		}
+	}
+	else if (equali(argCmd, "list")) // list command
+	{
+		new argStart[4]
+		new start = read_argv(2, argStart, 3) ? str_to_num(argStart) : 1
+		
+		if (start < 1)
+			start = 1
+		else if (start > g_maxMessages)
+			start = g_maxMessages
+			
+		new end = start + 9
+		if (end > g_maxMessages)
+			end = g_maxMessages
+			
+		new logstatus[8], msgname[32]
+		
+		console_print(id, "^n------------ Message Logging Statuses -------------")
+		console_print(id, "     %-31s   %s", "Message Name", "Status")
+		
+		for (new i = start; i <= end; i++)
+		{
+			copy(msgname, 31, g_msgCache[i])
+			
+			if (!msgname[0])
+				copy(msgname, 31, "<Unknown>")
+			
+			copy(logstatus, 7, g_msgLogging[i] ? "LOGGING" : "IDLE")
+			
+			console_print(id, "%3d: %-31s   %s", i, msgname, logstatus)
+		}
+		
+		console_print(id, "Entries %d - %d of %d", start, end, g_maxMessages)
+		
+		if (end < g_maxMessages)
+			console_print(id, "-------- Use 'amx_msglog list %d' for more --------", end + 1)
+		else
+			console_print(id,"-------- Use 'amx_msglog list 1' for beginning --------")
+		
+	}
+	else
+	{
+		// Display usage information
+		console_print(id, "Usage:  amx_msglog <command> [argument]")
+		console_print(id, "Valid commands are: ")
+		
+		console_print(id, "   start [msg name or id] - Starts logging given message or all if no argument")
+		console_print(id, "   stop [msg name or id]  - Stops logging given message or all if no argument")
+		console_print(id, "   list [page]            - Displays list of messages and their logging status")
+	}
+	
+	return PLUGIN_HANDLED
+}
+
+/* Forward for hooked messages */ 
+public message_forward(msgid, msgDest, msgEnt) {
+	if (!g_msgLogging[msgid]) return PLUGIN_CONTINUE
+	
+	new entFilter = get_pcvar_num(g_cvarFilter)
+	
+	/* If value of amx_ml_filter isn't a valid entity index (0 is accepted in order to log ALL)
+	   Then stop all logging */
+	if (entFilter != 0 && !pev_valid(entFilter)) {
+		set_msglog_status(0, MSGLOG_STOPPED)
+			
+		log_msgf("Logging stopped for all messages because entity index ^"%d^" is not valid", entFilter)
+		return PLUGIN_CONTINUE
+	}
+	
+	// If not filtering by entity and the receiver entity doesn't match the filter, don't log message
+	if (entFilter != 0 && msgEnt != 0 && msgEnt != entFilter)
+		return PLUGIN_CONTINUE
+
+	new msgname[32], id[4], argcount, dest[15], Float:msgOrigin[3], entStr[7], entClassname[32], entNetname[32]
+	
+	// Get message name
+	copy(msgname, 31, g_msgCache[msgid])
+	
+	// If message has no name, then set the name to message ID
+	if (!msgname[0])
+	{
+		num_to_str(msgid, id, 3)
+		copy(msgname, 31, id)
+	}
+	
+	// Get number of message arguments
+	argcount = get_msg_args()
+	
+	// Determine the destination of the message
+	switch (msgDest) {
+		case MSG_BROADCAST:
+			copy(dest, 9, "Broadcast")
+		case MSG_ONE:
+			copy(dest, 3,  "One")
+		case MSG_ALL:
+			copy(dest, 3,  "All")
+		case MSG_INIT:
+			copy(dest, 4,  "Init")
+		case MSG_PVS:
+			copy(dest, 3,  "PVS")
+		case MSG_PAS:
+			copy(dest, 3,  "PAS")
+		case MSG_PVS_R:
+			copy(dest, 12, "PVS Reliable")
+		case MSG_PAS_R:
+			copy(dest, 12, "PAS Reliable")
+		case MSG_ONE_UNRELIABLE:
+			copy(dest, 14, "One Unreliable")
+		case MSG_SPEC:
+			copy(dest, 4,  "Spec")
+		default:
+			copy(dest, 7,  "Unknown")
+	}
+	
+	// Get the origin of the message (only truly valid for PVS through PAS_R)
+	get_msg_origin(msgOrigin)
+	
+	// Get the receiving entity's classname and netname
+	if (msgEnt != 0) {
+		num_to_str(msgEnt, entStr, 6)
+		pev(msgEnt, pev_classname, entClassname, 31)
+		pev(msgEnt, pev_netname, entNetname, 31)
+		
+		if (!entNetname[0])
+			copy(entNetname, 31, NULL_STR)
+	} else {
+		copy(entStr, 6, NULL_STR)
+		copy(entClassname, 6, NULL_STR)
+		copy(entNetname, 6, NULL_STR)
+	}
+	
+	// Log message information (MessageBegin)
+	log_msgf("MessageBegin (%s ^"%d^") (Destination ^"%s<%d>^") (Args ^"%d^") (Entity ^"%s^") (Classname ^"%s^") (Netname ^"%s^") (Origin ^"%f %f %f^")", 
+		msgname, msgid, dest, msgDest, argcount, entStr, entClassname, entNetname, msgOrigin[0], msgOrigin[1], msgOrigin[2])
+	
+	static str[256]
+	
+	// Log all argument data
+	if (argcount > 0)
+	{
+		for (new i = 1; i <= argcount; i++) {
+			switch (get_msg_argtype(i)) {
+				case ARG_BYTE:
+					log_msgf("Arg %d (Byte ^"%d^")", i, get_msg_arg_int(i))
+				case ARG_CHAR:
+					log_msgf("Arg %d (Char ^"%d^")", i, get_msg_arg_int(i))
+				case ARG_SHORT:
+					log_msgf("Arg %d (Short ^"%d^")", i, get_msg_arg_int(i))
+				case ARG_LONG:
+					log_msgf("Arg %d (Long ^"%d^")", i, get_msg_arg_int(i))
+				case ARG_ANGLE:
+					log_msgf("Arg %d (Angle ^"%f^")", i, get_msg_arg_float(i))
+				case ARG_COORD:
+					log_msgf("Arg %d (Coord ^"%f^")", i, get_msg_arg_float(i))
+				case ARG_STRING:
+				{
+					get_msg_arg_string(i, str, 255)
+					
+					replace_all(str, 254, "^t", "^^t")
+					replace_all(str, 254, "^n", "^^n")
+					replace_all(str, 254, "%", "%%")
+					
+					log_msgf("Arg %d (String ^"%s^")", i, str)
+				}
+				case ARG_ENTITY:
+					log_msgf("Arg %d (Entity ^"%d^")", i, get_msg_arg_int(i))
+				default:
+					log_msgf("Arg %d (Unknown ^"%d^")", i, get_msg_arg_int(i))
+			}
+		}
+	}
+	else
+	{
+		log_msgf("Message contains no arguments")
+	}
+	
+	// Log that the message ended (MessageEnd)
+	log_msgf("MessageEnd (%s ^"%d^")", msgname, msgid)
+	
+	return PLUGIN_CONTINUE
+}
+
+/***************** Other Functions *****************/
+
+/* Fills g_msgCache with message names for faster look up
+   Return value: Number of messages that are valid */
+generate_msg_table() {	
+	for (new i = MAX_ENGINE_MESSAGES + 1; i <= MAX_POSSIBLE_MESSAGES; i++)
+	{
+		// Store the message name in the cache for faster lookup
+		if (!get_user_msgname(i, g_msgCache[i], 31))
+			return i - 1
+	}
+	
+	return MAX_POSSIBLE_MESSAGES
+}
+
+/* Returns true if msgid is a valid message */
+bool:is_msg_valid(msgid)
+{
+	return (msgid > 0 && msgid <= g_maxMessages)
+}
+
+/* Returns message ID from string */
+str_to_msgid(const str[]) {
+	new n = str_to_num(str)
+	
+	if (n <= 0 )
+		return get_user_msgid(str)
+		
+	return n
+}
+
+/* Gets logging status of message */
+get_msglog_status(msgid)
+{
+	return g_msgLogging[msgid] ? MSGLOG_STARTED : MSGLOG_STOPPED
+}
+
+/* Sets logging status of message
+   If msgid = 0, status will be applied to all messages */
+set_msglog_status(msgid, status)
+{	
+	if (msgid > 0) // Individual message
+	{
+		g_msgLogging[msgid] = (status == MSGLOG_STARTED)
+		if (!g_msgRegistered[msgid]) 
+		{
+			register_message(msgid, "message_forward")
+			g_msgRegistered[msgid] = true
+		}
+
+	}
+	else // ALL messages
+	{
+		for (new i = 1; i <= g_maxMessages; i++) 
+		{
+			g_msgLogging[i] = (status == MSGLOG_STARTED)
+			if (status == MSGLOG_STARTED) 
+			{
+				if (!g_msgRegistered[i]) 
+				{
+					register_message(i, "message_forward")
+					g_msgRegistered[i] = true
+				}
+			}
+		}
+	}	
+}
+
+/* Writes messages to log file depending on value of amx_ml_logmode */ 
+log_msgf(const fmt[], {Float,Sql,Result,_}:...)
+{		
+	static buffer[512]
+	vformat(buffer, 511, fmt, 2)
+	
+	if (get_pcvar_num(g_cvarLogMode))
+		log_to_file(LOGFILE_NAME, buffer)
+	else
+		log_amx(buffer)
+}
+

Fake Forwards.txt

@@ -0,0 +1,203 @@
+Your plugin has many forwards?
+with this example you can create forward like register_forward of fakemeta module.
+I know that other way is CreateMultiForward but this can be a another option.
+
+PHP Code:
+#include <amxmodx>
+
+enum
+{
+    Fake_Connect = 0,
+    Fake_Disconnect,
+    Fake_ChangeName,
+    Fake_PutInServer
+}
+
+new Array:g_fakeforwards_type
+new Array:g_fakeforwards_num
+
+public plugin_precache() 
+{
+    register_plugin("Fake Forwards", "1.0", "ReymonARG")
+
+    g_fakeforwards_num = ArrayCreate(1, 1)
+    g_fakeforwards_type = ArrayCreate(1, 1)
+    
+}
+
+// We need to register the call for the forwards
+public plugin_natives()
+{
+    // Librery
+    register_library("fake_forwards")
+    
+    // Natives
+    register_native("register_fakeforward", "_register_event")
+    register_native("unregister_fakeforward", "_unregister_event")
+}
+
+public _register_event(plugin, params)
+{
+    // Are correct the params? return
+    if( params != 2 )
+        return -1
+    
+    static type, g_callout[33], forwards_num
+    type = get_param(1)
+    get_string(2, g_callout, 32)
+    
+    // Here We create the Forward.
+    switch( type )
+    {
+        // So some forwards have diferent out, so we need this to create diferent styles.
+        case Fake_Connect: forwards_num = CreateOneForward(plugin, g_callout, FP_CELL)
+        case Fake_Disconnect : forwards_num = CreateOneForward(plugin, g_callout, FP_CELL)
+        case Fake_ChangeName : forwards_num = CreateOneForward(plugin, g_callout, FP_CELL, FP_STRING)
+        case Fake_PutInServer : forwards_num = CreateOneForward(plugin, g_callout, FP_CELL)
+        default: return -1
+    }
+    
+    // Can create the forward? Return.
+    if( forwards_num == -1 )
+        return -1
+    
+    // Save the type of the forward and the num.
+    ArrayPushCell(g_fakeforwards_type, type)
+    ArrayPushCell(g_fakeforwards_num, forwards_num)
+    
+    return forwards_num
+}
+
+// Well i think that this dont is good, But i will try to better this part.
+public _unregister_event(plugin, params)
+{
+    // Its param = 1 ? return.
+    if( params != 1 )
+        return -1
+    
+    static i, fwd_id
+    fwd_id = get_param(1)
+    
+    // Found the forward and delete.
+    for( i = 0; i < ArraySize( g_fakeforwards_num ); i++)
+    {
+        if( ArrayGetCell(g_fakeforwards_num, i) == fwd_id )
+        {
+            // Delete forward
+            DestroyForward(fwd_id)
+            
+            // And items.
+            ArrayDeleteItem(g_fakeforwards_type, i)
+            ArrayDeleteItem(g_fakeforwards_num, i)
+            
+            return 1
+        }
+    }
+    
+    return 0
+}
+
+public client_connect(id)
+{
+    static i, null_id
+    
+    // Well this is the mechanism to exec the forwards.
+    for( i = 0; i < ArraySize( g_fakeforwards_num ); i++)
+    {
+        // If item type is Fake_Connect ?
+        if( ArrayGetCell(g_fakeforwards_type, i) == Fake_Connect )
+        {
+            // Exec the forward.
+            ExecuteForward(ArrayGetCell(g_fakeforwards_num, i), null_id, id)
+        }
+    }
+}
+
+public client_disconnect(id)
+{
+    static i, null_id
+    for( i = 0; i < ArraySize( g_fakeforwards_num ); i++)
+    {
+        if( ArrayGetCell(g_fakeforwards_type, i) == Fake_Disconnect )
+        {
+            ExecuteForward(ArrayGetCell(g_fakeforwards_num, i), null_id, id)
+        }
+    }
+}
+
+public client_infochanged(id)
+{
+    static oldname[32], newname[32], i, null_id
+    get_user_name(id, oldname, 31)
+    get_user_info(id, "name", newname, 31)
+    
+    if( !equal(oldname, newname) )
+    {
+        for( i = 0; i < ArraySize( g_fakeforwards_num ); i++)
+        {
+            if( ArrayGetCell(g_fakeforwards_type, i) == Fake_ChangeName )
+            {
+                ExecuteForward(ArrayGetCell(g_fakeforwards_num, i), null_id, id, newname)
+            }
+        }
+    }
+}
+
+public client_putinserver(id)
+{
+    static i, null_id
+    for( i = 0; i < ArraySize( g_fakeforwards_num ); i++)
+    {
+        if( ArrayGetCell(g_fakeforwards_type, i) == Fake_PutInServer )
+        {
+            ExecuteForward(ArrayGetCell(g_fakeforwards_num, i), null_id, id)
+        }
+    }
+} 
+And Example for recibe the forwards.
+
+PHP Code:
+#include <amxmodx>
+
+#pragma library fake_forwards
+
+enum Fake_Forwards
+{
+    Fake_Connect = 0,
+    Fake_Disconnect,
+    Fake_ChangeName,
+    Fake_PutInServer
+}
+
+native register_fakeforward(Fake_Forwards:type, const out[])
+native unregister_fakeforward(fwd_id)
+
+public plugin_init() 
+{
+    register_plugin("Forward Recive", "1.0", "ReymonARG")
+    
+    register_fakeforward(Fake_Connect, "fw_client_connect")
+    register_fakeforward(Fake_Disconnect, "fw_client_disconnect")
+    register_fakeforward(Fake_ChangeName, "fw_client_changename")
+    register_fakeforward(Fake_PutInServer, "fw_client_putinserver")
+}
+
+public fw_client_connect(id)
+{
+    server_print("Client %d Connecting", id)
+}
+
+public fw_client_disconnect(id)
+{
+    server_print("Client %d Disconnect", id)
+}
+
+public fw_client_changename(id, const newname[])
+{
+    server_print("Client %d Change name to %s", id, newname)
+}
+
+public fw_client_putinserver(id)
+{
+    server_print("Client %d Connect", id)
+} 

Finding Entities.txt

@@ -0,0 +1,82 @@
+Introduction
+It is sometimes necessary to find an entity in the world for some reason. For example, you may need to find a button in the world, and then remove it (this example will be covered later). This article will explain how to do so.
+
+Functions
+There are a number of functions built into AMX Mod X / AMXX Modules that allow you to find entities. For a complete list, please consult this page: http://www.amxmodx.org/funcwiki.php?search=find_ent&go=search
+
+(As of last edit, these are the functions included):
+
+find_ent_by_class
+find_ent_by_model
+find_ent_by_owner
+find_ent_by_target
+find_ent_by_tname
+find_ent_in_sphere
+find_sphere_class
+find_ent_by_class
+<Function is included in Engine>
+
+This function allows you to find an entity based on it's classname. All entities have classnames. For example, a player's classname is "player", while a button is either "func_button" or "func_rot_button".
+
+To find an entity using this, one would simply use the following:
+
+find_ent_by_class(-1,"classname_to_find");
+Note : Index is -1 because that's the invalid entity index. We start from the invalid one so we can get all the entities, if you start from a different index, all entities with a lower index will be ignored.
+
+find_ent_by_model
+<Function is included in Engine>
+
+This function can be used to find an entity based on its model. Some entities do not have models, meaning they cannot be found using this method. Also, it is, most of the time, better to use another type of ent finding, as this can be highly inaccurate and be broken by something as simple as a model changing plugin. This function also takes into account the class name, and is generally used more for isolating a certain model from a set of classnames (ex you have 3 grenades, with different models, and want to find 1 of them)
+
+To find an entity using this, one would use the following:
+
+find_ent_by_model(-1,"classname_to_find","model_to_find")
+find_ent_by_owner
+<Function is included in Engine>
+
+This function can be used to find an entity based on an owner. For example, if there is a player in the world, and you want to find if he has thrown a grenade out, you would use this and check for "grenade" entities that's owner is the player. Note: planted C4 (in CS) also have "grenade" classname.
+
+To find an entity using this, one would use the following:
+
+find_ent_by_owner(-1,"classname_to_find",owner_id,0);
+Notice the last parameter. This is a mode to find in.
+
+find_ent_by_target
+<Function is included in Engine>
+
+This function allows one to find an entity based on its target. This function also checks for classname.
+
+To find an entity using this, one would use the following:
+
+find_ent_by_target(-1,"classname_to_find");
+find_ent_by_tname
+<Function is included in Engine> This essentially functions the same as find_ent_by_target.
+
+find_ent_in_sphere
+<Function is included in Engine>
+
+This function can be used to find an entity within a certain distance of another entity. This can be quite handy to, for example, see if a player is around another player, and then deal damage or slap that player. This is effectively a shortcut to using find_ent_by_class and get_distance(_f) together.
+
+To find an entity using this, one would use the following:
+
+find_ent_in_sphere(-1,location_of_ent_vector,radius_float);
+find_sphere_class
+This function is probably the most complex of all the find_ent functions. This allows you to find an entity inside a certain radius of another entity, with a certian classname. This is effectively a shortcut to using find_ent_by_class & get_distance & entity_get_string(ent,EV_SZ_classname... or find_ent_in_sphere & entity_get_string(ent,EV_SZ_classname...
+
+To find an entity using this, one would use the following:
+
+new entlist[513];
+find_sphere_class(0,"classname_to_find",radius_float,entlist,512,origin_vector);
+Also, note that origin_vector and the first parameter (_aroundent) should not both be specified. If _aroundent is specified as 0, origin_vector is used. If origin_vector is not specified, or is 0, then _aroundent is used.
+
+Looping
+If, for example, one wants to loop one of these, it is quite simple to do so.
+
+Example:
+
+while((ent = find_ent_by_class(ent,"classname_to_find")) != 0)
+{
+	// do whatever
+}
+This will find every entity with classname "classname_to_find" and then execute the "// do whatever" code every time it finds one.
+

Half-Life 1 Events, Registering, Using, Reaing.txt

@@ -0,0 +1,90 @@
+Introduction
+
+This tutorial will cover the correct ways to register, use, and read events. It is written to address beginners new to PAWN language. So lets begin:
+
+Part 1: Registering Events
+
+Registering events is quite easy. Just use register_event in the plugin_init() function to make that event usable in your code.
+
+
+e.x.:
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+public plugin_init() {
+    register_plugin("Events", "1.0", "Rolnaaba")
+    register_event("DeathMsg", "Death", "a", "3!0")
+}
+when using register_event the first parameter is the event to be registered (which in this case is the “DeathMsg” event, which is called whenever anyone dies) the second is the function to be called when this even happens (which in this case is “Death”), the third parameter are the flags (which in this case is flag “a” (global event), for more information on flags check your amxmodx.inc), the fourth parameter are the restrictions. In this case the restrictions are as follows: the 3 argument (which is whether the killshot was a headshot or not), Cannot (“!”) equal “0”. (this means the kill shot must be a headshot for the function to be called upon)
+Here is the code from amxmodx.inc concerning register_event:
+Code:
+/* Registers event on which a given function will be called
+* Flags:
+* "a" - global event.
+* "b" - specified.
+* "c" - send only once when repeated to other players.
+* "d" - call if is send to dead player.
+* "e" - to alive.
+* Examples for conditions:
+* "2=c4" - 2nd parameter of message must be sting "c4".
+* "3>10" - 3rd parameter must be greater then 10.
+* "3!4" - 3rd must be different from 4.
+* "2&Buy" - 2nd parameter of message must contain "Buy" substring.
+* "2!Buy" - 2nd parameter of message can't contain "Buy" substring. */
+native register_event(const event[],const function[],const flags[],cond[]="", ... );
+Part 2: Using Events
+
+Using an event is even easier than calling it. All you do is register the event you wish to use then on the function you set, then execute what you wish to do.
+Lets say you want to create a chat message (sent to everybody on the server) that says “someone has died by a headshot”
+
+e.x.:
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+public plugin_init() {
+    register_plugin("Events", "1.0", "Rolnaaba")
+    register_event("DeathMsg", "Death", "a", "3!0")
+}
+
+public Death() {
+    client_print(0, print_chat, “Someone has died by a headshot”)
+}
+
+Part 3: reading the data that event collect
+
+Most events have special data that is collected when that event occurs in game. Lets use the “DeathMsg” event as an example. This event is called whenever someone dies. The data it collects is as follows: (1) The Killer’s ID, (2) The Victim’s ID, (3) Was Kill A Headshot or Not, (4) Weapon Name that issued the Kill. (check out “HL1 Events and their data” in the Helpful Links Section at the beginning of this tutorial for more information on all events and their data). This means we can use the read_data function to get this data.
+e.x.:
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+public plugin_init() {
+    register_plugin("Events", "1.0", "Rolnaaba")
+    register_event("DeathMsg", "Death", "a", “3!0”)
+}
+
+public Death() {
+    new victim = read_data(2)
+    client_print(victim, print_chat, “You died by a headshot”)
+}
+This would get the ID of the person killed (new victim = read_data(2)) and print “You died by a headshot” in their chat, when the “DeathMsg” event is called. You use read_data(2) since Victim ID is the second pack of data collected during this event. If we had written:
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+public plugin_init() {
+    register_plugin("Events", "1.0", "Rolnaaba")
+    register_event("DeathMsg", "Death", "a", “3!0”)
+}
+
+public Death() {
+    new victim = read_data(1)
+    client_print(victim, print_chat, “You died by a headshot”)
+}
+This would have printed “You died by a headshot” in the chat of the killer’s screen since we used read_data(1) to read the first pack of data, which in this event is the killers ID, and not read_data(2) (the victims ID).

Half-Life 1 List of Events.txt

@@ -0,0 +1,1947 @@
+Introduction
+In AMX Mod X you are able to hook in-game messages/events with register_message / register_event. Here are the list of messages/events and their arguments which can be read with get_msg_arg_* / read_data.
+
+
+See the Advanced Scripting article for more on events and messages.
+See messages.inc and message_const.inc from amxmodx/scriptong/include folder or Messaging functions and Message constants for full messages control including blocking, argument alteration and much more.
+Type meta game in the server console to list messages for the current mod.
+Damaged Soul's Message Logging plugin for AMX Mod X can be used to log messages and their parameters on a live server.
+
+
+ADStop
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+Note: No Information is available for this message.
+Note: This message has no arguments.
+
+Name:	ADStop
+Structure:	
+
+
+AlienInfo
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+AllowSpec
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Half-Life: Opposing Force • Team Fortress Classic
+
+This message changes whether or not "SPECTATE" appears on the change team menu. It is sent whenever the allow_spectators CVar is changed, with its new value sent as the byte.
+
+Note: This changes how the change team menu appears, but spectating functionality is based on the actual CVar value.
+
+Name:	AllowSpec
+Structure:	
+byte	Allowed
+
+
+AmmoPickup
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message temporarily draws HUD numerical ammo amount and corresponding ammo HUD icon in the middle of the right side of the screen.
+
+Note: Draw time depends on the hud_drawhistory_time client CVar value.
+Note: See CS Weapons Information for more information.
+
+Name:	AmmoPickup
+Structure:	
+byte	AmmoID
+byte	Ammount
+
+
+AmmoShort
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+AmmoX
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the green bar indicator in the HUD weapons list. It also updates HUD backpack ammo number in the lower right corner of the screen if the given ammo type is compatible with the current weapon.
+
+Note: See CS Weapons Information for more information.
+
+Name:	AmmoX
+Structure:	
+byte	AmmoID
+byte	Ammount
+
+
+ArmorType
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message draws/removes the helmet HUD icon. If flag is set to 1, the helmet HUD icon will be drawn (located right on the armor icon).
+
+Name:	ArmorType
+Structure:	
+byte	Flag
+
+
+BalanceVar
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+BarTime
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message draws a HUD progress bar which is filled from 0% to 100% for the time Duration seconds. Once the bar is fully filled it will be removed from the screen automatically.
+
+Note: Set Duration to 0 to hide the bar.
+
+Name:	BarTime
+Structure:	
+short	Duration
+
+
+BarTime2
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+The message is the same as BarTime, but StartPercent specifies how much of the bar is (already) filled.
+
+Note: Display time can be calculated with this formula: (1 - (StartPercent / 100)) / Duration
+
+Name:	BarTime2
+Structure:	
+short	Duration
+short	StartPercent
+
+
+Battery
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the icon and numerical armor value on the HUD.
+
+Name:	Battery
+Structure:	
+short	Armor
+
+
+Bench
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+BlinkAcct
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message makes a player's money display flash rapidly, a total of BlinkAmt times.
+
+Name:	BlinkAcct
+Structure:	
+byte	BlinkAmt
+
+
+BlipList
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+BloodPuff
+Supported Mods:	Day of Defeat
+
+This message creates a puff of blood at the specified coordinates.
+
+
+
+Name:	BloodPuff
+Structure:	
+coord	CoordX
+coord	CoordY
+coord	CoordZ
+
+
+BombDrop
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message is sent when the bomb is dropped or planted by a player.
+
+The first three arguments are the origin of the dropped bomb. The last argument is set to 0 if the bomb was dropped due to voluntary dropping or death/disconnect. It is set to 1 if the bomb was planted, which will trigger the round timer to hide. It also will show the dropped bomb on the Terrorist team's radar in the location specified by the first three arguments.
+
+Name:	BombDrop
+Structure:	
+coord	CoordX
+coord	CoordY
+coord	CoordZ
+byte	Flag
+
+
+BombPickup
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message just tells the clients that the bomb has been picked up. It will cause the dropped bomb to disappear from the Terrorist team's radar.
+
+Note: This message has no arguments.
+
+Name:	BombPickup
+Structure:	
+
+
+BotProgress
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message is sent when CZ's bots are learning a new map. It displays a progress bar in the middle of the screen, with some header text. The bar doesn't move, and you can't do anything while the bar is displayed. This is a different style of progress bar than from the BarTime event. This really doesn't display well in CS.
+
+Note: Flag can be 0 (update bar), 1 (create new bar), or 2 (remove bar). When using flag 0, send all arguments. When using flag 1, send only Flag and Header. When using flag 2, send only Flag.
+
+Name:	BotProgress
+Structure:	
+byte	Flag
+byte	Progress
+string	Header
+
+
+BotVoice
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message displays (or hides) the voice icon above a user's head and the talking icon on the right side of the screen. This is called by CZ for bots; it's not called for regular players, although you can specify a regular player (non-bot) for the PlayerIndex. Status is 1 for talking, or 0 for not talking.
+
+Name:	BotVoice
+Structure:	
+byte	Status
+byte	PlayerIndex
+
+
+Brass
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message creates a brass shell. Used, for example, by the AWP, after firing.
+
+Name:	Brass
+Structure:	
+byte	MessageID
+coord	StartX
+coord	StartY
+coord	StartZ
+coord	VelocityX?
+coord	VelocityY?
+coord	VelocityZ?
+coord	UnknownX
+coord	UnknownY
+coord	UnknownZ
+angle	Rotation
+short	ModelIndex
+byte	BounceSoundType
+byte	Life
+byte	PlayerID
+
+
+BuildSt
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+BuyClose
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message forces the buy menu to close. This is not called when the player manually closes the buy menu; it's only called when the game forces them to do so (e.g. walking outside of the buy zone, getting killed, etcetera).
+
+Note: This message has no arguments.
+
+Name:	BuyClose
+Structure:	
+
+
+Camera
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+CameraMouse
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+CameraView
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+CancelProg
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+CapMsg
+Supported Mods:	Day of Defeat
+
+This displays a message like "Player captured the Allied plaza for the Axis". An example PointName is POINT_CAEN_AXISPLAZA.
+
+Name:	CapMsg
+Structure:	
+byte	PlayerID
+string	PointName
+byte	TeamID
+
+
+CbElec
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+ClanTimer
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+ClCorpse
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat
+
+This message spawns a player's corpse. ModelName is the player's model name, for example: "leet". Delay is a delay before animation playback, which can be a negative value.
+
+Note: Coord and Delay is multiplied by 128.
+Note: In CS, argument #10 is always equal to 0.
+
+See CS Team Constants for team indices constants list.
+Name:	ClCorpse
+Structure:	
+string	ModelName
+long	CoordX
+long	CoordY
+long	CoordZ
+coord	Angle0
+coord	Angle1
+coord	Angle2
+long	Delay
+byte	Sequence
+byte	ClassID?
+byte	TeamID
+byte	PlayerID
+
+
+ClientAreas
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+ClScript
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Concuss
+Supported Mods:	Team Fortress Classic • Half-Life Deathmatch • Counter-Strike • Counter-Strike: Condition Zero
+
+This message creates screen shake effect similar to the TFC concussion grenade effect.
+
+Note: In all mods except TFC, this message requires to be registered by using EngFunc_RegUserMsg.
+
+Name:	Concuss
+Structure:	
+byte	amount
+
+
+Countdown
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+CreateBlood
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+Crosshair
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message draws/removes a crosshair. If Flag is set to 1 the crosshair will be drawn.
+
+Note: This crosshair looks not like the regular one, but like the one that is drawn in spectator mode.
+
+Name:	Crosshair
+Structure:	
+byte	Flag
+
+
+CTFScore
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+CurMarker
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+CurWeapon
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the numerical magazine ammo count and the corresponding ammo type icon on the HUD.
+
+Note: See CS Weapons Information for more information on Counter-Strike weapons.
+
+Name:	CurWeapon
+Structure:	
+byte	IsActive
+byte	WeaponID
+byte	ClipAmmo
+
+
+CustomIcon
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+CZCareer
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message supplies certain updates to the player regarding Condition Zero single-player missions.
+
+Note: See the CZCareer page for more information.
+Note: Using an invalid type has no repercussions whatsoever. Therefore, you can use this to make your own custom communications (you can send any number of arguments of any type after the first string).
+Note: The Type argument is case-sensitive.
+Note: This event does nothing in CS and CZ multiplayer.
+
+Name:	CZCareer
+Structure:	
+string	Type
+*	Parameters
+
+
+CZCareerHUD
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message displays certain HUD elements regarding Condition Zero single-player missions.
+
+Note: See the CZCareerHUD page for more information.
+Note: Using an invalid type has no repercussions whatsoever. Therefore, you can use this to make your own custom communications (you can send any number of arguments of any type after the first string).
+Note: The Type argument is case-sensitive.
+Note: This event has some limited functionality in CS and CZ multi-player (albeit better in CZ).
+
+Name:	CZCareerHUD
+Structure:	
+string	Type
+*	Parameters
+
+
+Damage
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message is sent when a player takes damage, to display the red locational indicators. The last three arguments are the origin of the damage inflicter or victim origin if inflicter isn't found. DamageType is a bitwise value which usually consists of a single bit.
+
+Note: To capture this message, you should use "b" as the third parameter in the register_event() function.
+
+Name:	Damage
+Structure:	
+byte	DamageSave
+byte	DamageTake
+long	DamageType
+coord	CoordX
+coord	CoordY
+coord	CoordZ
+
+
+DeathMsg
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This event is fired to all players (MSG_ALL or MSG_BROADCAST) to notify them of a death. This generates the HUD message the client sees in the upper right corner of their screen.
+It also prints the console text message "KillerName killed VictimName with TruncatedWeaponName" or "*** KillerName killed VictimName with a headshot from TruncatedWeaponName ***"
+
+Note: This message has different parameters depending upon the mod.
+Note: KillerID may not always be a Player ID. It would be 0 if a player died from fall/acid/radiation/fire/etc damage/lack of oxygen or from touch to a "trigger_hurt" entity, in which cases TruncatedWeaponName will be "worldspawn" and "trigger_hurt" respectively.
+Note: For vehicle kills, TruncatedWeaponName could be "vehicle", "tank", etc.
+Note: In some mods, TruncatedWeaponName is "teammate" for a team kill, which shows a green skull in the HUD message.
+
+Name:	DeathMsg
+Structure:	
+byte	KillerID
+byte	VictimID
+string	TruncatedWeaponName
+
+
+Counter-Strike
+Note: TruncatedWeaponName doesn't contain a "weapon_" prefix. See CS Weapons Information for more information.
+Note: For a grenade kill, TruncatedWeaponName isn't "hegrenade", but rather "grenade", which is the actual classname of a thrown grenade.
+
+Name:	DeathMsg
+Structure:	
+byte	KillerID
+byte	VictimID
+byte	IsHeadshot
+string	TruncatedWeaponName
+
+
+Day of Defeat
+Name:	DeathMsg
+Structure:	
+byte	KillerID
+byte	VictimID
+byte	WeaponID
+
+
+DebugCSP
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+DelEntHier
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+DelParts
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Detpack
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+EditPS
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+EndRnd
+Supported Mods:	Ricochet
+
+Note: No Information is available for this message.
+
+EntHier
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Feign
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+FlagIcon
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+FlagTimer
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+FlashBat
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the flashlight battery charge on the HUD.
+
+Name:	FlashBat
+Structure:	
+byte	ChargePercentage
+
+
+Flashlight
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the flashlight state and battery charge on the HUD. If Flag is set to 1 the flashlight HUD icon will be shown as active.
+
+Name:	Flashlight
+Structure:	
+byte	Flag
+byte	ChargePercent
+
+
+Fog
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Natural Selection • Sven Co-op
+
+Note: mp_Fog 1 for fog in Counter-Strike
+
+Name:	Fog
+Structure:	
+byte	FogValue
+byte	FogValue
+byte	Unknown
+
+
+ForceCam
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message is sent whenever mp_forcecam or mp_forcechasecam are changed, with their new values passed. There is presumably a third CVar that this tracks, but which one is currently unknown. Note that this message doesn't actually change any of the spectating rules for the client.
+
+Note: Even if mp_forcechasecam is set to 2, it is sent by this message as 1.
+
+Name:	ForceCam
+Structure:	
+byte	ForcecamValue
+byte	ForcechasecamValue
+byte	Unknown
+
+
+Frags
+Supported Mods:	Day of Defeat
+
+This message sets a player's kills, as seen on the scoreboard. This message is only sent for the killer.
+
+Name:	Frags
+Structure:	
+byte	PlayerID
+short	Kills
+
+
+Frozen
+Supported Mods:	Ricochet
+
+Note: No Information is available for this message.
+
+GameMode
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message informs the client of the current game mode.
+
+Name:	GameMode
+Structure:	
+byte	Game mode
+
+
+GameRules
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+GameStatus
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+GameTitle
+Supported Mods:	Deathmatch Classic • Half-Life: Opposing Force • Half-Life Deathmatch
+
+Display game title (gametitle) - 0 is No and 1 is Yes. If write_byte 1, then Half-Life will be displayed.
+Note: This only works for Half-life
+
+
+Name:	GameTitle
+Structure:	
+byte	0 or 1
+
+
+GargSplash
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+Geiger
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message signals the client to notify the player of the radiation level through special sound signals. Distance is the distance to the hazard area.
+
+Name:	Geiger
+Structure:	
+byte	Distance
+
+
+Gib
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+HandSignal
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+Health
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the numerical health value on the HUD.
+
+Name:	Health
+Structure:	
+byte	Health
+
+
+HideWeapon
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message hides the specified HUD elements.
+Flags:
+
+  1   (1<<0)  -  crosshair, ammo, weapons list
+  2   (1<<1)  -  flashlight, +
+  4   (1<<2)  -  ALL
+  8   (1<<3)  -  radar, health, armor, +
+ 16   (1<<4)  -  timer, +
+ 32   (1<<5)  -  money, +
+ 64   (1<<6)  -  crosshair
+128   (1<<7)  -  +
+Symbol + mean that an additional crosshair will be drawn. That crosshair looks exactly like the one from Crosshair message.
+
+Name:	HideWeapon
+Structure:	
+byte	Flags
+
+
+HLTV
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat
+
+This message is sent for HLTV and is unique for each round-start.
+On new round is fired 2 messages:
+
+// reset all players health for HLTV
+MESSAGE_BEGIN( MSG_SPEC, gmsgHLTV );
+WRITE_BYTE( 0 );   // 0 = all players
+WRITE_BYTE( 100 | 128 );
+MESSAGE_END();
+
+// reset all players FOV for HLTV
+MESSAGE_BEGIN( MSG_SPEC, gmsgHLTV );
+WRITE_BYTE( 0 );   // all players
+WRITE_BYTE( 0 );
+MESSAGE_END();
+Name:	HLTV
+Structure:	
+byte	ClientID
+byte	Flags
+
+
+HostageK
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message temporarily draws a blinking red dot on the CT players' radar when a hostage is killed.
+
+Name:	HostageK
+Structure:	
+byte	HostageID
+
+
+HostagePos
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message draws/updates the blue mark on the CT players' radar which indicates the corresponding hostage's position.
+
+Note: It is called with Flag set to 1 on player HUD full update.
+
+Name:	HostagePos
+Structure:	
+byte	Flag
+byte	HostageID
+coord	CoordX
+coord	CoordY
+coord	CoordZ
+
+
+HudColor
+Supported Mods:	Half-Life: Opposing Force
+
+This message sets HudColor. Set HUD color in RGB.
+Note: This only works for OP4. Affects weapon pick-ups, health, armor, and ammo.
+
+
+Name:	HudColor
+Structure:	
+byte	0-255 RED
+byte	0-255 GRN
+byte	0-255 BLU
+
+
+HudText
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message prints HUD text.
+
+Note: Prints message with specified style in titles.txt with small signs (like in HL)
+
+Name:	HudText
+Structure:	
+string	TextCode
+byte	InitHUDstyle
+
+
+HudText2
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+HudTextArgs
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message prints HUD text.
+
+Note: An example of TextCode could be "#Hint_you_have_the_bomb".
+Note: Prints message with specified style in titles.txt with Big signs (CS Default)
+Note: If you have problems specifying the last two arguments, use 1 and 0 respectively.
+
+Name:	HudTextArgs
+Structure:	
+string	TextCode
+byte	InitHUDstyle
+byte	NumberOfSubMessages
+string	SubMsg
+string	SubMsg
+string	...
+
+
+HudTextPro
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message prints HUD text.
+
+Note: Prints message with specified style in titles.txt with Big signs (CS Default)
+
+Name:	HudText
+Structure:	
+string	TextCode
+byte	InitHUDstyle
+
+
+InitHUD
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message initializes the HUD.
+
+Note: This message has no arguments.
+
+Name:	InitHUD
+Structure:	
+
+
+InitObj
+Supported Mods:	Day of Defeat
+
+This message updates the flags (axis/allies/objective flags, not programming flags) displayed to the client when a point is captured.
+
+Name:	InitObj
+Structure:	
+byte	TotalObjectives
+Objective	...
+...	
+
+
+TotalObjectives represents the number of Objective sub-messages that are present. Each Objective sub-message is in the following format:
+
+Name:	Objective
+Structure:	
+short	EntityID?
+byte	ObjectiveID?
+byte	TeamID
+byte	Unknown
+byte	Unknown
+byte	Unknown
+byte	Unknown
+coord	CoordX?
+coord	CoordY?
+
+
+If a map has 5 objectives, this message will have 46 arguments (1 + 5 * 9).
+
+IssueOrder
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+ItemPickup
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message temporarily draws a corresponding item HUD icon in the middle of the right side of the screen.
+
+Note: Draw time is dependent on the hud_drawhistory_time client CVar value.
+
+Name:	ItemPickup
+Structure:	
+string	ItemName
+
+
+Items
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+ItemStatus
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message notifies the client about carried items.
+Example of some item bits:
+
+1   (1<<0)  -  nightvision goggles
+2   (1<<1)  -  defusal kit
+Name:	ItemStatus
+Structure:	
+byte	ItemsBitSum
+
+
+ListPS
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Location
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message is sent when a player changes zones on a map.
+
+Name:	Location
+Structure:	
+byte	PlayerId
+string	LocationName
+
+
+MapList
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+MapMarker
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+MiniMap
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Money
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message updates the amount of money on the HUD. If the Flag is 1, the amount of money added will also be displayed.
+
+Name:	Money
+Structure:	
+long	Amount
+byte	Flag
+
+
+Monitor
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+MOTD
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message displays the MOTD window.
+
+Note: Max. Text length is 60. A larger MOTD is sent in multiple messages. Flag will be set to 1 for the final segment.
+
+Name:	MOTD
+Structure:	
+byte	Flag
+string	Text
+
+
+NextMap
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+NexusBytes
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+NVGToggle
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message toggles night vision mode. For Flag: 1 is on, 0 is off.
+
+Name:	NVGToggle
+Structure:	
+byte	Flag
+
+
+Object
+Supported Mods:	Day of Defeat
+
+This message is sent when a player picks up certain objects. The specified sprite will be displayed on the left side of the HUD. An example Sprite is sprites/mapsprites/ae_satchel2.spr.
+
+Name:	Object
+Structure:	
+string	Sprite
+
+
+ObjScore
+Supported Mods:	Day of Defeat
+
+This message sets a player's score, as seen on the scoreboard.
+
+Name:	ObjScore
+Structure:	
+byte	PlayerID
+short	Score
+
+
+OldWeapon
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+Particles
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+PClass
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+Name:	PClass
+Structure:	
+byte	PlayerID?
+byte	Unknown
+
+
+PlayerIcon
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+PlayersIn
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+PlayHUDNot
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Playlist
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+PlyrBrowse
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+Portal
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+Powerup
+Supported Mods:	Ricochet
+
+Note: No Information is available for this message.
+
+ProfileInfo
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Progress
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+ProgUpdate
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+PShoot
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+PStatus
+Supported Mods:	Day of Defeat
+
+This message is sent along with Object when a player picks up an object. It may have other uses. When I picked up a satchel charge, the Unknown value was 5.
+
+Name:	PStatus
+Structure:	
+byte	PlayerID?
+byte	Unknown
+
+
+PTeam
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+QItems
+Supported Mods:	Deathmatch Classic
+
+Note: No Information is available for this message.
+
+Radar
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message draws/updates the dot on the HUD radar which indicates the given player position.
+
+Note: This works for teammates only.
+
+Name:	Radar
+Structure:	
+byte	PlayerID
+coord	CoordX
+coord	CoordY
+coord	CoordZ
+
+
+RampSprite
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+RandomPC
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+ReceiveW
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message tells the client which visual weather effect to be executed client side, if client's cl_weather CVar is above 0.
+
+Note: Main part of CBasePlayer::SendWeatherInfo() function that is sent in CBasePlayer :: UpdateClientData() when player offset m_fInitHUD is 1
+(right after putinserver or after fullupdate command)
+Mode: 1 is for rain effect, 2 is for snow effect
+Though mode 0 is never sent by the game itself, it removes the weather effect.
+Alternatively send mode 1 and mode 2 with judicious delays (time for effect to disappear) to make both rain and snow effect
+
+Name:	ReceiveW
+Structure:	
+byte	Mode
+
+
+ReloadDone
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+ReloadSound
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message plays generic reload sounds.
+
+Note: Setting IsNotShotgun to 1 will play weapons/generic_reload.wav
+Note: Setting IsNotShotgun to 0 will play weapons/generic_shot_reload.wav
+
+Name:	ReloadSound
+Structure:	
+byte	Volume * 255
+byte	IsNotShotgun
+
+
+ReqState
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+Note: No Information is available for this message.
+Note: This message has no arguments.
+
+Name:	ReqState
+Structure:	
+
+
+ResetFade
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+ResetHUD
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message resets the HUD.
+
+Note: This message has no arguments.
+
+Name:	ResetHUD
+Structure:	
+
+
+ResetSens
+Supported Mods:	Day of Defeat
+
+This message resets the client's sensitivity?
+
+Note: This message has no arguments.
+
+Name:	ResetSens
+Structure:	
+
+
+Reward
+Supported Mods:	Ricochet
+
+Note: No Information is available for this message.
+
+RoundState
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+RoundTime
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message updates the round timer on the HUD. Time is in seconds.
+
+Name:	RoundTime
+Structure:	
+short	Time
+
+
+SayText
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message prints say HUD text. The second argument can be a predefined string or a custom one. In the latter case, the last two arguments aren't required.
+Examples of predefined Counter-Strike string values include #Cstrike_Chat_AllDead and #Cstrike_Name_Change.
+
+Note: For #Cstrike_Name_Change String2 is an old name and String3 is a new name.
+
+Name:	SayText
+Structure:	
+byte	SenderID
+string	String1
+string	String2
+string	String3
+
+
+Scenario
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+If Active is 0, this display will be hidden. If Active is 1, this displays Sprite (valid names listed in sprites/hud.txt) to the right of the round timer with an alpha value of Alpha (100-255). If FlashRate is nonzero, then the sprite will flash from the given alpha to an alpha of 100, at a rate of FlashRate (measured in ???). This is used by CZ to display how many hostages remain unrescued, and also to display the ticking bomb when it is planted.
+
+
+Scenario message in CS, using the following parameters: 1, d_mp5navy, 150
+Note: If Active is 0, don't send any other arguments afterwards. Also, you don't need to send either short if FlashRate is just going to be 0.
+Note: This works in both CS and CZ!
+Note: In CZ (and possibly CS), if someone respawns after the bomb has been planted, their Scenario event will not work at all until the next round.
+
+Name:	Scenario
+Structure:	
+byte	Active
+string	Sprite
+byte	Alpha
+short	FlashRate
+short	FlashDelay
+
+
+Scope
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+Name:	Scope
+Structure:	
+byte	Unknown
+
+
+ScoreAttrib
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message updates the scoreboard attribute for the specified player. For the 2nd argument, 0 is nothing, (1<<0) i.e. 1 is dead, (1<<1) i.e. 2 is bomb, (1<<2) i.e. 4 is VIP, (1<<3) i.e. 8 is defuse kit.
+
+Note: Flags is a bitwise value so if VIP player is dying with the bomb the Flags will be 7 i.e. bit sum of all flags.
+
+Name:	ScoreAttrib
+Structure:	
+byte	PlayerID
+byte	Flags
+
+
+ScoreInfo
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the scoreboard with the given player's Score and Deaths. In Counter-Strike, the score is based on the number of frags and the bomb detonating or being defused. In Team Fortress Classic, the score is based on the number of kills, suicides, and captures. Day of Defeat uses ScoreShort and ObjScore instead of this message to update score and deaths.
+
+Note: In CS the 4th argument (ClassID) is always equal to 0.
+
+See CS Team Constants for team indices constants list.
+Name:	ScoreInfo
+Structure:	
+byte	PlayerID
+short	Score
+short	Deaths
+short	ClassID
+short	TeamID
+
+
+ScoreInfoLong
+Supported Mods:	Day of Defeat
+
+Note: Although Metamod lists this message, it doesn't appear to be used or even a valid message name.
+
+ScoreShort
+Supported Mods:	Day of Defeat
+
+This message updates a player's Score, Kills, and Deaths as seen on the scoreboard. This message is only sent for the victim.
+
+Note: The fifth argument appears to be the same as the refresh parameter used in dod_set_pl_deaths and was always 1 in my testing.
+
+Name:	ScoreShort
+Structure:	
+byte	PlayerID
+short	Score
+short	Kills
+short	Deaths
+short	Refresh?
+
+
+ScreenFade
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message fades the screen.
+
+Note: Duration and HoldTime is in special units. 1 second is equal to (1<<12) i.e. 4096 units.
+
+Flags (from HLSDK):
+
+FFADE_IN         0x0000 // Just here so we don't pass 0 into the function
+FFADE_OUT        0x0001 // Fade out (not in)
+FFADE_MODULATE   0x0002 // Modulate (don't blend)
+FFADE_STAYOUT    0x0004 // ignores the duration, stays faded out until new ScreenFade message received
+Name:	ScreenFade
+Structure:	
+short	Duration
+short	HoldTime
+short	Flags
+byte	ColorR
+byte	ColorG
+byte	ColorB
+byte	Alpha
+
+
+ScreenShake
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message shakes the screen.
+
+Note: All arguments is in special units. 1 second is equal to (1<<12) i.e. 4096 units.
+
+Name:	ScreenShake
+Structure:	
+short	Amplitude
+short	Duration
+short	Frequency
+
+
+SecAmmoIcon
+Supported Mods:	Team Fortress Classic • Half-Life Deathmatch • Counter-Strike • Counter-Strike: Condition Zero
+
+This message creates an icon at the bottom right corner of the screen. TFC uses it to display carried grenade icon. It is not registered in other mods, but it is still useable though.
+
+Note: icon is any sprite name from hud.txt.
+Note: this message will have effect only when sent in conjuction with SecAmmoVal message.
+
+Name:	SecAmmoIcon
+Structure:	
+string	icon
+
+
+SecAmmoVal
+Supported Mods:	Team Fortress Classic • Half-Life Deathmatch • Counter-Strike • Counter-Strike: Condition Zero
+
+It is used to show carried grenade amount in TFC; it is disabled on all other mods, but it is still useable though.
+
+Note: Slots range from 1 to 4.
+Note: Sending 0 as amount for all slots will remove the effect of this message.
+
+
+
+Name:	SecAmmoVal
+Structure:	
+byte	slot
+byte	amount
+
+
+SelAmmo
+Supported Mods:	Deathmatch Classic • Half-Life: Opposing Force • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+Note: No Information is available for this message.
+
+SendAudio
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message plays the specified audio. An example of AudioCode could be "%!MRAD_rounddraw".
+
+Name:	SendAudio
+Structure:	
+byte	SenderID
+string	AudioCode
+short	Pitch
+
+
+ServerName
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message sends the server name to a client.
+
+Name:	ServerName
+Structure:	
+string	ServerName
+
+
+ServerVar
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetFOV
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message sets the specified field of view.
+
+Name:	SetFOV
+Structure:	
+byte	Degrees
+
+
+SetGmma
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetMenuTeam
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+SetObj
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+Name:	SetObj
+Structure:	
+byte	Unknown1
+byte	Unknown2
+byte	Unknown3
+
+
+SetOrder
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetRequest
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetSelect
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetTech
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetTopDown
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetUpgrades
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+SetupMap
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+ShadowIdx
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+Note: Creates/Hides shadow beneath player.
+Note: Passing 0 as the argument will hide the shadow.
+
+Name:	ShadowIdx
+Structure:	
+long	spriteIndex
+
+
+ShieldRic
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+ShkFlash
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+ShowMenu
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message displays a "menu" to a player (text on the left side of the screen). It acts like AMXX's show_menu (in fact, this is how AMXX shows a menu).
+
+Note: Multipart should be 1 if your menu takes up multiple messages (i.e.: string is too big to fit into one). On the final message, Multipart should be 0.
+
+Name:	ShowMenu
+Structure:	
+short	KeysBitSum
+char	Time
+byte	Multipart
+string	Text
+
+
+ShowTimer
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message forces the round timer to display.
+
+Note: This message has no arguments.
+
+Name:	ShowTimer
+Structure:	
+
+
+Sky3D
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+SoundList
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+SoundNames
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+Speaksent
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+SpecFade
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+SpecHealth
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Team Fortress Classic
+
+This message updates a spectator's screen with health of the currently spectated player, on health change (on TakeDamage, doesn't seems to be sent anywhere else).
+
+Note: Previous information has been checked on cs1.6/cz only
+
+Name:	SpecHealth
+Structure:	
+byte	Health
+
+
+SpecHealth2
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message updates a spectator's screen with the name and health of the given player when player is freshly spectated.
+
+Name:	SpecHealth2
+Structure:	
+byte	Health
+byte	PlayerID
+
+
+Spectator
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Half-Life: Opposing Force • Ricochet • Sven Co-op • Team Fortress Classic
+
+This message is sent when a player becomes an observer/spectator.
+
+Note: On join to Spectators this usually is fired twice in a row.
+
+Name:	Spectator
+Structure:	
+byte	ClientID
+byte	IsSpectator
+
+
+SporeTrail
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+SRDetonate
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+SRPrimed
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+SRPrimedOff
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+StartProg
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+StartProgF
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+StartRnd
+Supported Mods:	Ricochet
+
+Note: No Information is available for this message.
+
+StartSound
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+StatsInfo
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+StatsPlayer
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+StatusIcon
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Half-Life: Opposing Force • Team Fortress Classic
+
+This message draws/removes the specified status HUD icon. For Status, 0 is Hide Icon, 1 is Show Icon, 2 is Flash Icon. Color arguments are optional and are required only if Status isn't equal to 0.
+
+Name:	StatusIcon
+Structure:	
+byte	Status
+string	SpriteName
+byte	ColorR
+byte	ColorG
+byte	ColorB
+
+
+StatusText
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Natural Selection • Team Fortress Classic • Half-Life Deathmatch
+
+This message specifies the status text format.
+
+Name:	StatusText
+Structure:	
+byte	Unknown
+string	Text
+
+
+StatusValue
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Natural Selection • Team Fortress Classic • Half-Life Deathmatch
+
+This message sends/updates the status values. For Flag, 1 is TeamRelation, 2 is PlayerID, and 3 is Health. For TeamRelation, 1 is Teammate player, 2 is Non-Teammate player, 3 is Hostage. If TeamRelation is Hostage, PlayerID will be 0 or will be not sent at all.
+Usually this is fired as a triple message, for example:
+
+{1,  2}  -  non-teammate player
+{2, 17}  -  player index is 17
+{3, 59}  -  player health is 59
+Name:	StatusValue
+Structure:	
+byte	Flag
+short	Value
+
+
+TaskTime
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message displays a secondary timer above the round timer. It is used for Condition Zero singleplayer missions.
+If Time is -1, the timer dissappears. If Time is any other negative value, it is displayed as green instead of yellow, and considered positive.
+If Active is true, timer counts down. Otherwise, it is paused.
+If Fade is above zero, the timer will slowly fade out after that many seconds have passed (even if the timer is inactive).
+
+Note: This event can only be used on missions that have an objective requiring a secondary timer!
+
+Name:	TaskTime
+Structure:	
+short	Time
+byte	Active
+byte	Fade
+
+
+TE_CUSTOM
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+TeamFull
+Supported Mods:	Half-Life: Opposing Force
+
+Note: No Information is available for this message.
+
+TeamInfo
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message sets the team information for the given player.
+
+Note: In CS TeamName is either "UNASSIGNED", "TERRORIST", "CT" or "SPECTATOR".
+
+Name:	TeamInfo
+Structure:	
+byte	PlayerID
+string	TeamName
+
+
+TeamNames
+Supported Mods:	Half-Life: Opposing Force • Natural Selection • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+Note: No Information is available for this message.
+
+TeamScore
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message updates the team score on the scoreboard.
+
+Note: This message has different parameters depending upon the mod.
+Note: In CS TeamName is either "TERRORIST" or "CT".
+
+Name:	TeamScore
+Structure:	
+string	TeamName
+short	Score
+
+
+Day of Defeat
+Name:	TeamScore
+Structure:	
+byte	TeamID
+short	Score
+
+
+TechSlots
+Supported Mods:	Natural Selection
+
+Note: No Information is available for this message.
+
+TextMsg
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message prints a custom or predefined text message.
+There does not necessarily have to be a total of 6 arguments; there could be as little as 2. For example, you can send a message with the following:
+
+Arg1: 1
+Arg2: #Game_join_ct
+Arg3: Pimp Daddy
+Name:	TextMsg
+Structure:	
+byte	DestinationType
+string	Message
+string	Submsg
+string	Submsg
+string	Submsg
+string	Submsg
+
+
+TimeEnd
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+TimeLeft
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+TimerStatus
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+ToxicCloud
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+TracerDecal
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+Train
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message displays the speed bar used for controlling a train.
+
+Note: Speed is as follows: 0 (disable display), 1 (neutral), 2 (slow speed), 3 (medium speed), 4 (maximum speed), 5 (reverse)
+
+Name:	Train
+Structure:	
+byte	Speed
+
+
+TurretLaser
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+TutorClose
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message closes all CZ-style tutor popups.
+
+Note: This message has no arguments.
+
+Name:	TutorClose
+Structure:	
+
+
+TutorLine
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+Note: No Information is available for this message.
+
+Name:	TutorLine
+Structure:	
+short	Unknown1
+short	Unknown2
+
+
+TutorState
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+Note: No Information is available for this message.
+
+Name:	TutorState
+Structure:	
+string	Unknown
+
+
+TutorText
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero
+
+This message is used to display a CZ-style tutor popup.
+
+Note: If NumberOfSubMsgs is higher than 0, there should be such amount of write_string after this byte.
+Note: TutorMessageEventId is indexed as listed in czero/tutordata.txt and starts from 0
+Note: IsDead is the message receiver alive status
+
+DEFAULT		1	// 1<<0 | GREEN  | INFO
+FRIENDDEATH	2	// 1<<1 | RED    | SKULL
+ENEMYDEATH	4	// 1<<2 | BLUE   | SKULL
+SCENARIO	8	// 1<<3 | YELLOW | INFO
+BUY		16	// 1<<4 | GREEN  | INFO
+CAREER		32	// 1<<5 | GREEN  | INFO
+HINT		64	// 1<<6 | GREEN  | INFO
+INGAMEHINT	128	// 1<<7 | GREEN  | INFO
+ENDGAME		256	// 1<<8 | YELLOW | INFO
+Name:	TutorText
+Structure:	
+string	String
+byte	NumberOfSubMsgs
+string	SubMessage
+string	...
+short	TutorMessageEventId
+short	IsDead
+short	Type
+
+
+UseSound
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+ValClass
+Supported Mods:	Team Fortress Classic
+
+Note: No Information is available for this message.
+
+VGUIMenu
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Half-Life: Opposing Force • Sven Co-op • Team Fortress Classic
+
+This message displays a predefined VGUI menu.
+
+Name:	VGUIMenu
+Structure:	
+byte	MenuID
+short	KeysBitSum
+char	Time?
+byte	Multipart?
+string	Name?
+
+
+ViewMode
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Team Fortress Classic
+
+Note: No Information is available for this message (HLSDK says this switches to first-person view, but it doesn't seem to function as so).
+Note: This message has no arguments.
+
+Name:	ViewMode
+Structure:	
+
+
+VoiceMask
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message tells a client whom they can hear over the microphone.
+
+Name:	VoiceMask
+Structure:	
+long	AudiblePlayersIndexBitSum
+long	ServerBannedPlayersIndexBitSum
+
+
+VoteMenu
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+WaveStatus
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+WaveTime
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+WeaponList
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message configures the HUD weapons list.
+
+Note: This is fired on map initialization.
+Note: SlotID starts from 0.
+
+Flags (from HLSDK):
+
+ITEM_FLAG_SELECTONEMPTY       1
+ITEM_FLAG_NOAUTORELOAD        2
+ITEM_FLAG_NOAUTOSWITCHEMPTY   4
+ITEM_FLAG_LIMITINWORLD        8
+ITEM_FLAG_EXHAUSTIBLE        16 // A player can totally exhaust their ammo supply and lose this weapon.
+Note: See CS Weapons Information for more information.
+
+Name:	WeaponList
+Structure:	
+string	WeaponName
+byte	PrimaryAmmoID
+byte	PrimaryAmmoMaxAmount
+byte	SecondaryAmmoID
+byte	SecondaryAmmoMaxAmount
+byte	SlotID
+byte	NumberInSlot
+byte	WeaponID
+byte	Flags
+
+
+WeapPickup
+Supported Mods:	Counter-Strike • Counter-Strike: Condition Zero • Day of Defeat • Deathmatch Classic • Half-Life: Opposing Force • Natural Selection • Ricochet • Sven Co-op • Team Fortress Classic • Half-Life Deathmatch
+
+This message temporarily draws the corresponding weapon HUD icon in the middle of the right side of the screen.
+
+Note: Draw time depends on the hud_drawhistory_time client CVar value.
+Note: This is fired right before weapon is picked up (notice "before").
+Note: See CS Weapons Information for more information.
+
+Name:	WeapPickup
+Structure:	
+byte	WeaponID
+
+
+Weather
+Supported Mods:	Day of Defeat
+
+Note: No Information is available for this message.
+
+WeatherFX
+Supported Mods:	Sven Co-op
+
+Note: No Information is available for this message.
+
+YouDied
+Supported Mods:	Day of Defeat
+
+This message is sent to a player when they die.

Messages (Temp Entities, Game Events, etc.).txt

@@ -0,0 +1,115 @@
+
+Old 01-13-2007 , 17:59   [TUT] Messages (Temp Entities, Game Events, etc.)
+Reply With Quote #1
+Before we begin, please be advised that this tutorial is intended for intermediate level scripters. It will not cover any basic concepts and assumes that you know the syntax of Pawn.
+
+A message is essentially the server's way of telling a client about something that should be interpreted and acted upon accordingly by the client dll. In easier terms, it works like this:
+
+Server sends small bit of information. Player's computer reads it, figures out what to do with it, then displays that to the player. In human terms, this could be compared to someone (the server) giving you a recipe (the message) and you (client / player's computer) preparing the meal. The components are not included in the recipe (message), and it is the chef (player's computer) that brings them together.
+
+Messages can serve many purposes. They can do things from make a player implode to make a user think they have more ammo. Thus, the scope of this article is naturally going to be very large and will not cover everything.
+
+The most basic part of a message is the structure. Messages are started with a "message_begin" function call, followed by "write_x" function call(s) (where x is "byte","short","coord","angle","char","string ","long" and one more that I can't remember), and concluded with a "message_end" function call. Thus, the structure is usually some variant of this:
+
+Code:
+#define FFADE_IN			0x0000		// Just here so we don't pass 0 into the function
+#define FFADE_OUT			0x0001		// Fade out (not in)
+#define FFADE_MODULATE		0x0002		// Modulate (don't blend)
+#define FFADE_STAYOUT		0x0004		// ignores the duration, stays faded out until new ScreenFade message received
+
+ message_begin(MSG_ONE_UNRELIABLE,get_user_msgid("ScreenFade"),{0,0,0},id)
+    write_short(1<<12) // fade time (1 second = 4096 = 1<<12)
+    write_short(2<<12) // hold time (how long it lasts after fading) (1 second = 4096 = 1<<12)
+    write_short(FFADE_IN) // fade type (in/out)
+    write_byte(255) // r
+    write_byte(255) // g
+    write_byte(255) // b
+    write_byte(150) // alpha / intensity
+    message_end()
+There are a few important things in this that I haven't even touched upon yet. The first one is the params of message_begin.
+
+As found in message_const (in the include directory), the options for the first param are the following:
+
+Code:
+/* Destination types for message_begin() */
+#define    MSG_BROADCAST               0        // Unreliable to all
+#define    MSG_ONE                     1        // Reliable to one (msg_entity)
+#define    MSG_ALL                     2        // Reliable to all
+#define    MSG_INIT                    3        // Write to the init string
+#define MSG_PVS                     4        // Ents in PVS of org
+#define MSG_PAS                     5        // Ents in PAS of org
+#define MSG_PVS_R                   6        // Reliable to PVS
+#define MSG_PAS_R                   7        // Reliable to PAS
+#define MSG_ONE_UNRELIABLE          8        // Send to one client, but don't put in reliable stream, put in unreliable datagram (could be dropped)
+#define    MSG_SPEC                    9        // Sends to all spectator proxies
+The most commonly used of these is MSG_BROADCAST, MSG_ONE, MSG_ALL, MSG_ONE_UNRELIABLE, and MSG_SPEC, of which the rest I've never seen in use personally.
+
+This parameter's function is to tell the engine which clients to send the message to. MSG_BROADCAST and MSG_ALL both send to ALL clients, whereas MSG_ONE and MSG_ONE_UNRELIABLE send to one client (but id, the final parameter of message_begin, must be specified in order to use this). Generally, it is better to use MSG_BROADCAST or MSG_ONE_UNRELIABLE. The reason for this is that these both send to the unreliable stream (as opposed to the reliable stream), which avoids the chance of a crash in the event that the message gets dropped. If a message is sent on the reliable channel but fails to make it to the client, the server generally crashes, or at the very best the client gets dropped.
+
+The next parameter is the type of message. There are many options for this. The two generally most used types of messages are events (like the ScreenFade one called, generally with the usage of get_user_msgid), or SVC_TEMPENTITY. Event related messages are used to artificially tell the client that an event has happened, such as the round ending, the player's health changing, weapons changing, etc. SVC_TEMPENTITY (or just temp ents for short) is used to create a temporary entity, usually to make a nice visual effect or so a group of entities don't have to be manually removed.
+
+Note that the get_user_msgid native can be cached in another forward (such as plugin_init) and then called using a variable, like this:
+
+Code:
+new g_MsgScreenFade
+
+public plugin_init()
+{
+    //...
+    g_MsgScreenFade = get_user_msgid("ScreenFade")
+    //...
+}
+
+// ...
+{
+// ...
+    message_begin(MSG_ONE_UNRELIABLE,g_MsgScreenFade,...
+The next parameter is the origin. Note that this is NOT where the message will appear if it has any visual effects, but is used for scripting so anything catching/reading it knows where the message originated from on the map. This parameter is generally unimportant.
+
+The next parameter, as already talked about, is the id of the player to send this message to. This is only needed when not using MSG_BROADCAST, MSG_ALL or MSG_SPEC, since these messages all target either everyone or a predefined set of people.
+
+Onto the next part - the writing of data. The next function call will always be a write_byte if you're using SVC_TEMPENTITY. This function will tell the engine which type of temp ent you want to make. The list is too long to post, but it can be found in message_const.inc (all of the TE_ defines).
+
+As you can see, it's quite lengthy. For the sake of this tutorial, your and my own sanity, I'm going to pick the first one to use as an example, TE_BEAMPOINTS.
+
+Here's how I'd do it:
+
+Code:
+new g_Beam
+
+public plugin_precache()
+    g_Beam = precache_model("sprites/lightning1.spr")
+
+//...
+
+    message_begin(MSG_BROADCAST,SVC_TEMPENTITY)
+    write_byte(TE_BEAMPOINTS)
+    // this is where the beginning of the beam is
+    write_coord(0) // x
+    write_coord(0) // y
+    write_coord(0) // z
+    // this is where the end of the beam is
+    write_coord(4096) // x
+    write_coord(4096) // y
+    write_coord(4096) // z
+    // this is the sprite index, as we got in plugin_precache)
+    write_short(g_Beam)
+    // this is the starting frame, it's generally best to leave this at 1
+    write_byte(1)
+    // frame rate in 0.1s
+    write_byte(10)
+    // how long it lasts in 0.1 seconds (10 for 1 second)
+    write_byte(100)
+    // line width in 0.1s
+    write_byte(10)
+    // amplitude (how much it goes off the line)
+    write_byte(10)
+    // r, g, b
+    write_byte(255)
+    write_byte(255)
+    write_byte(255)
+    // brightness
+    write_byte(255)
+    // scroll speed
+    write_byte(100)
+    message_end()

NEW DBI API (MySQL SQL).txt

@@ -0,0 +1,66 @@
+This is very important for scripters! For AMXx 0.20, I have significantly changed the SQL interface. All plugins will be rendered broken, so you will need to upgrade.
+
+If you need any help with this, just ask. I can help you convert your plugin or answer technical questions. Remember though, this is for 0.20 and you should be prepared to swap in the new code close to the release date (we will announce this).
+
+This new DBI is important because it gets rid of the shoddy interface from AMX 0.9.x. Plugin writers now get resource handles for both result sets and connections, as well as a better guarantee that the driver will not crash.
+
+To best explain this, here is a sample program:
+
+Code:
+//Create a connection
+    new Sql:mysql = dbi_connect("localhost", "dvander", "pass", "dbase")
+
+//If the connection is less than 1, it is bad   
+    if (mysql < SQL_OK) {
+        new err[255]
+        new errNum = dbi_error(mysql, err, 254)
+        server_print("error1: %s|%d", err, errNum)
+        return 1
+    }
+    
+    server_print("Connection handle: %d", mysql)
+//Run a query
+    new Result:ret = dbi_query(mysql, "INSERT INTO config (keyname, val) VALUES ('amx', 'yes')")
+
+//If the query is less than 0, it failed    
+    if (ret < RESULT_NONE) {
+        new err[255]
+        new errNum = dbi_error(mysql, err, 254)
+        server_print("error2: %s|%d", err, errNum)
+        return 1
+    }
+
+//Do a select query 
+    new Result:res = dbi_query(mysql, "SELECT * FROM config")
+
+//If the query is greater than 0, you got a handle to the result set    
+    if (res <= RESULT_NONE) {
+        new err[255]
+        new errNum = dbi_error(mysql, err, 254)
+        server_print("error3: %s|%d", err, errNum)
+        return 1
+    }
+    
+    server_print("Result handle: %d", res)
+
+//Loop through the result set   
+    while (res && dbi_nextrow(res)>0) {
+        new qry[32]
+//Get the column/field called "keyname" from the result set
+        dbi_result(res, "keyname", qry, 32)
+        server_print("result: %s", qry)
+    }
+
+//Free the result set   
+    dbi_free_result(res)
+
+//Close the connection  
+    ret = dbi_close(mysql)
+    if (ret <= RESULT_NONE) {
+        new err[255]
+        new errNum = dbi_error(mysql, err, 254)
+        server_print("error4: %s|%d", err, errNum)
+        return 1
+    }
+
+These differences are subtle and important. It means you can create nested or recursive SQL queries and not have the previous ones erased. It also gives you much better errorchecking/debugging control. You can also reference fields by name instead of number.

New AMXX Menu System.txt

@@ -0,0 +1,909 @@
+Basic Menu - for interacting within a plugin or having a player select between objects ( such as a weapon menu )
+Player Menu - for interacting with a selected player ( such as a kick menu )
+Basic Vote Menu - for getting a preference from players ( such as a mapvote menu )
+Sub-Menu - for having a menu within a menu ( such as a multilayered admin menu )
+Advanced Vote Menu - for getting a more advanced preference ( such as a Galileo's map menu )
+Multiple Menus with 1 Handler - for having multiple menus and only using a single menu_handler
+Menu Items with Callbacks - for enabling/disabling menu items ( such as a Shop menu that disables items if you don't have enough money )
+newmenus.inc - some helpful things from newmenus.inc
+End Notes - some tips with the new menus
+
+
+Basic Menu [top]
+Code:
+ #include <amxmodx>
+
+ public plugin_init()
+ {
+    //..stuff for your plugin
+
+    register_clcmd( "my_awesome_menu","AwesomeMenu" );
+    //note that we do not need to register the menu anymore, but just a way to get to it
+ }
+ //lets make the function that will make the menu
+ public AwesomeMenu( id )
+ {
+    //first we need to make a variable that will hold the menu
+    new menu = menu_create( "\rLook at this awesome Menu!:", "menu_handler" );
+    //Note - menu_create
+    //The first parameter  is what the menu will be titled ( what is at the very top )
+    //The second parameter is the function that will deal/handle with the menu ( which key was pressed, and what to do )
+
+    //Now lets add some things to select from the menu
+    menu_additem( menu, "\wI'm Selection #1", "", 0 );
+    menu_additem( menu, "\wI'm Selection #2", "", 0 );
+    menu_additem( menu, "\wI'm Secret Selection #3", "", ADMIN_ADMIN );
+    //Note - menu_additem
+    //The first parameter is which menu we will be adding this item/selection to
+    //The second parameter is what text will appear on the menu ( Note that it is preceeded with a number of which item it is )
+    //The third parameter is data that we want to send with this item
+    //The fourth parameter is which admin flag we want to be able to access this item ( Refer to the admin flags from the amxconst.inc )
+    //The fifth parameter is the callback for enabling/disabling items, by default we will omit this and use no callback ( default value of -1 ) Refer to the Menu Items with Callbacks section for more information.
+
+    //Set a property on the menu
+    menu_setprop( menu, MPROP_EXIT, MEXIT_ALL );
+    //Note - menu_setprop
+    //The first parameter is the menu to modify
+    //The second parameter is what to modify ( found in amxconst.inc )
+    //The third parameter is what to modify it to ( in this case, we are adding a option to the menu that will exit the menu. setting it to MEXIT_NEVER will disable this option )
+    //Additional note - MEXIT_ALL is the default property for MPROP_EXIT, so this is redundant
+
+    //Lets display the menu
+    menu_display( id, menu, 0 );
+    //Note - menu_display
+    //The first parameter is which index to show it to ( you cannot show this to everyone at once )
+    //The second parameter is which menu to show them ( in this case, the one we just made )
+    //The third parameter is which page to start them on
+ }
+ //okay, we showed them the menu, now lets handle it ( looking back at menu_create, we are going to use that function )
+ public menu_handler( id, menu, item )
+ {
+    //Because of the simplicity of this menu, we can switch for which item was pressed
+    //Note - this is zero-based, so the first item is 0
+    switch( item )
+    {
+        case 0:
+        {
+            client_print( id, print_chat, "Hooray! You selected the Awesome 1st Selection" );
+            
+            //Note that if we dont want to continue through the function, we can't just end with a return. We want to kill the menu first
+            menu_destroy( menu );
+            return PLUGIN_HANDLED;
+        }
+        case 1:
+        {
+            client_print( id, print_chat, "OH NO! You selected the Awesome 2nd Selection! BEWARE!" );
+        }
+        case 2:
+        {
+            client_print( id, print_chat, "You have selected the Awesome Admin Selection! Hail Teh Bail!" );
+        }
+        case MENU_EXIT:
+        {
+            client_print( id, print_chat, "You exited the menu... what a bummer!" );
+        }
+    }
+
+    //lets finish up this function by destroying the menu with menu_destroy, and a return
+    menu_destroy( menu );
+    return PLUGIN_HANDLED;
+ }
+
+Player Menu [top]
+*Note - You should have an understanding of the Basic Menu first.
+Code:
+ #include <amxmodx>
+ #include <fun>
+
+ public plugin_init()
+ {
+    //Register a way to get to your menu...
+    register_clcmd( "my_player_menu","AwesomeMenu" );
+ }
+
+ public AwesomeMenu( id )
+ {
+    //Create a variable to hold the menu
+    new menu = menu_create( "\rLook at this Player Menu!:", "menu_handler" );
+
+    //We will need to create some variables so we can loop through all the players
+    new players[32], pnum, tempid;
+
+    //Some variables to hold information about the players
+    new szName[32], szUserId[32];
+
+    //Fill players with available players
+    get_players( players, pnum, "a" ); // flag "a" because we are going to add health to players, but this is just for this specific case
+
+    //Start looping through all players
+    for ( new i; i<pnum; i++ )
+    {
+        //Save a tempid so we do not re-index
+        tempid = players[i];
+
+        //Get the players name and userid as strings
+        get_user_name( tempid, szName, charsmax( szName ) );
+        //We will use the data parameter to send the userid, so we can identify which player was selected in the handler
+        formatex( szUserId, charsmax( szUserId ), "%d", get_user_userid( tempid ) );
+
+        //Add the item for this player
+        menu_additem( menu, szName, szUserId, 0 );
+    }
+
+    //We now have all players in the menu, lets display the menu
+    menu_display( id, menu, 0 );
+ }
+
+ public menu_handler( id, menu, item )
+ {
+    //Do a check to see if they exited because menu_item_getinfo ( see below ) will give an error if the item is MENU_EXIT
+    if ( item == MENU_EXIT )
+    {
+        menu_destroy( menu );
+        return PLUGIN_HANDLED;
+    }
+
+    //now lets create some variables that will give us information about the menu and the item that was pressed/chosen
+    new szData[6], szName[64];
+    new _access, item_callback;
+    //heres the function that will give us that information ( since it doesnt magicaly appear )
+    menu_item_getinfo( menu, item, _access, szData,charsmax( szData ), szName,charsmax( szName ), item_callback );
+
+    //Get the userid of the player that was selected
+    new userid = str_to_num( szData );
+
+    //Try to retrieve player index from its userid
+    new player = find_player( "k", userid ); // flag "k" : find player from userid
+
+    //If player == 0, this means that the player's userid cannot be found
+    //If the player is still alive ( we had retrieved alive players when formating the menu but some players may have died before id could select an item from the menu )
+    if ( player && is_user_alive( player ) )
+    {
+        //Set their health to 100
+        set_user_health( player, 100 );
+    }
+
+    menu_destroy( menu );
+    return PLUGIN_HANDLED;
+ }
+
+Here is a generic player menu from ConnorMcLeod that you can use to easily add to your plugin
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+#define VERSION "0.0.1"
+#define PLUGIN "Players Menu Generic"
+
+public plugin_init()
+{
+    register_plugin( PLUGIN, VERSION, "ConnorMcLeod" );
+    register_clcmd( "say /players", "ClCmd_Menu", ADMIN_RCON );
+}
+
+public ClCmd_Menu( id, lvl, cid )
+{
+    if ( cmd_access( id, lvl, cid, 0 ) )
+    {
+        new iMenu = MakePlayerMenu( id, "Players Menu Misc", "PlayersMenuHandler" );
+        menu_setprop( iMenu, MPROP_NUMBER_COLOR, "\y" );
+        menu_display( id, iMenu );
+    }
+    return PLUGIN_HANDLED;
+}
+
+enum ( <<= 1 )
+{
+    PLMENU_OBEY_IMMUNITY = 1,
+    PLMENU_ALLOW_SELF,
+    PLMENU_ONLY_ALIVE,
+    PLMENU_NO_BOTS
+}
+
+MakePlayerMenu( id, const szMenuTitle[], const szMenuHandler[], iFlags = PLMENU_OBEY_IMMUNITY )
+{
+    new iMenu = menu_create( szMenuTitle, szMenuHandler );
+    new bool:bIsSuperAdmin;
+    if ( iFlags & PLMENU_OBEY_IMMUNITY )
+    {
+        bIsSuperAdmin = !!( get_user_flags( id ) & ADMIN_RCON );
+    }
+
+    new iPlayers[32], iNum, iPlayer, szPlayerName[32], szUserId[32];
+    new szFlags[4] = "h";
+    if ( iFlags & PLMENU_ONLY_ALIVE )
+    {
+        szFlags[++iNum] = 'a';
+    }
+    if ( flags & PLMENU_NO_BOTS )
+    {
+        szFlags[++iNum] = 'c';
+    }
+
+    get_players( iPlayers, iNum, szFlags );
+
+    for ( --iNum; iNum >= 0; iNum-- )
+    {
+        iPlayer = iPlayers[iNum];
+        get_user_name( iPlayer, szPlayerName, charsmax( szPlayerName ) );
+
+        if ( iFlags & PLMENU_OBEY_IMMUNITY && !bIsSuperAdmin
+        && ( ( get_user_flags( iPlayer ) & ADMIN_IMMUNITY ) && 
+             ( ( iFlags & PLMENU_ALLOW_SELF ) ? ( id != iPlayer ) : true ) )    )
+        {
+            menu_addtext( iMenu, szPlayerName );
+        }
+        else
+        {
+            formatex( szUserId, charsmax( szUserId ), "%d", get_user_userid( iPlayer ) );
+            menu_additem( iMenu, szPlayerName, szUserId, 0 );
+        }
+    }
+
+    return iMenu;
+}
+
+public PlayersMenuHandler_Sample( id, iMenu, iItem )
+{
+    if ( iItem == MENU_EXIT )
+    {
+        menu_destroy( iMenu );
+        return PLUGIN_HANDLED;
+    }
+
+    new szUserId[32], szPlayerName[32], iPlayer, iAccess, iCallback;
+    menu_item_getinfo( iMenu, iItem, iCallback, szUserId, charsmax( szUserId ), szPlayerName, charsmax( szPlayerName ), iCallback );
+
+    if ( ( iPlayer = find_player( "k", str_to_num( szUserId ) ) )  )
+    {
+        new szName[32];
+        get_user_name( iPlayer, szName, charsmax( szName ) );
+        client_print( id, print_chat, "You have chosen #%s %s %s", szUserId, szPlayerName, szName );
+    }
+    else
+    {
+        client_print( id, print_chat, "Player %s<%s> seems to be disconnected", szPlayerName, szAuthid );
+    }
+    menu_destroy( iMenu );
+    return PLUGIN_HANDLED;
+}
+
+
+Basic Vote Menu [top]
+*Note - You should have an understanding of the Basic Menu first.
+Code:
+ #include <amxmodx>
+
+ //This will hold the VoteMenu
+ new gVoteMenu;
+ //This will hold the votes for each option
+ new gVotes[2];
+ //This determines if a vote is already happening
+ new gVoting;
+
+ public plugin_init()
+ {
+    //Register a way to get to your vote...
+    register_clcmd( "start_vote","StartVote" );
+ }
+ public StartVote( id )
+ {
+    //If there is already a vote, don't start another
+    if ( gVoting )
+    {
+        client_print( id, print_chat, "There is already a vote going." );
+        //We return PLUGIN_HANDLED so the person does not get Unknown Command in console
+        return PLUGIN_HANDLED;
+    }
+
+    //Reset vote counts from any previous votes
+    gVotes[0] = gVotes[1] = 0;
+    //Note that if you have more than 2 options, it would be better to use the line below:
+    //arrayset( gVotes, 0, sizeof gVotes );
+
+    //Store the menu in the global
+    gVoteMenu = menu_create( "\rLook at this Vote Menu!:", "menu_handler" );
+
+    //Add some vote options
+    menu_additem( gVoteMenu, "Vote Option 1", "", 0 );
+    menu_additem( gVoteMenu, "Vote Option 2", "", 0 );
+
+    //We will need to create some variables so we can loop through all the players
+    new players[32], pnum, tempid;
+
+    //Fill players with available players
+    get_players( players, pnum );
+
+    //Start looping through all players to show the vote to
+    for ( new i; i < pnum; i++ )
+    {
+        //Save a tempid so we do not re-index
+        tempid = players[i];
+
+        //Show the vote to this player
+        menu_display( tempid, gVoteMenu, 0 );
+
+        //Increase how many players are voting
+        gVoting++;
+    }
+
+    //End the vote in 10 seconds
+    set_task(10.0, "EndVote" );
+
+    return PLUGIN_HANDLED;
+ }
+ public menu_handler( id, menu, item )
+ {
+    //If the menu was exited or if there is not a vote
+    if ( item == MENU_EXIT || !gVoting )
+    {
+        //Note were not destroying the menu
+        return PLUGIN_HANDLED;
+    }
+
+    //Increase the votes for what they selected
+    gVotes[ item ]++;
+
+    //Note were not destroying the menu
+    return PLUGIN_HANDLED;
+ }
+ public EndVote()
+ {
+    //If the first option recieved the most votes
+    if ( gVotes[0] > gVotes[1] )
+        client_print(0, print_chat, "First option recieved most votes (%d )", gVotes[0] );
+
+    //Else if the second option recieved the most votes
+    else if ( gVotes[0] < gVotes[1] )
+        client_print(0, print_chat, "Second option recieved most votes (%d )", gVotes[1] );
+
+    //Otherwise the vote tied
+    else
+        client_print(0, print_chat, "The vote tied at %d votes each.", gVotes[0] );
+
+    //Don't forget to destroy the menu now that we are completely done with it
+    menu_destroy( gVoteMenu );
+
+    //Reset that no players are voting
+    gVoting = 0;
+ }
+
+Sub-Menu [top]
+*Note - You should have an understanding of the Basic Menu first.
+Code:
+ #include <amxmodx>
+
+ public plugin_init()
+ {
+    register_clcmd( "my_awesome_menu","AwesomeMenu" );
+ }
+ public AwesomeMenu( id )
+ {
+    new menu = menu_create( "\rLook at this awesome Menu!:", "menu_handler" )
+
+    menu_additem( menu, "\wI'm Selection #1", "", 0 );
+    menu_additem( menu, "\wGo to SubMenu", "", 0 );
+
+    menu_display( id, menu, 0 );
+ }
+ public menu_handler( id, menu, item )
+ {
+    switch( item )
+    {
+        case 0:
+        {
+            client_print( id, print_chat, "Hooray! You selected the Awesome 1st Selection" );
+        }
+        case 1:
+        {
+            //Send them to the submenu
+            SubMenu( id );
+        }
+        case MENU_EXIT:
+        {
+            //Do nothing?
+        }
+    }
+
+    menu_destroy( menu );
+    return PLUGIN_HANDLED;
+ }
+ SubMenu( id )
+ {
+    //Note that we will be using a different menu handler
+    new menu = menu_create( "\rLook at this awesome Sub-Menu!:", "submenu_handler" )
+
+    menu_additem( menu, "\wI'm Sub-Selection #1", "", 0 );
+    menu_additem( menu, "\wI'm Sub-Selection #2", "", 0 );
+
+    menu_display( id, menu, 0 );
+ }
+ public submenu_handler( id, menu, item )
+ {
+    switch( item )
+    {
+        case 0:
+        {
+            client_print( id, print_chat, "Hooray! You selected the Awesome 1st Sub-Selection" );
+        }
+        case 1:
+        {
+            client_print( id, print_chat, "OH NO! You selected the Awesome 2nd Sub-Selection! BEWARE!" );
+        }
+        case MENU_EXIT:
+        {
+            //If they are still connected
+            if ( is_user_connected( id ) )
+                //Lets send them back to the top menu
+                AwesomeMenu( id );
+        }
+    }
+
+    menu_destroy( menu );
+    return PLUGIN_HANDLED;
+ }
+
+Advanced Vote Menu [top]
+*Note - You should have an understanding of the Basic Menu and the Basic Vote Menu first.
+Code:
+ #include <amxmisc>
+ #include <fun>
+
+ //How many different votes there will be in the menu
+ #define MAX_VOTEIDS 7
+
+ //How much "weight" a normal player's vote is worth
+ #define WEIGHT_PLAYER 1
+ //How much "weight" an admin's vote is worth
+ #define WEIGHT_ADMIN 2
+
+ new gVoteMenu;
+ new gVotes[MAX_VOTEIDS];
+ new gVoting;
+
+ //This will store the voteids
+ new gVoteID[MAX_VOTEIDS];
+
+ public plugin_init()
+ {
+    register_clcmd( "start_vote","StartVote" );
+ }
+ public StartVote( id )
+ {
+    if ( gVoting )
+    {
+        client_print( id, print_chat, "There is already a vote going." );
+        return PLUGIN_HANDLED;
+    }
+
+    //Reset vote counts from any previous votes
+    arrayset( gVotes, 0, sizeof gVotes );
+
+    gVoteMenu = menu_create( "\rWho should get 255 Health?", "menu_handler" );
+
+    //Here you can do whatever you want to add your voteids.
+    //We are going to use players for the example
+    new players[32], pnum, tempid;
+    get_players( players, pnum, "a" );
+
+    //Variable for if the player was added to the vote
+    new bool:player_added[33], voteid_count;
+
+    new szName[32], szVoteId[10];
+
+    //Loop through until we get enough voteids or run out of players
+    while( voteid_count < MAX_VOTEIDS && voteid_count < pnum )
+    {
+        //Get a random player
+        tempid = players[ random( pnum ) ];
+
+        //If they haven't been added yet
+        if ( !player_added[tempid] )
+        {
+            get_user_name( tempid, szName, charsmax( szName ) );
+
+            //We are setting the data to the voteid number
+            num_to_str( voteid_count, szVoteId, charsmax( szVoteId ) );
+
+            menu_additem( gVoteMenu, szName, szVoteId, 0 );
+
+            //Make sure we do not add them again
+            player_added[tempid] = true;
+
+            //Save the voteid as the user id for the player
+            gVoteID[voteid_count] = get_user_userid( tempid );
+
+            //Go to the next voteid
+            voteid_count++;
+        }
+    }
+
+    //Now we have all the voteids
+
+    for ( new i; i < pnum; i++ )
+    {
+        //Save a tempid so we do not re-index
+        tempid = players[i];
+
+        //Show the vote to this player
+        menu_display( tempid, gVoteMenu, 0 );
+
+        //Increase how many players are voting by their weight
+        if ( is_user_admin( tempid ) )
+            gVoting += WEIGHT_ADMIN;
+        else
+            gVoting += WEIGHT_PLAYER;
+    }
+
+    set_task(10.0, "EndVote" );
+
+    return PLUGIN_HANDLED;
+ }
+ public menu_handler( id, menu, item )
+ {
+    //If the menu was exited or if there is not a vote
+    if ( item == MENU_EXIT || !gVoting )
+    {
+        return PLUGIN_HANDLED;
+    }
+
+    new szData[6], szName[64];
+    new item_access, item_callback;
+    menu_item_getinfo( menu, item, item_access, szData,charsmax( szData ), szName,charsmax( szName ), item_callback );
+
+    //Get the voteid number that was selected
+    new voteid_num = str_to_num( szData );
+
+    //Increase the votes for what they selected by weight
+    if ( is_user_admin( id ) )
+        gVotes[voteid_num] += WEIGHT_ADMIN;
+    else
+        gVotes[voteid_num] += WEIGHT_PLAYER;
+
+    return PLUGIN_HANDLED;
+ }
+ public EndVote()
+ {
+    //This will hold how many different votes were selected
+    new votes_select;
+
+    //This will hold the top 3 votes
+    new votes[3];
+
+    //This will hold the top 3 selected voteids
+    new voteid[3];
+
+    new i, j;
+
+    //Loop through all the voteids
+    for ( i=0; i<MAX_VOTEIDS; i++ )
+    {
+        //If the voteid recieved any votes
+        if ( gVotes[i] )
+        {
+            //If we are still trying to get the top 3
+            if ( votes_select < 3 )
+            {
+                //Save the data for the current voteid selected
+                votes[votes_select] = gVotes[i];
+                voteid[votes_select] = i;
+
+                //Go to the next voteid that might have been selected
+                votes_select++;
+            }
+            else
+            {
+                //Loop through all the top votes, replace any that are lower than the selected voteid
+                for ( j=0; j<3; j++ )
+                {
+                    //If this one recieved less votes
+                    if ( votes[j] < gVotes[i] )
+                    {
+                        //Change the data to the voteid with more votes
+                        votes[j] = gVotes[i];
+                        voteid[j] = i;
+
+                        //Don't need to bother looking for more
+                        break;
+                    }
+                }
+            }
+        }
+    }
+
+    //If noone voted
+    if ( !votes_select )
+    {
+        client_print(0, print_chat, "CRICKEY! No one voted!" );
+    }
+    //Else if one voteid recieved all the votes
+    else if ( votes_select == 1 )
+    {
+        //Get the player id from the voteid
+        new player = find_player( "k", voteid[0]);
+        VoteGiveHealth( player );
+    }
+    //Else if two different voteids recieved all the votes
+    else if ( votes_select == 2 )
+    {
+        //If they recieved even votes
+        if ( votes[0] == votes[1] )
+        {
+            //Give it to a random one
+            client_print(0, print_chat, "Vote has tied. Choosing random from tied votes." );
+            new player = find_player( "k", voteid[ random(2 ) ] );
+            VoteGiveHealth( player );
+        }
+
+        //Else if the first recieved the most
+        else if ( votes[0] > votes[1] )
+        {
+            //Give it to the first
+            new player = find_player( "k", voteid[ 0 ] );
+            VoteGiveHealth( player );
+        }
+
+        //Else the second recieved the most
+        else
+        {
+            //Give it to the second
+            new player = find_player( "k", voteid[ 1 ] );
+            VoteGiveHealth( player );
+        }
+    }
+    //Else there were at least 3 different votes
+    else
+    {
+        //Here you might want to do run-off voting, but well just select a random one
+        new player = find_player( "k", voteid[ random( MAX_VOTEIDS ) ] );
+        client_print(0, print_chat, "Could not determine a winner. Selecting random." );
+        VoteGiveHealth( player );
+    }
+
+    menu_destroy( gVoteMenu );
+    gVoting = 0;
+ }
+ VoteGiveHealth( id )
+ {
+    if ( is_user_alive( id ) )
+    {
+        set_user_health( id, 255 );
+        new szName[32];
+        get_user_name( id, szName, charsmax( szName ) );
+        client_print(0, print_chat, "Look that Kangaroo %s has 255 Health!", szName );
+    }
+ }
+
+Multiple Menus with 1 Handler [top]
+*Note - You should have a good understanding of the Sub Menu first.
+Code:
+ #include <amxmodx>
+
+ public plugin_init()
+ {
+    register_clcmd( "my_awesome_menu","AwesomeMenu" );
+ }
+ public AwesomeMenu( id )
+ {
+    new menu = menu_create( "\rLook at this awesome Menu!:", "menu_handler" )
+
+    //Note that our data is 'm' to know it is from the main menu
+    menu_additem( menu, "\wI'm Selection #1", "m", 0 );
+    menu_additem( menu, "\wGo to SubMenu", "m", 0 );
+
+    menu_display( id, menu, 0 );
+ }
+ SubMenu( id )
+ {
+    new menu = menu_create( "\rLook at this awesome Sub-Menu!:", "menu_handler" )
+
+    //Note that our data is 's' to know it is from the sub menu
+    menu_additem( menu, "\wI'm Sub-Selection #1", "s", 0 );
+    menu_additem( menu, "\wI'm Sub-Selection #2", "s", 0 );
+
+    menu_display( id, menu, 0 );
+ }
+ public menu_handler( id, menu, item )
+ {
+    if ( item == MENU_EXIT )
+    {
+        menu_destroy( menu );
+        return PLUGIN_HANDLED;
+    }
+
+    new szData[6], szName[64];
+    new item_access, item_callback;
+    menu_item_getinfo( menu, item, item_access, szData,charsmax( szData ), szName,charsmax( szName ), item_callback );
+
+    //Switch based on the first character of the data ( the 'm' or the 's')
+    switch( szData[0] )
+    {
+        //All our main menu data will be handled in this case
+        case 'm':
+        {
+            switch( item )
+            {
+                case 0:
+                {
+                    client_print( id, print_chat, "Hooray! You selected the Awesome 1st Selection" );
+                }
+                case 1:
+                {
+                    SubMenu( id );
+                }
+            }
+        }
+        //All our sub menu data will be handled in this case
+        case 's':
+        {
+            switch( item )
+            {
+                case 0:
+                {
+                    client_print( id, print_chat, "Hooray! You selected the Awesome 1st Sub-Selection" );
+                }
+                case 1:
+                {
+                    client_print( id, print_chat, "OH NO! You selected the Awesome 2nd Sub-Selection! BEWARE!" );
+                }
+            }
+
+            //Note that this is still only for our sub menu
+            AwesomeMenu( id );
+        }
+    }
+
+    menu_destroy( menu );
+    return PLUGIN_HANDLED;
+ }
+
+Menu Items with Callbacks [top]
+*Note - You should have a good understanding of the Player Menu first.
+*Additional Note - This example uses a respawn function specific for Counter-Strike
+Code:
+ #include <amxmodx>
+ #include <hamsandwich>
+
+ //Create a global variable to hold our callback
+ new g_MenuCallback;
+
+ public plugin_init()
+ {
+    register_clcmd( "my_player_menu","RespawnMenu" );
+
+    //Create our callback and save it to our variable
+    g_MenuCallback = menu_makecallback( "menuitem_callback" );
+    //The first parameter is the public function to be called when a menu item is being shown.
+ }
+ public RespawnMenu( id )
+ {
+    new menu = menu_create( "\rRevive Player Menu!:", "menu_handler" );
+
+    new players[32], pnum, tempid;
+    new szName[32], szUserId[10];
+    get_players( players, pnum );
+
+    for ( new i; i < pnum; i++ )
+    {
+        tempid = players[i];
+        get_user_name( tempid, szName, charsmax( szName ) );
+        formatex( szUserId, charsmax( szUserId ), "%d", get_user_userid( tempid ) );
+
+        //Add the item for this player with the callback
+        menu_additem( menu, szName, szUserId, 0, g_MenuCallback );
+        //Note that the last parameter that we usually omit is now filled with the callback variable
+
+    }
+
+    menu_display( id, menu, 0 );
+ }
+ //This is our callback function. Return ITEM_ENABLED, ITEM_DISABLED, or ITEM_IGNORE.
+ public menuitem_callback( id, menu, item )
+ {
+    //Create some variables to hold information about the menu item
+    new szData[6], szName[64];
+    new item_access, item_callback;
+
+    //Get information about the menu item
+    menu_item_getinfo( menu, item, item_access, szData,charsmax( szData ), szName,charsmax( szName ), item_callback );
+    //Note - item_callback should be equal to g_MenuCallback
+
+    //Get which player the item is for
+    new userid = str_to_num( szData );
+    new player = find_player( "k", userid ); // flag "k" : find player from userid
+
+    //If the user is alive, we want to disable reviving them
+    if ( is_user_alive( tempid ) )
+    {
+        return ITEM_DISABLED;
+    }
+
+    //Otherwise we can just ignore the return value
+    return ITEM_IGNORE;
+    //Note that returning ITEM_ENABLED will override the admin flag check from menu_additem
+ }
+ public menu_handler( id, menu, item )
+ {
+    if ( item == MENU_EXIT )
+    {
+        menu_destroy( menu );
+        return PLUGIN_HANDLED;
+    }
+
+    new szData[6], szName[64];
+    new item_access, item_callback;
+    menu_item_getinfo( menu, item, item_access, szData,charsmax( szData ), szName,charsmax( szName ), item_callback );
+
+    //Get the id of the player that was selected
+    new userid = str_to_num( szData );
+    new player = find_player( "k", userid ); // flag "k" : find player from userid
+
+    //If the player is not alive
+    //Note - you should check this again in the handler function because the player could have been revived after the menu was shown
+    if ( !is_user_alive( player ) )
+    {
+        //Respawn them
+        ExecuteHamB( Ham_CS_RoundRespawn, player );
+    }
+
+    menu_destroy( menu );
+    return PLUGIN_HANDLED;
+ }
+
+
+
+newmenus.inc [top]
+Code:
+//The following defines are to be used with the native menu_setprop
+#define MPROP_PERPAGE   1       /* Number of items per page ( param1 = number, 0=no paginating, 7=default ) */
+#define MPROP_BACKNAME  2       /* Name of the back button ( param1 = string ) */
+#define MPROP_NEXTNAME  3       /* Name of the next button ( param1 = string ) */
+#define MPROP_EXITNAME  4       /* Name of the exit button ( param1 = string ) */
+#define MPROP_TITLE     5       /* Menu title text ( param1 = string ) */
+#define MPROP_EXIT      6       /* Exit functionality ( param1 = number, see MEXIT constants ) */
+#define MPROP_NOCOLORS  8       /* Sets whether colors are not auto ( param1 = number, 0=default ) */
+#define MPROP_NUMBER_COLOR  10  /* Color indicator to use for numbers ( param1 = string, "\r"=default ) */
+
+//These two defines are to be used when changing a menu's MPROP_EXIT value
+#define MEXIT_ALL       1       /* Menu will have an exit option ( default )*/
+#define MEXIT_NEVER     -1      /* Menu will not have an exit option */
+
+//For more details about the following natives, check your actual newmenus.inc
+native menu_create( const title[], const handler[], ml=0 );
+native menu_makecallback( const function[]);
+native menu_additem( menu, const name[], const info[]="", paccess=0, callback=-1 );
+native menu_pages( menu );
+native menu_items( menu );
+native menu_display( id, menu, page=0 );
+native menu_find_id( menu, page, key );
+native menu_item_getinfo( menu, item, &access, info[], infolen, name[]="", namelen=0, &callback );
+native menu_item_setname( menu, item, const name[]);
+native menu_item_setcmd( menu, item, const info[]);
+native menu_item_setcall( menu, item, callback=-1 );
+native menu_destroy( menu );
+native player_menu_info( id, &menu, &newmenu, &menupage=0 );
+native menu_addblank( menu, slot=1 );
+native menu_addtext( menu, const text[], slot=1 );
+native menu_setprop( menu, prop, ...);
+native menu_cancel( player );
+
+
+End Notes: [top]
+Most of the menu_* natives will throw errors if they are passed an invalid menu. A menu is invalid if it is -1.
+You can expand on these in many ways, like only have one menu_handler to handle more than 1 menu
+If you are using a constant menu ( doesn't change at all ) you do not need to create and destroy it each time. It is better to save it as a global.
+These examples are not completely optimized, but they are for beginners and so they are simplified.
+List of Colors for menus: ( there are no other colors available )
+White - \w
+Yellow - \y
+Red - \r
+Grey/Disabled - \d
+To align text to the right - \R
+A menu will not show if it does not have any items.
+Text and blanks can only be added after an item.
+To hide a menu ( new or old style ) one can do:
+Code:
+show_menu( id, 0, "^n", 1 );
+One can remove the Next, Back, and Exit buttons to show up to 10 items by using:
+Code:
+menu_setprop( menu, MPROP_PERPAGE, 0 );

Plugin API.txt

@@ -0,0 +1,200 @@
+There is API functionality in AMXX plugins, implemented through a set of natives. The following natives, built into the core, allow API capabilities:
+CreateMultiForward
+CreateOneForward
+ExecuteForward
+PrepareArray
+DestroyForward
+
+But what are they used for? Well, let's take a look at an example and then pull it apart to figure out how it works. Please keep in mind that an API is designed for multiple plugins, so every example will be 2 individual scripts instead of 1 (although it's possible to put them both in one)
+
+Code:
+#include <amxmodx>
+
+new Float:g_flDelay
+
+public plugin_init()
+{
+    register_plugin("API Test - Core","1.0","Hawk552")
+    
+    g_flDelay = random_float(0.1,0.5)
+    set_task(g_flDelay,"fnDoForward")
+}
+
+public fnDoForward()
+{
+    new iForward = CreateMultiForward("plugin_init_delay",ET_IGNORE,FP_FLOAT),iReturn
+    if(iForward < 0)
+        return log_amx("Forward could not be created.")
+    
+    if(!ExecuteForward(iForward,iReturn,g_flDelay))
+        return log_amx("Could not execute forward.")
+        
+    return DestroyForward(iForward)
+}
+
+Code:
+#include <amxmodx>
+
+public plugin_init()
+    register_plugin("API Test - Attachment","1.0","Hawk552")
+    
+public plugin_init_delay(Float:flDelay)
+    log_amx("Forward executed %f seconds after plugin_init.",flDelay)
+
+Now, let's pick these two apart.
+
+In the first script, the important part starts at fnDoForward. What we see is:
+
+Code:
+new iForward = CreateMultiForward("plugin_init_delay",ET_IGNORE,FP_FLOAT)
+
+CreateMultiForward and CreateOneForward (which will be addressed later) return handles that can be used for ExecuteForward and DestroyForward.
+NOTE: Difference between CreateMultiForward and CreateOneForward: multi accepts a return value and you must specify upon which condition it'll stop. Multi also sends to all plugins that have a public function after the name of const name[], as shown below. CreateOneForward requires a plugin id, and automatically ignores the return value (although you can still pass it byref)
+
+But as for the parameters:
+
+const name[] - this is the name of the public function you want to call from whatever plugin(s) specified
+stop_type - this is what the plugin should obey in terms of stopping. For example, if you register a client command "kill" and then return PLUGIN_HANDLED, it'll stop right there. This parameter allows you to specify whether or not it will stop there, and whether or not the return value from plugins called matters. The possibilities are here:
+
+Code:
+#define ET_IGNORE        0    //ignore return val
+#define ET_STOP            1    //stop on PLUGIN_HANDLED
+#define ET_STOP2        2    //same, except return biggest
+#define ET_CONTINUE        3    //no stop, return biggest
+
+In this case, we use ET_IGNORE because plugin_init never stops calling, despite what plugins return (which is why it's useless to return PLUGIN_CONTINUE/_HANDLED in plugin_init), and we want to duplicate that functionality.
+
+... - This is where the parameters of the header of the function called should be specified. In the above example, FP_FLOAT was specified. This is to let the AMXX core know that we want to send a floating point int to the functions called.
+
+Here are the possibilities for the previous section (I will explain how to pass an array/string later):
+
+Code:
+#define FP_CELL            0
+#define FP_FLOAT        1
+#define FP_STRING        2
+#define FP_ARRAY        4
+
+Next we check if iForward > 0, or if it's not we stop there and inform the server console. As said in the funcwiki, "Results will be > 0 for success.".
+
+Next, we execute the forward using ExecuteForward. Picking this function apart:
+
+forward_handle - this is the forward to call. It's the handle returned from CreateMultiForward / CreateOneForward.
+
+&ret - this is the return value, passed by reference. It is effectively the value that the function being called returns (ex. return PLUGIN_HANDLED -> &ret == 1) It usually is effected by the stop_type in CreateMultiForward.
+
+... - this is the param(s) where you can input the data that will be passed onto the function header for the function being called. In the example above, g_flDelay is passed and in the second plugin, the plugin_init_delay function recieves it in the header as Float:flDelay. NOTE: You can theoretically have infinite parameters, but they must match with the types passed into CreateOneForward / CreateMultiForward.
+
+If ExecuteForward returns 0 (false) then we stop there and inform the server of this error. Otherwise, we continue onward to DestroyForward.
+
+The next part we find is DestroyForward. The functionality for this is quite obvious, and can be used on any forward but should be used by the time plugin_end is called (or the FM forward for server shutting down) otherwise memory leaks can occur.
+
+Now, what was the point of that? Not really much, that was pretty damn useless. Here's something a little more useful:
+
+Code:
+#include <amxmodx>
+#include <fakemeta>
+
+new g_iForward
+new g_iReturn
+
+public plugin_init()
+{
+    register_plugin("API Test 2 - Core","1.0","Hawk552")
+    
+    g_iForward = CreateMultiForward("client_PreThink",ET_IGNORE,FP_CELL)
+    if(g_iForward < 0)
+        log_amx("Error creating forward")
+        
+    register_forward(FM_PlayerPreThink,"fnForwardPlayerPreThink")
+    register_forward(FM_Sys_Error,"fnForwardSysError")
+}
+
+public fnForwardPlayerPreThink(id)
+    if(!ExecuteForward(g_iForward,g_iReturn,id))
+        log_amx("Could not execute forward")
+        
+public fnForwardSysError()
+    plugin_end()
+    
+public plugin_end()
+    DestroyForward(g_iForward)
+
+Code:
+#include <amxmodx>
+
+public plugin_init()
+    register_plugin("API Test - Attachment 2","1.0","Hawk552")
+    
+public client_PreThink(id)
+    log_amx("PreThink called on %d",id)
+
+We just allowed a plugin to use client_PreThink using fakemeta without having to even create the fakemeta forward in the other plugin. On top of this, if we added another plugin to the API, it would call client_PreThink for that one too. Be careful though, it'll call it twice if you have engine included.
+
+But one thing remains unanswered: how do you pass an array/string?
+
+A special native has been implemented for this, PrepareArray. Here's an example of how to use it:
+
+Code:
+#include <amxmodx>
+#include <fakemeta>
+
+new g_iForward
+new g_iReturn
+
+public plugin_init()
+{
+    register_plugin("API Test 2 - Core","1.0","Hawk552")
+    
+    g_iForward = CreateMultiForward("client_PreThink",ET_IGNORE,FP_ARRAY)
+    if(g_iForward < 0)
+        log_amx("Error creating forward")
+        
+    register_forward(FM_PlayerPreThink,"fnForwardPlayerPreThink")
+    register_forward(FM_Sys_Error,"fnForwardSysError")
+}
+
+public fnForwardPlayerPreThink(id)
+{
+    new iRand = random(5),iArray[2]
+    iArray[0] = id
+    iArray[1] = iRand
+    
+    new iArrayPass = PrepareArray(iArray,2,0)
+    
+    if(!ExecuteForward(g_iForward,g_iReturn,iArrayPass))
+        log_amx("Could not execute forward")
+}
+        
+public fnForwardSysError()
+    plugin_end()
+    
+public plugin_end()
+    DestroyForward(g_iForward)
+
+Code:
+#include <amxmodx>
+
+public plugin_init()
+    register_plugin("API Test - Attachment 2","1.0","Hawk552")
+    
+public client_PreThink(iArray[2])
+    log_amx("PreThink called on %d, random value is %d",iArray[0],iArray[1])
+
+Regardless of the fact we could use 2 cells instead of an array, this allows client_PreThink to have a random value from 0-5 packed into the parameters (which is quite useless, again this is just an example).
+
+Now, to pick this apart:
+
+We created an array and then packed it with data. You should know how to already do this.
+
+We then use:
+
+Code:
+new iArrayPass = PrepareArray(iArray,2,0)
+
+The usage of PrepareArray is as follows:
+
+array[] - this is the array to be prepared
+size - this is the amount of cells in the array (the same amount as when declaring it, not the highest cell)
+copyback=0 - this is whether or not changing the array will result in the calling function's array being changed as well. This defaults to 0.
+
+PrepareArray returns a handle as well that can be passed into ExecuteForward under the param of FP_ARRAY or FP_STRING. The difference between these two is that FP_STRING stops reading at the null terminator (and does not need to be prepared using PrepareArray), but FP_ARRAY must be prepared and only stops reading at the "size" cell.

Regular Expressions. regex_tester.txt

@@ -0,0 +1,99 @@
+#include < amxmodx >
+#include < amxmisc >
+#include < regex >
+
+new Regex:g_pPattern = REGEX_PATTERN_FAIL;
+
+new Regex:g_pPatternFlags;
+
+public plugin_init( )
+{
+	register_plugin( "Regex Tester", "0.0.1", "Exolent" );
+	
+	register_concmd( "regex_pattern", "CmdPattern", _, "<pattern>" );
+	register_concmd( "regex_test", "CmdTest", _, "<test data>" );
+	
+	new iReturn, szError[ 128 ];
+	g_pPatternFlags = regex_compile( "^^\/(.*)\/([imsx]*)$", iReturn, szError, charsmax( szError ) );
+	
+	if( g_pPatternFlags == REGEX_PATTERN_FAIL )
+	{
+		log_amx( "Error creating pattern for patterns: %s", szError );
+	}
+}
+
+public CmdPattern( iPlayer, iLevel, iCID )
+{
+	if( !cmd_access( iPlayer, iLevel, iCID, 2 ) )
+	{
+		return PLUGIN_HANDLED;
+	}
+	
+	new szPattern[ 128 ];
+	read_args( szPattern, charsmax( szPattern ) );
+	trim( szPattern );
+	remove_quotes( szPattern );
+	
+	new szFlags[ 5 ];
+	
+	new iReturn;
+	
+	if( regex_match_c( szPattern, g_pPatternFlags, iReturn ) > 0 )
+	{
+		regex_substr( g_pPatternFlags, 1, szPattern, charsmax( szPattern ) );
+		regex_substr( g_pPatternFlags, 2, szFlags, charsmax( szFlags ) );
+	}
+	
+	new szError[ 128 ];
+	g_pPattern = regex_compile( szPattern, iReturn, szError, charsmax( szError ), szFlags );
+	
+	if( g_pPattern == REGEX_PATTERN_FAIL )
+	{
+		console_print( iPlayer, "Error with pattern: %s", szError );
+	}
+	else
+	{
+		console_print( iPlayer, "Pattern set to: %s", szPattern );
+		console_print( iPlayer, "Flags set to: %s", szFlags );
+	}
+	
+	return PLUGIN_HANDLED;
+}
+
+public CmdTest( iPlayer, iLevel, iCID )
+{
+	if( !cmd_access( iPlayer, iLevel, iCID, 2 ) )
+	{
+		return PLUGIN_HANDLED;
+	}
+	
+	if( g_pPattern == REGEX_PATTERN_FAIL )
+	{
+		console_print( iPlayer, "No pattern set. Use regex_pattern first." );
+		return PLUGIN_HANDLED;
+	}
+	
+	new szData[ 256 ];
+	read_args( szData, charsmax( szData ) );
+	trim( szData );
+	remove_quotes( szData );
+	
+	new iReturn;
+	if( regex_match_c( szData, g_pPattern, iReturn ) != -2 )
+	{
+		console_print( iPlayer, "%d matches", iReturn );
+		
+		for( new i = 0; i < iReturn; i++ )
+		{
+			regex_substr( g_pPattern, i, szData, charsmax( szData ) );
+			
+			console_print( iPlayer, "%d. ^"%s^"", ( i + 1 ), szData );
+		}
+	}
+	else
+	{
+		console_print( iPlayer, "Regex match error code %d", iReturn );
+	}
+	
+	return PLUGIN_HANDLED;
+}

Regular Expressions.txt

@@ -0,0 +1,388 @@
+Regular Expressions
+
+Introduction
+For information on what regular expressions are (or how to create them), consult the wiki.
+
+RegEx Patterns
+Here is a quick reference for patterns:
+Code:
++-------------+--------------------------------------------------------------+
+| Expression  | Description                                                  |
++-------------+--------------------------------------------------------------+
+| .           | Any character except newline.                                |
++-------------+--------------------------------------------------------------+
+| \.          | A period (and so on for \*, \(, \\, etc.)                    |
++-------------+--------------------------------------------------------------+
+| ^           | The start of the string.                                     |
++-------------+--------------------------------------------------------------+
+| $           | The end of the string.                                       |
++-------------+--------------------------------------------------------------+
+| \d,\w,\s    | A digit, word character [A-Za-z0-9_], or whitespace.         |
++-------------+--------------------------------------------------------------+
+| \D,\W,\S    | Anything except a digit, word character, or whitespace.      |
++-------------+--------------------------------------------------------------+
+| [abc]       | Character a, b, or c.                                        |
++-------------+--------------------------------------------------------------+
+| [a-z]       | a through z.                                                 |
++-------------+--------------------------------------------------------------+
+| [^abc]      | Any character except a, b, or c.                             |
++-------------+--------------------------------------------------------------+
+| aa|bb       | Either aa or bb.                                             |
++-------------+--------------------------------------------------------------+
+| ?           | Zero or one of the preceding element.                        |
++-------------+--------------------------------------------------------------+
+| *           | Zero or more of the preceding element.                       |
++-------------+--------------------------------------------------------------+
+| +           | One or more of the preceding element.                        |
++-------------+--------------------------------------------------------------+
+| {n}         | Exactly n of the preceding element.                          |
++-------------+--------------------------------------------------------------+
+| {n,}        | n or more of the preceding element.                          |
++-------------+--------------------------------------------------------------+
+| {m,n}       | Between m and n of the preceding element.                    |
++-------------+--------------------------------------------------------------+
+| ??,*?,+?,   | Same as above, but as few as possible.                       |
+| {n}?, etc.  |                                                              |
++-------------+--------------------------------------------------------------+
+| (expr)      | Capture expr for use with \1, etc.                           |
++-------------+--------------------------------------------------------------+
+| (?:expr)    | Non-capturing group.                                         |
++-------------+--------------------------------------------------------------+
+| (?=expr)    | Followed by expr.                                            |
++-------------+--------------------------------------------------------------+
+| (?!expr)    | Not followed by expr.                                        |
++-------------+--------------------------------------------------------------+
+
+Example:
+Let's try to catch a swear work, like "ass".
+We could simply make our pattern "ass" and it would match it.
+But, it would also match "glass" or "brass", so how do we fix that?
+
+We add a non-character requirement in front of ass.
+So we would do this: "\Wass", which means allow anything except for a letter before "ass".
+Now, "glass" or "brass" won't get picked, but now just "ass" won't because it requires something besides a letter in front.
+
+To fix this, we make the non-character requirement also allow nothing in front, like so: "\W*ass"
+
+We're still not done yet. What about the word "assassin"?
+That will still get picked up because it matches the first "ass" in "assassin".
+So now we have to allow nothing, or anything except a character, after it: "\W*ass\W*"
+
+Looks good, right? Now, we need to add checking for people who would type variations, like asssss or aaasssss.
+So, let's just say any number of A's and at least 2 S's: "\W*a+s{2,}\W*"
+
+One last thing is checking for non-alphabetic characters to look like those letters, like a$$.
+Well, let's see what looks alike:
+a = @, 4, /\, /-\
+s = 5, z, $
+
+Now, let's transform them into character classes:
+a = (?:[a@4]|\/\\|\/-\\)
+s = [s5z\$]
+
+We had to put A's in a non-capturing group since /\ and /-\ are more than 1 character and won't work for character classes.
+I used a non-capturing group so every A isn't put into the matches when checked.
+Also, the slashes in A's and the dollar sign in S's needed to be escaped.
+
+Add those to the pattern now:
+"\W*(?:[a@4]|\/\\|\/-\\)+[s5z\$]{2,}\W*"
+
+Finally, let's add the ignore case-sensitivity flag to allow capital letters checking:
+/\W*(?:[a@4]|\/\\|\/-\\)+[s5z\$]{2,}\W*/i
+
+That's how you create RegEx patterns, and they normally do look crazy when you're done with them so be sure to comment what they are for in case you need to go back to them later.
+
+RegEx Flags
+Flags were introduced to AMXX in version 1.8.
+
+These are the flags you can use with your patterns:
+i - Ignore case
+- Ignores case sensitivity with your pattern, so /a/i would be "a" and "A"
+m - Multilines
+- Affects ^ and $ so that they match the start/end of a line rather than the start/end of the string
+s - Single line
+- Affects . so it matches any character, even new line characters
+x - Pattern extension
+- Ignore whitespace and # comments
+
+RegEx in AMXX
+In most languages, you will see this format for the expression: /pattern/flags
+In AMXX, the pattern and flags are separated, and those slashes are taken away.
+
+So if you had this pattern: /[ch]+at/i
+It would be split into:
+- pattern: [ch]+at
+- flags: i
+
+Do not escape for new line characters (or other escapable characters) with Pawns escape character, like ^n.
+Instead, use the RegEx escape with \n.
+
+Using RegEx
+First, you'll need to include regex.inc:
+Code:
+#include <regex>
+
+These are the error codes from matching:
+Code:
+enum Regex
+{
+    REGEX_MATCH_FAIL = -2,
+    REGEX_PATTERN_FAIL,
+    REGEX_NO_MATCH,
+    REGEX_OK
+};
+
+Checking if a string matches a pattern is simple.
+Spoiler 
+Code:
+/**
+ * Matches a string against a regular expression pattern.
+ *
+ * @note                If you intend on using the same regular expression pattern
+ *                      multiple times, consider using regex_compile and regex_match_c 
+ *                      instead of making this function reparse the expression each time.
+ *
+ * @param string        The string to check.
+ * @param pattern       The regular expression pattern.
+ * @param ret           Error code, or result state of the match.
+ * @param error     Error message, if applicable.
+ * @param maxLen        Maximum length of the error buffer.
+ * @param flags     General flags for the regular expression.
+ *                      i = Ignore case
+ *                      m = Multilines (affects ^ and $ so that they match 
+ *                          the start/end of a line rather than matching the 
+ *                          start/end of the string).
+ *                      s = Single line (affects . so that it matches any character, 
+ *                          even new line characters).
+ *                      x = Pattern extension (ignore whitespace and # comments).
+ *
+ * @return              -2 = Matching error (error code is stored in ret)
+ *                      -1 = Error in pattern (error message and offset # in error and ret)
+ *                       0 = No match.
+ *                      >1 = Handle for getting more information (via regex_substr)
+ *
+ * @note                Flags only exist in amxmodx 1.8 and later.
+ * @note                You should free the returned handle (with regex_free())
+ *                      when you are done extracting all of the substrings.
+ */
+native Regex:regex_match(const string[], const pattern[], &ret, error[], maxLen, const flags[] = "");
+
+
+Example:
+Spoiler 
+Code:
+new const string[] = "123.456"
+
+new ret, error[128]
+new Regex:regex_handle = regex_match(string, "\d+\.\d+", ret, error, charsmax(error))
+
+switch(regex_handle)
+{
+    case REGEX_MATCH_FAIL:
+    {
+        // There was an error matching against the pattern
+        // Check the {error} variable for message, and {ret} for error code
+    }
+    case REGEX_PATTERN_FAIL:
+    {
+        // There is an error in your pattern
+        // Check the {error} variable for message, and {ret} for error code
+    }
+    case REGEX_NO_MATCH:
+    {
+        // Matched string 0 times
+    }
+    default:
+    {
+        // Matched string {ret} times
+        
+        // Free the Regex handle
+        regex_free(regex_handle);
+    }
+}
+
+
+You can get the individual matches (if you supplied groupings).
+Spoiler 
+Code:
+/**
+ * Returns a matched substring from a regex handle.
+ * Substring ids start at 0 and end at ret-1, where ret is from the corresponding
+ * regex_match or regex_match_c function call.
+ *
+ * @param id            The regex handle to extract data from.
+ * @param str_id        The index of the expression to get - starts at 0, and ends at ret - 1.
+ * @param buffer        The buffer to set to the matching substring.
+ * @param maxLen        The maximum string length of the buffer.
+ *
+ */
+native regex_substr(Regex:id, str_id, buffer[], maxLen);
+
+
+Example, grabbing the numbers from a SteamID:
+Spoiler 
+Code:
+new const steamID[] = "STEAM_0:1:23456"
+
+new ret, error[128]
+new Regex:regex_handle = regex_match(steamID, "^^STEAM_0:[01]:(\d+)$", ret, error, charsmax(error))
+
+if(regex_handle > REGEX_NO_MATCH)
+{
+    // 0 string ID is always the whole string that matched
+    // After 0 are the groupings
+    
+    new numbers[32]
+    regex_substr(regex_handle, 1, numbers, charsmax(numbers))
+    
+    // numbers = "23456"
+    
+    regex_free(regex_handle)
+}
+
+Compiling Patterns
+When you have a pattern that will be used more than one time, it is more efficient to compile it.
+
+Spoiler 
+Code:
+/**
+ * Precompile a regular expression.  Use this if you intend on using the 
+ * same expression multiple times.  Pass the regex handle returned here to
+ * regex_match_c to check for matches.
+ *
+ * @param pattern       The regular expression pattern.
+ * @param errcode       Error code encountered, if applicable.
+ * @param error     Error message encountered, if applicable.
+ * @param maxLen        Maximum string length of the error buffer.
+ * @param flags     General flags for the regular expression.
+ *                      i = Ignore case
+ *                      m = Multilines (affects ^ and $ so that they match 
+ *                          the start/end of a line rather than matching the 
+ *                          start/end of the string).
+ *                      s = Single line (affects . so that it matches any character, 
+ *                          even new line characters).
+ *                      x = Pattern extension (ignore whitespace and # comments).
+ *
+ * @return              -1 on error in the pattern, > valid regex handle (> 0) on success.
+ *
+ * @note                This handle is automatically freed on map change.  However,
+ *                      if you are completely done with it before then, you should
+ *                      call regex_free on this handle.
+ */
+native Regex:regex_compile(const pattern[], &ret, error[], maxLen, const flags[]="");
+
+
+Example:
+Spoiler 
+Code:
+new ret, error[128]
+new Regex:regex_handle = regex_compile("^^STEAM_0:[01]:(\d+)$", ret, error, charsmax(error))
+
+if(regex_handle != REGEX_PATTERN_FAIL)
+{
+    // Match against strings
+}
+
+
+When matching against strings, you have to use another match function:
+Spoiler 
+Code:
+/**
+ * Matches a string against a pre-compiled regular expression pattern.
+ *
+ *
+ * @param pattern       The regular expression pattern.
+ * @param string        The string to check.
+ * @param ret           Error code, if applicable, or number of results on success.
+ *
+ * @return              -2 = Matching error (error code is stored in ret)
+ *                       0 = No match.
+ *                      >1 = Number of results.
+ *
+ * @note                You should free the returned handle (with regex_free())
+ *                      when you are done with this pattern.
+ *
+ * @note                Use the regex handle passed to this function to extract
+ *                      matches with regex_substr().
+ */
+native regex_match_c(const string[], Regex:pattern, &ret);
+
+
+Example:
+Spoiler 
+Code:
+new ret, error[128]
+new Regex:regex_handle = regex_compile("^^STEAM_0:[01]:(\d+)$", ret, error, charsmax(error))
+
+if(regex_handle != REGEX_PATTERN_FAIL)
+{
+    new players[32], pnum
+    get_players(players, pnum, "ch")
+    
+    new steamID[35], number[32]
+    
+    for(new i = 0; i < pnum; i++)
+    {
+        get_user_authid(players[i], steamID, charsmax(steamID))
+        
+        if(regex_match_c(steamID, regex_handle, ret) > 0)
+        {
+            regex_substr(regex_handle, 1, numbers, charsmax(numbers))
+            
+            // numbers = trailing numbers in SteamID of this player
+        }
+    }
+    
+    regex_free(regex_handle)
+}
+
+
+Another example for compiling:
+Spoiler 
+Code:
+#include <amxmodx>
+#include <regex>
+
+new Regex:gPatternSteamID = REGEX_PATTERN_FAIL // Default to invalid handle
+
+public plugin_init()
+{
+    new ret, error[128]
+    gPatternSteamID = regex_compile("^^STEAM_0:[01]:\d+$", ret, error, charsmax(error))
+    
+    if(gPatternSteamID == REGEX_PATTERN_FAIL)
+    {
+        log_amx("Error creating SteamID pattern (%d): %s", ret, error)
+    }
+}
+
+stock bool:IsValidSteamID(const string[])
+{
+    new ret
+    return (gPatternSteamID != REGEX_PATTERN_FAIL && regex_match_c(string, gPatternSteamID, ret) > 0)
+}
+
+RegEx Tester
+RegEx Tester is a plugin I wrote to be able to check strings against a pattern via the server console.
+
+Command:
+- regex_pattern <pattern>
+- regex_test <test data>
+
+The pattern can be in /pattern/flags format or just the pattern itself.
+
+Example:
+Code:
+] regex_pattern "^STEAM_0:[01]:\d+$"
+Pattern set to: ^STEAM_0:[01]:\d+$
+Flags set to: 
+] regex_test "STEAM_0:1:23456"
+1 matches
+1. "STEAM_0:1:23456"
+] regex_pattern "/^STEAM_0:[01]:\d+$/i"
+Pattern set to: ^STEAM_0:[01]:\d+$
+Flags set to: i
+] regex_test "steam_0:1:23456"
+1 matches
+1. "steam_0:1:23456"
+You can use this if you are unsure whether or not your pattern will work.

Scripting Cvars.txt

@@ -0,0 +1,96 @@
+Scripting Cvars (AMX Mod X)
+CVARs, or Console VARiables, are an easy and efficient way to store configurable variables on the server. Half-Life 1 supports both server-side cvars and client-side cvars. Internally, cvars are stored as both a float and a string. CVARs can be used for easy access outside the plugin. Valid example would be : Storing Weapon Knock back in a CVAR then editing it via configurable files.
+
+Contents
+1	Server-Side
+1.1	Getting Values
+1.2	Setting Value
+1.3	Flags
+2	Client Side CVARs
+2.1	Getting
+2.2	Setting
+2.3	Locking
+Server-Side
+To create a cvar, use register_cvar.
+
+register_cvar(const name[],const string[],flags = 0,Float:fvalue = 0.0);
+Note: The last parameter is for backwards compatibility only, and serves no purpose in AMXx. It is recommended you register CVARs during plugin_init, so that other plugins may alter them at plugin_cfg.
+
+Parameters:
+name[] : The name of the CVAR you want to register
+string[] : The default value of the CVAR
+flags : See Cvars (AMX Mod X).
+Getting Values
+/* Gets a cvar float. */
+Float:get_cvar_float(const cvarname[]);
+
+/* Gets a cvar integer value. */
+get_cvar_num(const cvarname[]);
+
+/* Reads a cvar value. */
+get_cvar_string(const cvarname[],output[],iLen);
+Setting Value
+/* Sets a cvar to given value. */
+set_cvar_string(const cvar[],const value[]);
+
+/* Sets a cvar to given float. */
+set_cvar_float(const cvar[],Float:value);
+
+/* Sets a cvar with integer value. */
+set_cvar_num(const cvarname[],value);
+Flags
+These flags can be used for the third parameter in the register_cvar native:
+
+#define	FCVAR_ARCHIVE		1	/* set to cause it to be saved to vars.rc */
+#define	FCVAR_USERINFO		2	/* changes the client's info string */
+#define	FCVAR_SERVER		4	/* notifies players when changed */
+#define FCVAR_EXTDLL		8	/* defined by external DLL */
+#define FCVAR_CLIENTDLL		16	/* defined by the client dll */
+#define FCVAR_PROTECTED		32	/* It's a server cvar, but we don't send the data since it's a password, etc.  Sends 1 if it's not bland/zero, 0 otherwise as value */
+#define FCVAR_SPONLY		64	/* This cvar cannot be changed by clients connected to a multiplayer server. */
+#define FCVAR_PRINTABLEONLY	128	/* This cvar's string cannot contain unprintable characters ( e.g., used for player name etc ). */
+#define FCVAR_UNLOGGED		256	/* If this is a FCVAR_SERVER, don't log changes to the log file / console if we are creating a log */
+You can alter these flags dynamically, using the cvar flag natives:
+
+/* Returns a cvar flags. */
+get_cvar_flags(const cvar[]);
+
+/* Sets a cvar flags (not allowed for amx_version,
+* fun_version and sv_cheats cvars). */
+set_cvar_flags(const cvar[],flags);
+
+/* Removes a cvar flags (not allowed for amx_version,
+* fun_version and sv_cheats cvars). */
+remove_cvar_flags(const cvar[],flags = -1);
+Client Side CVARs
+Client side cvars cannot be created in Half-Life 1. The cvar must exist in advance. Furthermore, since it must be retrieved or set over the network, knowing the value at a given point in time is impossible. You can, however, query a client for a cvar and get an asynchronous response, and use client_cmd to set a new value if necessary.
+
+Getting
+Recently, VALVE added a client CVAR checking interface, which has been added to AMX Mod X:
+
+// Dispatches a client cvar query
+//  id: Player id
+//  cvar: cvar name
+//  resultFunc: public handler function
+//  paramLen + params: optional array parameter
+// resultFunc looks like:
+//  public callbackCvarValue(id, const cvar[], const value[])
+// or if you use the optional parameter:
+//  public callbackCvarValue(id, const cvar[], const value[], const param[])
+query_client_cvar(id, const cvar[], const resultFunc[], paramlen=0, const params[] = "");
+This native may appear daunting, but it is actually quite simple; the first parameter is the player, the second the cvar, the third the function called which will contain the client CVAR, and the last two are for allowing the passage of strings.
+
+If you wish to get an array or strting back, simply put the length you want it, and fill params will a value. Then, in your return function, you will receive an array.
+
+Setting
+Setting a client side CVAR is easy; execute a new value onto the client:
+
+client_cmd(player_id,"cvar value")
+
+Locking
+Since the client can change cvar values back as soon as they're set, it might be necessary to lock them. Since alias's are executed before cvars, you can create an alias of the same name of the cvar, thus locking the cvar:
+
+//CVAR: cvar_ex.
+client_cmd(player_id,"cvar_ex 1")
+client_cmd(player_id,";alias cvar_ex")
+Now the cvar cannot be changed by the player or the server; it is locked.

The advantages cellArray.sma.txt

@@ -0,0 +1,55 @@
+
+#include <amxmodx>
+#include <amxmisc>
+#include <cellarray>
+
+#define PLUGIN	"New Plugin"
+#define AUTHOR	"Unknown"
+#define VERSION	"1.0"
+
+
+
+public plugin_init()
+{
+	register_plugin(PLUGIN, VERSION, AUTHOR)
+}
+
+public findSteamID(steamID[34],Array:steamIDs)
+{
+	new size = ArraySize(steamIDs);
+	new steamIDSearch[34];
+	
+	for(new i=0;i<size;i++)
+	{
+		ArrayGetString(steamIDs,i,steamIDSearch,33)
+		
+		if(!strcmp(steamID,steamIDSearch))
+			return true;
+	}
+	
+	return false;
+}
+
+public plugin_cfg()
+{
+	new file = fopen("list","r") 
+	
+	new steamID[34]
+	
+	new Array:steamIDs = ArrayCreate(34);
+	
+	while(fgets(file,steamID,33))
+	{
+		steamID[strlen(steamID)-2] = 0;
+		ArrayPushString(steamIDs,steamID);
+	}
+	
+	new steamIDFind[34] = "STEAM_0:1:1234567";
+	
+	for(new i=0;i<10000;i++)
+	{
+		findSteamID(steamIDFind,steamIDs);
+	}
+
+	server_cmd("quit");
+}

The advantages cellArrayResults.txt.txt

@@ -0,0 +1,36 @@
+date: Mon Mar 23 12:32:18 2009 map: de_dust2
+type |                             name |      calls | time / min / max
+-------------------------------------------------------------------
+   n |                  register_plugin |          1 | 0.000010 / 0.000010 / 0.000010
+   n |                        ArraySize |      10000 | 0.021665 / 0.000001 / 0.000070
+   n |                   ArrayGetString |     690000 | 1.522466 / 0.000001 / 0.000169
+   n |                           strcmp |     690000 | 1.526563 / 0.000001 / 0.000304
+   n |                            fopen |          1 | 0.000037 / 0.000037 / 0.000037
+   n |                      ArrayCreate |          1 | 0.000003 / 0.000003 / 0.000003
+   n |                            fgets |         70 | 0.000193 / 0.000002 / 0.000020
+   n |                           strlen |         69 | 0.000165 / 0.000002 / 0.000004
+   n |                  ArrayPushString |         69 | 0.000173 / 0.000002 / 0.000007
+   n |                       server_cmd |          1 | 0.000015 / 0.000015 / 0.000015
+   p |                       plugin_cfg |          1 | 0.023199 / 0.023199 / 0.023199
+   p |                      plugin_init |          1 | 0.000005 / 0.000005 / 0.000005
+   f |                      findSteamID |      10000 | 3.195967 / 0.000288 / 0.002059
+0 natives, 1 public callbacks, 2 function calls were not executed.
+
+date: Mon Mar 23 12:32:37 2009 map: de_dust2
+type |                             name |      calls | time / min / max
+-------------------------------------------------------------------
+   n |                  register_plugin |          1 | 0.000006 / 0.000006 / 0.000006
+   n |                        ArraySize |      10000 | 0.021601 / 0.000001 / 0.000063
+   n |                   ArrayGetString |     690000 | 1.528007 / 0.000001 / 0.000247
+   n |                           strcmp |     690000 | 1.530929 / 0.000001 / 0.001078
+   n |                            fopen |          1 | 0.000034 / 0.000034 / 0.000034
+   n |                      ArrayCreate |          1 | 0.000003 / 0.000003 / 0.000003
+   n |                            fgets |         70 | 0.000192 / 0.000002 / 0.000025
+   n |                           strlen |         69 | 0.000161 / 0.000002 / 0.000004
+   n |                  ArrayPushString |         69 | 0.000153 / 0.000001 / 0.000007
+   n |                       server_cmd |          1 | 0.000011 / 0.000011 / 0.000011
+   p |                       plugin_cfg |          1 | 0.023353 / 0.023353 / 0.023353
+   p |                      plugin_init |          1 | 0.000005 / 0.000005 / 0.000005
+   f |                      findSteamID |      10000 | 3.196872 / 0.000283 / 0.000774
+0 natives, 1 public callbacks, 2 function calls were not executed.
+

The advantages cellTrie.sma.txt

@@ -0,0 +1,45 @@
+
+#include <amxmodx>
+#include <amxmisc>
+#include <celltrie>
+
+#define PLUGIN	"New Plugin"
+#define AUTHOR	"Unknown"
+#define VERSION	"1.0"
+
+
+public plugin_init()
+{
+	register_plugin(PLUGIN, VERSION, AUTHOR)
+}
+
+public findSteamID(steamID[34],Trie:steamIDs)
+{
+	new value;
+	TrieGetCell(steamIDs,steamID,value);
+	return value;
+}
+
+public plugin_cfg()
+{
+	new file = fopen("list","r") 
+	
+	new steamID[34]
+	
+	new Trie:steamIDs = TrieCreate()
+	
+	while(fgets(file,steamID,33))
+	{
+		steamID[strlen(steamID)-2] = 0;
+		TrieSetCell(steamIDs,steamID,true);
+	}
+	
+	new steamIDFind[34] = "STEAM_0:1:1234567";
+	
+	for(new i=0;i<10000;i++)
+	{
+		findSteamID(steamIDFind,steamIDs);
+	}
+
+	server_cmd("quit");
+}

The advantages cellTrieResults.txt.txt

@@ -0,0 +1,31 @@
+sdate: Mon Mar 23 12:34:49 2009 map: de_dust2
+type |                             name |      calls | time / min / max
+-------------------------------------------------------------------
+   n |                  register_plugin |          1 | 0.000006 / 0.000006 / 0.000006
+   n |                      TrieGetCell |      10000 | 0.022582 / 0.000001 / 0.000161
+   n |                            fopen |          1 | 0.000035 / 0.000035 / 0.000035
+   n |                       TrieCreate |          1 | 0.000009 / 0.000009 / 0.000009
+   n |                            fgets |         70 | 0.000196 / 0.000002 / 0.000020
+   n |                           strlen |         69 | 0.000158 / 0.000001 / 0.000004
+   n |                      TrieSetCell |         69 | 0.000272 / 0.000002 / 0.000008
+   n |                       server_cmd |          1 | 0.000013 / 0.000013 / 0.000013
+   p |                       plugin_cfg |          1 | 0.023321 / 0.023321 / 0.023321
+   p |                      plugin_init |          1 | 0.000005 / 0.000005 / 0.000005
+   f |                      findSteamID |      10000 | 0.045496 / 0.000003 / 0.000429
+0 natives, 1 public callbacks, 2 function calls were not executed.
+
+date: Mon Mar 23 12:34:57 2009 map: de_dust2
+type |                             name |      calls | time / min / max
+-------------------------------------------------------------------
+   n |                  register_plugin |          1 | 0.000008 / 0.000008 / 0.000008
+   n |                      TrieGetCell |      10000 | 0.021956 / 0.000001 / 0.000080
+   n |                            fopen |          1 | 0.000040 / 0.000040 / 0.000040
+   n |                       TrieCreate |          1 | 0.000009 / 0.000009 / 0.000009
+   n |                            fgets |         70 | 0.000194 / 0.000002 / 0.000025
+   n |                           strlen |         69 | 0.000158 / 0.000002 / 0.000010
+   n |                      TrieSetCell |         69 | 0.000242 / 0.000002 / 0.000007
+   n |                       server_cmd |          1 | 0.000013 / 0.000013 / 0.000013
+   p |                       plugin_cfg |          1 | 0.022967 / 0.022967 / 0.022967
+   p |                      plugin_init |          1 | 0.000005 / 0.000005 / 0.000005
+   f |                      findSteamID |      10000 | 0.045080 / 0.000003 / 0.000090
+0 natives, 1 public callbacks, 2 function calls were not executed.

The advantages of a trie over an array for strings storage.txt

@@ -0,0 +1,43 @@
+Those who are unaware of what a trie is and what's its purpose, when needing a data structure to store strings, use an array. Since you can also use tries for store strings there are best cases of use for each one.
+
+
+
+What they are:
+
+An array is a group of sequential bytes in memory subdivided in groups of the same length, being each one of the subdivided a individual place to store data, that you can access by its position in the array (usually referred as index).
+
+A trie is a collection of data organized in the form of a hierarchy. The level zero is a start point. From there on, each level is a group of strings of length equal to the level number and different from each other. Each string can be associated to a value and to strings in the level below that share its characters. If one is associated to a value, it is stored in the trie.
+
+From wikipedia:
+
+
+
+In the tree above there are stored the strings:
+
+A , i , to , in , tea , ted , ten , inn
+
+(since they are those who have associated values).
+
+
+Which one should be used where you can use both:
+
+An array should be used when you know the index of the string that you want to posteriorly access or if you need to iterate over its values.
+
+A trie should be used when you want to posteriorly search for a string.
+
+To show the differences of its usage, in a case where you should use a trie, i created the following situation:
+
+I want to know if in a list of steam Ids there is a given steam Id. I have a list of 69 steam Ids and the given steam Id is not on the list.
+
+When comparing algorithms it must be tested what's referred to as "worst case". The worst case is the case on which you force the algorithm to test every possibility. That's why the steam Id is not on the list.
+
+The code and the profiling results go as attachments.
+
+A note:
+
+While the superiority of tries over arrays for this case should be obvious i think that the results for ArrayGetString are not accurate. So or:
+They are accurate and i am wrong
+I made something wrong
+There's something wrong with ArrayGetString
+There's something wrong with the profiling.
+Attached Files

Touch Stuff.txt

@@ -0,0 +1,106 @@
+1. Touch with natives
+Engine way:
+PHP Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <engine>
+
+
+public plugin_init() {
+    register_plugin("Touch Test","0.1","SAMURAI");
+    
+    // now registers a touch action to a function. 
+    register_touch("touched","toucher","hook_touch"); 
+}
+
+
+public hook_touch(touched,toucher)
+{
+    if(is_user_admin(toucher) && is_user_bot(touched))    
+    {
+        client_print(0,print_chat,"kbooom")
+    }
+    
+} 
+
+touched = Who are touched by Toucher
+toucher = Who touch
+
+If you want to filter touched / toucher
+An example :
+Only running hook_touch if a player touch something..
+PHP Code:
+register_touch("player","*","hook_touch"); 
+
+
+2. Forwards touch:
+Engine way:
+PHP Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <engine>
+
+
+public plugin_init() {
+    register_plugin("Touch test","0.1","SAMURAI");
+    
+    
+}
+
+// Called when two entities touch/collide. 
+public pfn_touch(ptr,ptd)
+{
+    new classname[32]
+    entity_get_string(ptr,EV_SZ_classname,classname,31) 
+
+    
+    if ( equal(classname, "hostage_entity") ) 
+    {
+        client_print(0,print_chat,"damn touched");
+        // and other stuff
+    }
+} 
+
+
+
+Fakemeta way:
+PHP Code:
+#include <amxmodx>
+#include <fakemeta>
+
+public plugin_init() {
+    register_plugin("Touch Test","0.1","SAMURAI");
+    
+    register_forward(FM_Touch,"hook_touch");
+}
+
+public hook_touch(ptr,ptd)
+{
+    new classname[32]
+    pev(ptr,pev_classname,classname,31)
+    
+    
+    if ( equal(classname, "hostage_entity") ) 
+    {
+        client_print(0,print_chat,"damn touched");
+        // and other stuff
+    }
+    
+} 
+
+
+3. Block touch operation:
+On Engine:
+To block touch use return PLUGIN_HANDLED;
+
+On Fakemeta:
+use return FMRES_SUPERCEDE;
+
+4. Fake Touch:
+This will simulates two entities colliding/touching.
+Engine:
+PHP Code:
+fake_touch(Touched,Toucher) 
+Fakemeta:
+PHP Code:
+dllfunc(DLLFunc_Touch, touched, toucher) 

Usage EngFunc_EntitiesInPVS.txt

@@ -0,0 +1,27 @@
+EngFunc_EntitiesInPVS (maybe the same for EngFunc_FindClientInPVS)
+It returns an entity in PVS (potential visible set) of a player.
+It never returns worldspawn.
+
+In that entity returned, you have a set of chained entities using pev_chain.
+
+Example
+Code:
+public whatisonPVS(id)
+{
+    static next, chain;
+    static class[32];
+
+    next = engfunc(EngFunc_EntitiesInPVS, id);
+    while(next)
+    {
+        pev(next, pev_classname, class, charsmax(class));
+        chain = pev(next, pev_chain);
+
+        server_print("Found entity in player (%i) PVS: ent(%i) class(%s)", id, next, class);
+        if(!chain)
+            break;
+        next = chain;
+    }
+}
+
+So this function iterates over and over every entity until pev_chain is NULL.

Using Button Constants.txt

@@ -0,0 +1,67 @@
+Usage
+
+Button constants are generally used to determine when an entity is doing a certain action, such as jumping, attacking, or moving. This is used because +/- commands cannot be hooked by the HL engine (if they are made by the HL engine).
+For example, this would work:
+Code:
+register_concmd("+explode","hook_explode")
+
+However this would not:
+Code:
+register_concmd("+attack","hook_attack")
+Why? Because the client does not literally send "+attack" over the reliable stream, since this would cause massive lag. Instead, an integer is sent, which is easier on bandwidth.
+
+
+Constants
+
+A full list of constants can be found here: http://amxmodx.org/funcwiki.php?go=m...#const_buttons
+
+
+Implementation
+
+If, for example, it is desired to check when a player is attacking, one would use the following:
+Code:
+#include <amxmodx>
+#include <engine>
+
+public plugin_init()
+{
+    register_plugin("Attack Test","1.0","Hawk552");
+}
+
+public client_PreThink(id)
+{
+    if(entity_get_int(id,EV_INT_BUTTON) & IN_ATTACK)
+    {
+        // do something
+    }
+}
+Notice how this uses the & operator, rather than the && operator. This is because a bit value is returned, and the & operator checks if a bit value is contained in another bit value.
+To set an entity's button, the same type of idea can be implemented:
+Code:
+#include <amxmodx>
+#include <engine>
+
+public plugin_init()
+{
+    register_plugin("Attack Test","1.0","Hawk552");
+}
+
+public client_PreThink(id)
+{
+    entity_set_int(id,EV_INT_button,IN_ATTACK);
+}
+This sets the client's attack flag to on every time a frame is rendered.
+To get an entity's buttons, and then ommit a certain button, one would use the following:
+Code:
+#include <amxmodx>
+#include <engine>
+
+public plugin_init()
+{
+    register_plugin("Attack Test","1.0","Hawk552");
+}
+
+public client_PreThink(id)
+{
+    entity_set_int(id,EV_INT_button,entity_get_int(id,EV_INT_button) & ~IN_ATTACK);
+}

Using Files to write datavalues(old and new file commands).txt

@@ -0,0 +1,351 @@
+This is a little tutorial about reading/writing files to store something.
+This Tutorial need basics in Amxx Scripting.
+I am not so good in explain and writing Tutorials,so the most are writing as code.
+I dont explain every Command.
+If there something wrong or better please post.
+
+Lets begin with the old file commands (easy and short).
+
+Code:
+read_file ( const file[], line, text[], len, &txtLen )
+Read a specific line with given lenght into an array.
+It returns index of next line or 0 when the end of the file is reached.
+The number of characters read is stored in txtLen.
+Code:
+write_file ( const file[], const text[], [ line ] )
+Write an array to file to the given line,if line is -1 it write at end of the file
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+#define PLUGIN "Filehandle"
+#define VERSION "1.0"
+#define AUTHOR "Administrator"
+
+new filename[256]
+
+public plugin_init() {
+    register_plugin(PLUGIN, VERSION, AUTHOR)
+    
+    /*get the config directory of amxx*/
+    get_configsdir(filename,255)
+    format(filename,255,"%s/filehandle.txt",filename)
+    register_concmd("amx_filetestwrite","filewritetest")
+    register_concmd("amx_filetestread","filereadtest")
+}
+
+public filewritetest(id){
+    new writedata[128]
+    new steamid[32],name[32],anyvalue,Float:anyfloatvalue
+    
+    /*Lets create and copy some dummy data*/
+    get_user_authid(id,steamid,31)
+    get_user_name(id,name,31)
+    anyvalue = 10
+    anyfloatvalue = 5.5
+    
+    formatex(writedata,127,"%s %s %d %f",steamid,name,anyvalue,anyfloatvalue)
+    
+    /*Now write this data to the file at last line
+    write_file ( const file[], const text[], [ line ] )
+    The line parameter defaults to -1, which appends to the end of the file. Otherwise, a specific line is overwritten.
+    If no file exist write_file create one*/
+    write_file(filename,writedata)
+}
+
+public filereadtest(id){
+    new readdata[128],steamid[32],anyvalue,Float:anyfloatvalue,txtlen
+    new parsedsteamid[32],parsedname[32],parsedanyvalue[8],parsedanyfloatvalue[8]
+    
+    /*now read the data from the file*/
+    /*It give 2 ways to read a file until end of line*/
+    
+    /*The first way*/
+    /*file_size - Returns the size of a file.
+    If flag is 0, size is returned in bytes.
+    If flag is 1, the number of lines is returned.
+    If flag is 2, 1 is returned if the file ends in a line feed.
+    If the file doesn't exist, -1 is returned. */
+    new fsize = file_size(filename,1)
+    for (new line=0;line<=fsize;line++)
+    {
+        /*read_file ( const file[], line, text[], len, &txtLen )*/
+        read_file(filename,line,readdata,127,txtlen)
+        /*We must parse the readata in somthing that we can use*/
+        parse(readdata,parsedsteamid,31,parsedname,31,parsedanyvalue,7,parsedanyfloatvalue,7)
+        
+        /*check if steamid the same as in file*/
+        get_user_authid(id,steamid,31)
+        if(equal(steamid,parsedsteamid))
+        {
+            /*steamid is same as in file,the do somthing with the rest of parsed values*/
+            anyvalue = str_to_num(parsedanyvalue)
+            anyfloatvalue = str_to_float(parsedanyfloatvalue)
+            client_print(id,print_chat,"Your saved Steamid:%s Name:%s Value:%d FloatValue:%f",parsedsteamid,parsedname,anyvalue,anyfloatvalue)
+            /*i use break to stop the loop to save more performance.On big files this is good*/
+            break
+            //...
+        }
+    }
+    
+    /*The second way/the better way*/
+    new line = 0
+    while(!read_file(filename,line++,readdata,127,txtlen))
+    {
+        parse(filename,parsedsteamid,31,parsedname,31,parsedanyvalue,7,parsedanyfloatvalue,7)
+        
+        get_user_authid(id,steamid,31)
+        if(equal(steamid,parsedsteamid))
+        {
+            anyvalue = str_to_num(parsedanyvalue)
+            anyfloatvalue = str_to_float(parsedanyfloatvalue)
+            client_print(id,print_chat,"Your saved Steamid:%s Name:%s Value:%d FloatValue:%f",parsedsteamid,parsedname,anyvalue,anyfloatvalue)
+            break
+            //...
+        }
+    }   
+}
+
+The next are the new file commands(many and very powerfull)
+
+Lets begin with basics of new file commands and write/read a string inside a file.
+This is good for textfiles where easily can read the file
+
+The new file commands dont read linespecific,they use a cursor inside the file to read the data.
+This cursor position can get with
+Code:
+ftell(file)
+And the cursor can set with
+Code:
+fseek ( file, position, start )
+"position" is an offset from start
+start can be:
+Code:
+SEEK_SET //beginning of the file
+SEEK_CUR //current cursor position
+SEEK_END //end of the file
+Code:
+rewind ( file )
+move the cursor position to begin of the file.
+
+Code:
+fopen ( filename[], mode[] )
+Open a file with given filename and mode.
+It returns a pointer to the file.
+
+Code:
+fputs ( file, const text[])
+Write a string to a text file at current filecursor position.
+"file" must be a pointer to a file from the fopen command.
+Code:
+fprintf ( file, const buffer[], ... )
+Write a formated string to a text file.Same as the format/formatex command,but for files.
+
+fputs/fprint dont add a newline at end of the string,so it must set manually.
+Code:
+fgets ( file, buffer[], maxlength )
+Read a line (including newlines) from a text file from current filecursor position until maxlenght is reached or newline/end of file is founded.
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+#define PLUGIN "Filehandle"
+#define VERSION "1.0"
+#define AUTHOR "Administrator"
+
+new filename[256]
+
+public plugin_init() {
+    register_plugin(PLUGIN, VERSION, AUTHOR)
+    
+    get_configsdir(filename,255)
+    format(filename,255,"%s/filehandle.txt",filename)
+    register_concmd("amx_filetestwrite","filewritetest")
+    register_concmd("amx_filetestread","filereadtest")
+}
+
+public filewritetest(id){
+    new writedata[128]
+    new steamid[32],name[32],anyvalue,Float:anyfloatvalue
+    
+    get_user_authid(id,steamid,31)
+    get_user_name(id,name,31)
+    anyvalue = 10
+    anyfloatvalue = 5.5
+    
+    /*fopen - Returns a file handle for advanced file functions. 
+    Mode uses the standard C library of mode types.
+    The first character can be:
+    "a" - append
+    "r" - read
+    "w" - write
+    
+    The second character can be:
+    "t" - text
+    "b" - binary
+    
+    You can also append a "+" to specify both read and write.
+    Open a file in append+read+write mode
+    On mode "a+"/"w+" it create a file if there no exist
+    Mode "w+" overwrite a file if one exist*/
+    new filepointer = fopen(filename,"a+")
+
+    /*check if file is open,on an error filepointer is 0*/
+    if(filepointer)
+    {
+        /*It give 2 ways to write a string inside a file*/
+        
+        /*First way*/
+        formatex(writedata,127,"%s %s %d %f^n",steamid,name,anyvalue,anyfloatvalue)
+        //The new file commands need to create a newline manual with "^n"
+        
+        /*write the string to the file*/
+        /*another commands are:
+        fputc - Writes a char (1 byte) to a file handle.
+        fputf - Writes a float (4 bytes, 8 on AMD64) to a file handle. 
+        fputi - Writes an integer (4 bytes) to a file handle. 
+        fputl - Writes a long (4 bytes) to a file handle. */
+        fputs(filepointer,writedata)
+        
+        /*Second way*/
+        /*fprintf - Writes a line to a file */
+        fprintf(filepointer,"%s %s %d %f^n",steamid,name,anyvalue,anyfloatvalue)
+        
+        /*close the file,this is optional,but better is it to close the file*/
+        fclose(filepointer)
+    }
+}
+
+public filereadtest(id){
+    /*open file in read-mode*/
+    new filepointer = fopen(filename,"r")
+    /*check if file is open,on an error filepointer is 0*/
+    if(filepointer)
+    {
+        new readdata[128],steamid[32],anyvalue,Float:anyfloatvalue
+        new parsedsteamid[32],parsedname[32],parsedanyvalue[8],parsedanyfloatvalue[8]
+    
+        /*Read the file until it is at end of file*/
+        /*fgets - Reads a line from a text file -- includes newline!*/
+        while(fgets(filepointer,readdata,127))
+        {   
+            parse(readdata,parsedsteamid,31,parsedname,31,parsedanyvalue,7,parsedanyfloatvalue,7)
+        
+            get_user_authid(id,steamid,31)
+            if(equal(steamid,parsedsteamid))
+            {
+                anyvalue = str_to_num(parsedanyvalue)
+                anyfloatvalue = str_to_float(parsedanyfloatvalue)
+                client_print(id,print_chat,"Your saved Steamid:%s Name:%s Value:%d FloatValue:%f",parsedsteamid,parsedname,anyvalue,anyfloatvalue)
+                break
+                //...
+            }
+        }
+        fclose(filepointer)
+    }
+}
+
+To write a file where must save many data ,the plugin growing big and are many work to write with using Parse,str_to_,...
+Here a little trick that i have learn to use strucs in Pawn.
+This is very easy to manage the filedata and adding new data,but every change need to change/convert also the file.
+
+Code:
+enum enumname{}
+enum give the variable inside the {} a number.It begin with number 0.
+With "new variablename[enumname]" it create a variable with the arraylenght of the given enum.
+Code:
+fwrite_raw ( file, const stream[], blocksize, mode )
+Write an array to the file at current cursor position."blocksize" is the size of the array or the lenght who want to write.
+Mode can be:
+Code:
+BLOCK_INT //Good to write any value/char
+BLOCK_SHORT //For writing values -32767 -> 32767 and chars
+BLOCK_CHAR //Good for writing chars/values -127 -> 127
+BLOCK_BYTE //Same as char
+Code:
+fread_raw ( file, stream[], blocksize, blocknum )
+Reads blocknum blocks from a file at current file cursor position until blocksize is reached or end of the file is found.It returns the number of succesfully readed blocks.
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+
+#define PLUGIN "Filehandle"
+#define VERSION "1.0"
+#define AUTHOR "Administrator"
+
+new filename[256]
+
+enum PLAYER_DATABASE
+{
+    STEAMID[32],
+    NAME[32],
+    ANYVALUE,
+    ANYFLOATVALUE,
+    
+    PLAYER_DATABASE_END
+}
+new player_data[33][PLAYER_DATABASE]
+
+public plugin_init() {
+    register_plugin(PLUGIN, VERSION, AUTHOR)
+    
+    get_configsdir(filename,255)
+    format(filename,255,"%s/filehandle.txt",filename)
+    register_concmd("amx_filetestwrite","filewritetest")
+    register_concmd("amx_filetestread","filereadtest")
+}
+
+public filewritetest(id){
+    /*Lets create and copy some dummy data into data*/
+    get_user_authid(id,player_data[id][STEAMID],31)
+    get_user_name(id,player_data[id][NAME],31)
+    player_data[id][ANYVALUE] = 10
+    /*theres a little problem with enum and floats:player_data[id][ANYFLOATVALUE] = 5.5 return an tag mismatch error
+    this error can be ignored but a better way is using _: in front of the float value*/
+    player_data[id][ANYFLOATVALUE] = _:5.5
+    
+    new fp=fopen(filename,"a+")
+    if(fp)
+    {
+        /*There exist 3 commands
+        fwrite - Writes an element to a file (for single chars)
+        fwrite_blocks - Writes a block of data in a file (for unknown,havent get any good results with this)
+        fwrite_raw - Writes blocks of data to a file (for strings/arrays)*/
+        fwrite_raw(fp,player_data[id][PLAYER_DATABASE:0],sizeof(player_data[]),BLOCK_INT)
+        /*Now i explain the fwrite_raw 
+        fp is the filepointer
+        player_data[id] is the data from player 
+        [PLAYER_DATABASE:0] is the begining of the data who want to write,
+        to write only Steamid it need to use player_data[id][PLAYER_DATABASE:STEAMID]
+        sizeof(player_data[]) is the lenght of data which want to write,
+        to write somthing like only steamid it need "player_data[id][PLAYER_DATABASE:STEAMID],32"
+        */
+    }
+    fclose(fp)  
+}
+
+public filereadtest(id){
+    new readdata[PLAYER_DATABASE],steamid[32]
+    new fp=fopen(filename,"r")
+    if(fp)
+    {
+        while(fread_raw(fp,readdata[PLAYER_DATABASE:0],sizeof(player_data[]),1))
+        {   
+            get_user_authid(id,steamid,31)
+            if(equal(steamid,readdata[STEAMID]))
+            {
+                player_data[id][ANYVALUE] = readdata[ANYVALUE]
+                player_data[id][ANYFLOATVALUE] = _:readdata[ANYFLOATVALUE]
+                copy(player_data[id][STEAMID],31,readdata[STEAMID])
+                copy(player_data[id][NAME],31,readdata[NAME])
+                client_print(id,print_chat,"Your saved Steamid:%s Name:%s Value:%d FloatValue:%f",readdata[STEAMID],readdata[NAME],readdata[ANYVALUE],readdata[ANYFLOATVALUE])
+                client_print(id,print_chat,"Your saved Data:%s Name:%s Value:%d FloatValue:%f",player_data[id][STEAMID],player_data[id][NAME],player_data[id][ANYVALUE],player_data[id][ANYFLOATVALUE])
+                break
+                //...
+            }
+        }
+    }
+    fclose(fp)
+}

Using Files to write datavalues, filehandle.sma.txt

@@ -0,0 +1,90 @@
+#include <amxmodx>
+#include <amxmisc>
+
+#define PLUGIN "Filehandle"
+#define VERSION "1.0"
+#define AUTHOR "Administrator"
+
+new filename[256]
+
+enum PLAYER_DATABASE
+{
+	STEAMID[32],
+	NAME[32],
+	ANYVALUE,
+	ANYFLOATVALUE,
+	//add here more values/data
+	PLAYER_DATABASE_END
+}
+
+new player_data[33][PLAYER_DATABASE]
+
+public plugin_init() {
+	register_plugin(PLUGIN, VERSION, AUTHOR)
+	
+	get_configsdir(filename,255)
+	format(filename,255,"%s/filehandle.txt",filename)
+	register_concmd("amx_filetestwrite","filewritetest")
+	register_concmd("amx_filetestread","filereadtest")
+}
+
+public filewritetest(id){
+	new founded,readdata[PLAYER_DATABASE]
+	get_user_authid(id,player_data[id][STEAMID],31)
+	get_user_name(id,player_data[id][NAME],31)
+	player_data[id][ANYVALUE] = 101
+	player_data[id][ANYFLOATVALUE] = _:9.9
+	
+	new fp=fopen(filename,"ab+")
+	if(fp)
+	{
+		while(fread_raw(fp,readdata[PLAYER_DATABASE:0],sizeof(player_data[]),BLOCK_INT))
+		{	
+			if(equal(player_data[id][STEAMID],readdata[STEAMID]))
+			{
+				fwrite_raw(fp,player_data[id][PLAYER_DATABASE:0],sizeof(player_data[]),BLOCK_INT)
+				founded = 1
+				break
+			}
+		}
+		if (!founded)
+			fwrite_raw(fp,player_data[id][PLAYER_DATABASE:0],sizeof(player_data[]),BLOCK_INT)
+	}
+	fclose(fp)	
+}
+
+public filereadtest(id){
+	new steamid[32],founded
+	new fp=fopen(filename,"rb")
+	if(fp)
+	{
+		while(fread_raw(fp,player_data[id][PLAYER_DATABASE:0],sizeof(player_data[]),1))
+		{	
+			get_user_authid(id,steamid,31)
+			if(equal(steamid,player_data[id][STEAMID]))
+			{
+				client_print(id,print_chat,"Your saved Data:%s Name:%s Value:%d FloatValue:%f",player_data[id][STEAMID],player_data[id][NAME],player_data[id][ANYVALUE],player_data[id][ANYFLOATVALUE])
+				founded = 1
+				break
+				//...
+			}
+		}
+		if(!founded)
+		{
+			//No Data founded in file
+			//Reset the Data to 0
+			for(new i=0;PLAYER_DATABASE:i<PLAYER_DATABASE_END;PLAYER_DATABASE:i++)
+			{
+				player_data[id][PLAYER_DATABASE:i] = 0
+			}
+			//client_print(id,print_chat,"Data resseted? 0=true :%f,%d,%s,%s",player_data[id][PLAYER_DATABASE:ANYFLOATVALUE],player_data[id][PLAYER_DATABASE:ANYVALUE],player_data[id][PLAYER_DATABASE:STEAMID],player_data[id][PLAYER_DATABASE:NAME])
+		}
+		else founded = 0
+	}
+	fclose(fp)
+}
+
+	
+/* AMXX-Studio Notes - DO NOT MODIFY BELOW HERE
+*{\\ rtf1\\ ansi\\ deff0{\\ fonttbl{\\ f0\\ fnil Tahoma;}}\n\\ viewkind4\\ uc1\\ pard\\ lang1031\\ f0\\ fs16 \n\\ par }
+*/

set_speak() in Fakemeta.txt

@@ -0,0 +1,175 @@
+This tutorial is for an engine-to-fakemeta conversion for the functions set_speak() and get_speak().
+
+First, we'll start off by defining the variables.
+
+Code:
+#include <amxmodx>
+#include <fakemeta>
+
+#define SPEAK_MUTED 0
+#define SPEAK_NORMAL    1
+#define SPEAK_ALL   2
+#define SPEAK_LISTENALL 4
+#define SPEAK_TEAM  8
+
+Now, "What is 'SPEAK_TEAM' ?"
+SPEAK_TEAM is a new one that I have thought up myself.
+It acts as if alltalk is on, but only for that team.
+Example:
+I'm dead, and I can still talk to my alive teammates, but not to the other team.
+
+Now, we will need to create a variable so each player can have his/her own flag.
+And, we will need to reset the player's flag to SPEAK_NORMAL when he/she enters.
+
+Code:
+new g_iSpeakFlags[33];
+
+public client_connect(id)
+{
+    g_iSpeakFlags[id] = SPEAK_NORMAL;
+}
+
+We will need some functions to get and set the player's speak mode.
+
+Code:
+#define fm_get_speak(%1) g_iSpeakFlags[%1]
+#define fm_set_speak(%1, %2) g_iSpeakFlags[%1] = %2
+fm_get_speak(index) - returns a player's speak mode
+fm_set_speak(index, iSpeakFlag) - sets a player's speak mode
+
+
+To hook when a player talks, we will need to register the forward FM_Voice_SetClientListening.
+Code:
+public plugin_init()
+{
+    register_forward(FM_Voice_SetClientListening, "fwd_FM_Voice_SetClientListening");
+}
+
+Information about the forward:
+Quote:
+FM_Voice_SetClientListening, // bool ) (iReceiver, iSender, bool:bListen)
+Now, we will create our hooked function:
+Code:
+public fwd_FM_Voice_SetClientListening(receiver, sender, bool:bListen)
+{
+    
+}
+
+This function is called even when a player isn't talking, so we must filter it out to check if the voice is valid:
+
+Code:
+public fwd_FM_Voice_SetClientListening(receiver, sender, bool:bListen)
+{
+    if(!is_user_connected(sender) || !is_user_connected(receiver))
+    {
+        return FMRES_IGNORED;
+    }
+}
+
+Also, we will need to check if the voice is a default server voice, and the two players don't have any special voice flags.
+
+Code:
+public fwd_FM_Voice_SetClientListening(receiver, sender, bool:bListen)
+{
+    if(!is_user_connected(sender) || !is_user_connected(receiver))
+    {
+        return FMRES_IGNORED;
+    }
+    
+    // the speaker has no special speech
+    // and the receiver isn't listening to everyone, so this is a default voice
+    if(g_iSpeakFlags[sender] == SPEAK_NORMAL && g_iSpeakFlags[receiver] != SPEAK_LISTENALL)
+    {
+        return FMRES_IGNORED;
+    }
+}
+
+Now it's time to set the listening.
+
+Code:
+public fwd_FM_Voice_SetClientListening(receiver, sender, bool:bListen)
+{
+    if(!is_user_connected(sender) || !is_user_connected(receiver))
+    {
+        return FMRES_IGNORED;
+    }
+    
+    // the speaker has no special speech
+    // and the receiver isn't listening to everyone, so this is a default voice
+    if(g_iSpeakFlags[sender] == SPEAK_NORMAL && g_iSpeakFlags[receiver] != SPEAK_LISTENALL)
+    {
+        return FMRES_IGNORED;
+    }
+    
+    new iSpeakValue = 0;
+    // this will be the value to determine if the voice should be sent
+    // (1 for true, 0 for false)
+    
+    // Check if the voice SHOULD be sent
+    if(g_iSpeakFlags[sender] == SPEAK_ALL
+    // speaker can talk to everyone
+    // or
+    || g_iSpeakFlags[receiver] == SPEAK_LISTENALL
+    // receiver can hear anyone
+    // or
+    || g_iSpeakFlags[sender] == SPEAK_TEAM && get_pdata_int(sender, 114) == get_pdata_int(receiver, 114))
+    // speaker can only talk to team.
+    // get_pdata_int(index, 114) is the fakemeta version of cs_get_user_team(index)
+    {
+        iSpeakValue = 1;
+    }
+    
+    // set the voice
+    engfunc(EngFunc_SetClientListening, receiver, sender, iSpeakValue);
+    return FMRES_SUPERCEDE;
+}
+
+When you are finished, this should be your full code (without comments):
+Code:
+#include <amxmodx>
+#include <fakemeta>
+
+#define SPEAK_MUTED 0
+#define SPEAK_NORMAL    1
+#define SPEAK_ALL   2
+#define SPEAK_LISTENALL 4
+#define SPEAK_TEAM  8
+
+new g_iSpeakFlags[33];
+
+#define fm_get_speak(%1) g_iSpeakFlags[%1]
+#define fm_set_speak(%1, %2) g_iSpeakFlags[%1] = %2
+
+public plugin_init()
+{
+    register_forward(FM_Voice_SetClientListening, "fwd_FM_Voice_SetClientListening");
+}
+
+public client_connect(id)
+{
+    g_iSpeakFlags[id] = SPEAK_NORMAL;
+}
+
+public fwd_FM_Voice_SetClientListening(receiver, sender, bool:bListen)
+{
+    if(!is_user_connected(receiver) || !is_user_connected(sender))
+    {
+        return FMRES_IGNORED;
+    }
+    
+    if(g_iSpeakFlags[sender] == SPEAK_NORMAL && g_iSpeakFlags[receiver] != SPEAK_LISTENALL)
+    {
+        return FMRES_IGNORED;
+    }
+    
+    new iSpeakValue = 0;
+    if(g_iSpeakFlags[sender] == SPEAK_ALL
+    || g_iSpeakFlags[receiver] == SPEAK_LISTENALL
+    || g_iSpeakFlags[sender] == SPEAK_TEAM && get_pdata_int(sender, 114) == get_pdata_int(receiver, 114))
+    {
+        iSpeakValue = 1;
+    }
+    
+    engfunc(EngFunc_SetClientListening, receiver, sender, iSpeakValue);
+    return FMRES_SUPERCEDE;
+}

set_tasks when they are and when they aren't necessary.txt

@@ -0,0 +1,153 @@
+set_task can sometimes be an extremely useful function, but other times it is really overkill. What few people know is that it is a very expensive operation, the CPU has to literally check every cycle if it is time for the set_task to be executed. Usually, there are ways around a set_task.
+
+set_task also has the restriction of being unable to be called more than every 0.1 seconds. This means that if you pass 0.01 in parameter 1, it will be clamped at 0.1.
+
+But what can we do to avoid it? Sometimes you really have to use a set_task, such as here:
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <engine>
+
+public plugin_init()
+{
+    register_plugin("ROFL","1.0","Hawk552")
+    
+    register_event("ResetHUD","EventResetHUD","be")
+}
+
+public EventResetHUD(id)
+    set_task(1.0,"DelayedResetHUD",id)
+    
+public DelayedResetHUD(id)
+    DispatchSpawn(id)
+
+But why? There is no real way to escape delaying the function once without doing something more CPU intensive or unreliable. We could create an ent and make it think in 1 second (which will be covered later), but that not only adds an unnecissary spawn for such a small thing, it also is more unreliable (i.e. the server could crash due to too many ents, or it could be failed to be spawned and the function simply has to end there).
+
+But there are other times where escaping a set_task is not only easier, but less resource consuming.
+
+One of the commonly known ways of doing this is the forward client_PreThink / FM_PlayerPreThink. This forward is called every frame on a client before rendering physics. In this forward, you would do things that generally must be constantly updated, like velocity or changing rendering.
+
+Here is an example:
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <engine>
+
+public plugin_init()
+    register_plugin("ROFL","1.0","Hawk552")
+
+public client_PreThink(id)
+{
+    static Float:Velocity[3]
+    entity_get_vector(id,EV_VEC_velocity,Velocity)
+    
+    Velocity[2] = -floatabs(Velocity[2])
+    
+    entity_set_vector(id,EV_VEC_velocity,Velocity)
+}
+
+Why is a set_task unsuitable here? For two reasons: 1) the half-life engine will allow you to have timers anyway (to a varying degree), and 2) it will look very glitchy since if the client has 60 FPS, the server is only checking every 10 frames if their velocity is what it should be.
+
+One of the less practiced ways of avoiding set_tasks is to spawn an entity, set its nextthink to whatever you want, and register_think/FM_Think it. But when is this necessary? Pretty much whenever you use the "b" flag in set_task, it's better to use this method. It's also preferred when you have already spawned an entity (such as an NPC) and want to make it say, disappear, in x seconds.
+
+Here is an example:
+
+Engine:
+Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <engine>
+
+new g_Classname[] = "roflmao"
+
+public plugin_init()
+{
+    register_plugin("ROFL","1.0","Hawk552")
+    
+    new Ent = create_entity("info_target")
+    entity_set_string(Ent,EV_SZ_classname,g_Classname)
+    entity_set_float(Ent,EV_FL_nextthink,20.0)
+    
+    register_think(g_Classname,"RoflmaoThink")
+}
+
+public RoflmaoThink(Ent)
+{
+    log_amx("ROFLMAO thinks.")
+    
+    entity_set_float(Ent,EV_FL_nextthink,20.0)
+}
+
+Fakemeta:
+Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <fakemeta>
+
+new g_Classname[] = "roflmao"
+
+public plugin_init()
+{
+    register_plugin("ROFL","1.0","Hawk552")
+    
+    new Ent = engfunc(EngFunc_CreateNamedEntity,engfunc(EngFunc_AllocString,"info_target"))
+    set_pev(Ent,pev_classname,g_Classname)
+    set_pev(Ent,pev_nextthink,20.0)
+    
+    register_forward(FM_Think,"ForwardThink")
+}
+
+public ForwardThink(Ent)
+{
+    static Classname[33]
+    pev(Ent,pev_classname,Classname,32)
+    
+    if(!equal(Classname,g_Classname))
+        return FMRES_IGNORED
+    
+    log_amx("ROFLMAO thinks.")
+    
+    set_pev(Ent,pev_nextthink,20.0)
+    
+    return FMRES_IGNORED
+}
+
+This is useful, as said, for escaping the usage of flag "b" on set_task, or executing set_task at the end of the function called.
+
+The final way to escape a set_task is when using cooldowns. For example, you want a player to be able to use a special attack every 30 seconds.
+
+Code:
+#include <amxmodx>
+#include <amxmisc>
+#include <fakemeta>
+
+// this is how often you want your players to be able to use your attack
+#define ATTACK_COOLDOWN 20.0
+
+new Float:g_LastAttack[33]
+// optimization
+new Float:g_Cooldown = ATTACK_COOLDOWN
+
+public plugin_init()
+{
+    register_plugin("ROFL","1.0","Hawk552")
+    
+    register_clcmd("myattack","CmdMyAttack")
+}
+
+public CmdMyAttack(id)
+{
+    // to use engine instead, use this:
+    /* new Float:Time = halflife_time() */
+    new Float:Time
+    global_get(glb_time,Time)    
+    
+    if(!is_user_alive(id) || Time - g_Cooldown < g_LastAttack[id])
+        return
+    
+    g_LastAttack[id] = Time
+    
+    // your code here
+}