Button constants (AMX Mod X) - Revision history

Kristi: /* Constants */

2017-08-30T20:56:45Z

‎Constants

VEN: +1 new line

2006-12-08T19:35:22Z

+1 new line

VEN: changed pre tag to pawn

2006-12-08T19:34:13Z

changed pre tag to pawn

AlMod: /* Usage */

2006-12-08T17:58:38Z

‎Usage

BAILOPAN: Button constants moved to Button constants (AMX Mod X)

2006-01-20T03:51:06Z

Button constants moved to Button constants (AMX Mod X)

BAILOPAN: added category

2006-01-20T03:50:34Z

added category

Hawk552 at 01:59, 20 January 2006

2006-01-20T01:59:52Z

New page

==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:
<pre>
register_concmd("+explode","explode");
</pre>

However this would not:
<pre>
register_concmd("+attack","hook_attack");
</pre>

==Constants==

A full list of constants can be found here:
http://amxmodx.org/funcwiki.php?go=module&id=3#const_buttons

==Implementation==
If, for example, it is desired to check when a player is attacking, one would use the following:
<pre>
#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
}
}
</pre>

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:
<pre>
#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);
}
</pre>

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:
<pre>
#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);
}
</pre>

Say, for example, during a certain time, the client is jumping and attacking at the same time. In this case, the entity_get_int(id,EV_INT_button) function would return IN_ATTACK and IN_JUMP. Using the ~ operator removes the certain bit value, making it into merely IN_JUMP.

There are many more ways to use button constants, and not all must be used on players. They are simply more commonly implemented when dealing with players.

← Older revision		Revision as of 19:35, 8 December 2006
Line 1:		Line 1:
	{{LanguageSwitch}}		{{LanguageSwitch}}
		+

	==Usage==		==Usage==

← Older revision		Revision as of 17:58, 8 December 2006
Line 1:		Line 1:
		+	{{LanguageSwitch}}
	==Usage==		==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).		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).

← Older revision		Revision as of 03:50, 20 January 2006
Line 76:		Line 76:

	There are many more ways to use button constants, and not all must be used on players. They are simply more commonly implemented when dealing with players.		There are many more ways to use button constants, and not all must be used on players. They are simply more commonly implemented when dealing with players.
		+
		+	[[Category:Scripting (AMX Mod X)]]

@@ Line 13: / Line 13: @@
 ==Constants==
-A full list of constants can be found here:
+A full list of constants can be found [http://amxmodx.org/api/hlsdk_const#pev-entity-pev-button-or-pev-entity-pev-oldbuttons-values/ here].
 ==Implementation==

@@ Line 1: / Line 1: @@
 {{LanguageSwitch}}
 ==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:
-<pre>
+<pawn>register_concmd("+explode","explode");</pawn>
 However this would not:
-<pre>
+<pawn>register_concmd("+attack","hook_attack");</pawn>
 ==Constants==
@@ Line 20: / Line 17: @@
 ==Implementation==
 If, for example, it is desired to check when a player is attacking, one would use the following:
-<pre>
+<pawn>#include <amxmodx>
 #include <engine>
@@ Line 35: / Line 31: @@
 		// do something
+	}
+}</pawn>
 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:
-<pre>
+<pawn>#include <amxmodx>
 #include <engine>
@@ Line 53: / Line 47: @@
+{
 	entity_set_int(id,EV_INT_button,IN_ATTACK);
+}</pawn>
 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:
-<pre>
+<pawn>#include <amxmodx>
 #include <engine>
@@ Line 71: / Line 63: @@
+{
 	entity_set_int(id,EV_INT_button,entity_get_int(id,EV_INT_button) & ~IN_ATTACK);
+}</pawn>
 Say, for example, during a certain time, the client is jumping and attacking at the same time. In this case, the entity_get_int(id,EV_INT_button) function would return IN_ATTACK and IN_JUMP. Using the ~ operator removes the certain bit value, making it into merely IN_JUMP.

← Older revision	Revision as of 03:51, 20 January 2006
(No difference)