FakeMeta General Usage (AMX Mod X) - Revision history

UserError: /* Return Values */

2006-09-05T10:02:41Z

‎Return Values

UserError: /* Engine vs. FakeMeta */

2006-09-05T09:58:19Z

‎Engine vs. FakeMeta

UserError: /* Engine vs. FakeMeta */

2006-09-05T09:57:28Z

‎Engine vs. FakeMeta

Brad: /* DLL / Engine Function Usage */

2006-02-21T01:14:24Z

‎DLL / Engine Function Usage

Brad: /* Entvars */

2006-02-21T01:14:10Z

‎Entvars

Brad: /* Engine vs. FakeMeta */

2006-02-21T01:13:35Z

‎Engine vs. FakeMeta

Hawk552: /* Return Values */ -- fixed paragraphs

2006-01-21T12:50:33Z

‎Return Values: -- fixed paragraphs

Hawk552: /* About */ -- fixed [PAWN] to actually link

2006-01-21T01:14:25Z

‎About: -- fixed [PAWN] to actually link

Hawk552 at 00:25, 21 January 2006

2006-01-21T00:25:34Z

BAILOPAN: pdata -> entvars, pdata is something different :)

2006-01-21T00:21:50Z

pdata -> entvars, pdata is something different :)

@@ Line 98: / Line 98: @@
 ==Return Values==
 There are 4 return values in FakeMeta:
 *FMRES_HANDLED --> Something was done in this function, but call the one in the DLL / Engine anyways.

@@ Line 17: / Line 17: @@
 public plugin_init()
+{
-	register_plugin("FakeMeta Test","1.0","Author");
+	register_plugin("FakeMeta Test","1.0","Hawk552");
 	register_forward(FM_PlayerPreThink,"PreThink");
@@ Line 35: / Line 35: @@
 public plugin_init()
+{
-	register_plugin("Engine Test","1.0","Author");
+	register_plugin("Engine Test","1.0","Hawk552");
+}

@@ Line 17: / Line 17: @@
 public plugin_init()
+{
-	register_plugin("FakeMeta Test","1.0","Hawk552");
+	register_plugin("FakeMeta Test","1.0","Author");
 	register_forward(FM_PlayerPreThink,"PreThink");
@@ Line 35: / Line 35: @@
 public plugin_init()
+{
-	register_plugin("FakeMeta Test","1.0","Hawk552");
+	register_plugin("Engine Test","1.0","Author");
+}

@@ Line 77: / Line 77: @@
 In DLLs and the Engine, there are functions that are called when certain events happen. These can be forced to be called through FakeMeta. Here is a general example:
-<pawn>
+<pawn>#include <amxmodx>
 #include <fakemeta>
@@ Line 93: / Line 92: @@
 	return FMRES_IGNORED;
 }</pawn>
 Refer to the end of the line while viewing the DLLFunc and EngFunc sections, as there is usually some description of paramaters, such as ''edict_t *p_Entity'' or ''void''. ''void'' generally refers to no parameters, while ''edict_t *p_Entity'' means the entity id, so the first parameter in the function would be the entity to call the function onto.

@@ Line 55: / Line 55: @@
 Here is an example of how to retrieve the armor entvar from an entity in FakeMeta:
-<pawn>
+<pawn>#include <amxmodx>
 #include <fakemeta>
@@ Line 73: / Line 72: @@
 	return FMRES_IGNORED;
 }</pawn>
 ==DLL / Engine Function Usage==

@@ Line 106: / Line 106: @@
 ==Return Values==
 There are 4 return values in FakeMeta:
-#define FMRES_HANDLED	2
+# FMRES_HANDLED
-#define FMRES_SUPERCEDE	4
+# FMRES_SUPERCEDE
-#define FMRES_IGNORED	1
+# FMRES_IGNORED
-#define FMRES_OVERRIDE	3
+# FMRES_OVERRIDE
-FMRES_HANDLED --> Something was done in this function, but call the one in the DLL / Engine anyways.
+*FMRES_HANDLED --> Something was done in this function, but call the one in the DLL / Engine anyways.
-FMRES_SUPERCEDE --> Prevent function in DLL / Engine from being called.
+*FMRES_SUPERCEDE --> Prevent function in DLL / Engine from being called.
-FMRES_IGNORED --> Call original function.
+*FMRES_IGNORED --> Call original function.
-FMRES_OVERRIDE --> Call original function, but change return value.
+*FMRES_OVERRIDE --> Call original function, but change return value.
 ==Constants / General==

@@ Line 3: / Line 3: @@
 ==About==
-FakeMeta is an extremely powerful module for AMX Mod X that effectively allows you to write Metamod plugins in [PAWN].
+FakeMeta is an extremely powerful module for AMX Mod X that effectively allows you to write Metamod plugins in [[Pawn]].
 Unlike Engine, FakeMeta uses no CPU if it is not told to do anything (other than to exist). For this reason, it is recommended to use FakeMeta over Engine. There is nothing in Engine that is not in FakeMeta -- while some functionality might be less [[Abstraction|abstracted]], it is still achievable, and usually with more flexibility.

← Older revision		Revision as of 00:25, 21 January 2006
Line 103:		Line 103:

	Refer to the end of the line while viewing the DLLFunc and EngFunc sections, as there is usually some description of paramaters, such as ''edict_t p_Entity'' or ''void''. ''void'' generally refers to no parameters, while ''edict_t p_Entity'' means the entity id, so the first parameter in the function would be the entity to call the function onto.		Refer to the end of the line while viewing the DLLFunc and EngFunc sections, as there is usually some description of paramaters, such as ''edict_t p_Entity'' or ''void''. ''void'' generally refers to no parameters, while ''edict_t p_Entity'' means the entity id, so the first parameter in the function would be the entity to call the function onto.
		+
		+	==Return Values==
		+	There are 4 return values in FakeMeta:
		+	#define FMRES_HANDLED 2
		+	#define FMRES_SUPERCEDE 4
		+	#define FMRES_IGNORED 1
		+	#define FMRES_OVERRIDE 3
		+
		+	FMRES_HANDLED --> Something was done in this function, but call the one in the DLL / Engine anyways.
		+	FMRES_SUPERCEDE --> Prevent function in DLL / Engine from being called.
		+	FMRES_IGNORED --> Call original function.
		+	FMRES_OVERRIDE --> Call original function, but change return value.

	==Constants / General==		==Constants / General==

@@ Line 1: / Line 1: @@
 ==Current FakeMeta and Old==
-This FakeMeta article is not to be confused with the old FakeMeta included directly in AMX Mod X, which allowed a fix for a problem that arose due to a Steam update. For this context, see [[FakeMeta_(Old) | FakeMeta (Old)]].
+FakeMeta used to be an internal mini-metamod inside [[AMX Mod X]].  This was removed in 1.50, and now only the module remains.  The module is an entirely different concept, which extends [[Metamod]] HL1 programming powers to scripts.
 ==About==
 FakeMeta is an extremely powerful module for AMX Mod X that effectively allows you to write Metamod plugins in [PAWN].
-Unlike Engine, FakeMeta uses no CPU if it is not told to do anything (other than to exist). For this reason, it is recommended to use FakeMeta over Engine. There is nothing in Engine that is not in FakeMeta, some way or another.
+Unlike Engine, FakeMeta uses no CPU if it is not told to do anything (other than to exist). For this reason, it is recommended to use FakeMeta over Engine. There is nothing in Engine that is not in FakeMeta -- while some functionality might be less [[Abstraction|abstracted]], it is still achievable, and usually with more flexibility.
 ==Engine vs. FakeMeta==
@@ Line 12: / Line 12: @@
 FakeMeta:
-<pre>
+<pawn>
 #include <amxmodx>
 #include <fakemeta>
@@ Line 29: / Line 29: @@
 	return FMRES_IGNORED;
+}
-</pre>
+</pawn>
 Engine:
-<pre>
+<pawn>
 #include <amxmodx>
 #include <engine>
@@ Line 47: / Line 47: @@
 	return;
+}
-</pre>
+</pawn>
 The "return FMRES_IGNORED" section will be covered later on this page.
@@ Line 55: / Line 55: @@
 FakeMeta also allows you to do other things, such as retrieve private data (using pev, set_pev / get_pdata_int, get_pdata_float, get_pdata_string, set_pdata_int, set_pdata_float, set_pdata_string), forcing DLL functions to be executed, as well as call Engine (not the module) functions.
-==Private Data Collecting==
+==Entvars==
-It is easy to read private data in FakeMeta, however it can sometimes cause problems if not done correctly (which is why Engine is more commonly used).
+It is easy to read [[Entvars (Half-Life 1)|entvars]] in FakeMeta, however it can sometimes cause problems if not done correctly (which is why Engine is more commonly used).  Entvars are variables in a player's [[Edicts (Half-Life 1)|edict]] structure (an edict is the basis for an entity).
-Here is an example of how to retrieve private data from an entity in FakeMeta:
+Here is an example of how to retrieve the armor entvar from an entity in FakeMeta:
-<pre>
+<pawn>
 #include <amxmodx>
 #include <fakemeta>
@@ Line 67: / Line 67: @@
 	register_plugin("FakeMeta Test","1.0","Hawk552");
-	register_forward(FM_PlayerPreThink,"PreThink");
+	register_forward(FM_PlayerPreThink, "PreThink");
+}
@@ Line 78: / Line 78: @@
 	return FMRES_IGNORED;
+}
-</pre>
+</pawn>
 ==DLL / Engine Function Usage==
 In DLLs and the Engine, there are functions that are called when certain events happen. These can be forced to be called through FakeMeta. Here is a general example:
-<pre>
+<pawn>
 #include <amxmodx>
 #include <fakemeta>
@@ Line 100: / Line 100: @@
 	return FMRES_IGNORED;
+}
-</pre>
+</pawn>
 Refer to the end of the line while viewing the DLLFunc and EngFunc sections, as there is usually some description of paramaters, such as ''edict_t *p_Entity'' or ''void''. ''void'' generally refers to no parameters, while ''edict_t *p_Entity'' means the entity id, so the first parameter in the function would be the entity to call the function onto.