Module Writing (AMX Mod X) - Revision history

ConnorMcLeod: /* Amxmodx SDK */

2012-02-12T16:16:13Z

‎Amxmodx SDK

DS: Replaced include path setup with envirornment var information

2008-08-17T00:46:39Z

Replaced include path setup with envirornment var information

Zor: /* Developing Module */

2007-12-26T20:22:41Z

‎Developing Module

Zor: /* HL API */

2007-12-26T20:21:27Z

‎HL API

Zor: /* HL API */

2007-12-26T20:18:32Z

‎HL API

Zor: /* Developing Module */

2007-12-26T20:17:47Z

‎Developing Module

Zor at 20:11, 26 December 2007

2007-12-26T20:11:32Z

Zor at 20:08, 26 December 2007

2007-12-26T20:08:00Z

Show changes

DS: Reverted edits by Hs0Uuc (Talk); changed back to last version by Damaged Soul

2007-07-09T02:42:53Z

Reverted edits by Hs0Uuc (Talk); changed back to last version by Damaged Soul

Hs0Uuc at 19:47, 8 July 2007

2007-07-08T19:47:36Z

@@ Line 24: / Line 24: @@
 ==== Amxmodx SDK ====
-Now we need to grab the last of the SDK's so we can go carry on.  First we need to goto the Amxmodx Website so that we can get to the SDK via the Downloads area and SVN!  [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx.tar.gz?root=amxmodx&view=tar Amxmodx SDK].
+Now we need to grab the last of the SDK's so we can go carry on.  First we need to goto the Amxmodx Website so that we can get to the SDK via the Downloads area and SVN!  [http://hg.alliedmods.net/amxmodx-central/ Amxmodx SDK].
 ==== Unix2Dos the Files ====

@@ Line 28: / Line 28: @@
 ==== Unix2Dos the Files ====
 So, once you have all the files we need to fix them up a bit.  One of the things that will become bothersome later is the Unix File Format that HLSDK / Metamod has, its suppose to be Windows, but its not, so we need to convert the files, soooo...we will use the following tutorial to fix this [[GnuWin32]] Once you have that setup you can use the following to repair all files easily [http://wiki.dodplugins.net/images/6/61/Repair.rar Repair.bat].
 == Compiler GUI ==
@@ Line 44: / Line 55: @@
 === .NET SDK ===
 Next we need to grab the Dot Net install and the Dot Net SDK.  You can grab the [http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=262d25e3-f589-4842-8157-034d1e7cf3a3&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2fa%2fa%2fc%2faac39226-8825-44ce-90e3-bf8203e74006%2fdotnetfx.exe dotnet.1.1.exe] and install it.  Next you will need the .NET SDK, you can grapple [http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=9B3A2CA6-3647-4070-9F41-A333C6B9181D&u=http%3a%2f%2fdownload.microsoft.com%2fdownload%2f5%2f2%2f0%2f5202f918-306e-426d-9637-d7ee26fbe507%2fsetup.exe dotnet.1.1.sdk.exe]  Once these are installed your good to start up the GUI.
 == Message Module ( Demo ) ==

@@ Line 157: / Line 157: @@
   #endif
-So this will ensure that all the code we put between those two comments are only loaded once into the compilation process.  Now that we have this part complete we will start coding.  As we are making a module to catch all the Messages that occur on a HL DoD Server the first thing we need to do is create a structure to keep all the data that we will use.  This structure will be called StructUserMsg and will contain two members the id of the message which can be anything from 0 - 256 messages and the name of the message.  We can get these names from [http://wiki.dodplugins.net/index.php/Meta_Game].  These will be the messages that will pop up.  Now that we have this done the file should look like so:
+So this will ensure that all the code we put between those two comments are only loaded once into the compilation process.  Now that we have this part complete we will start coding.  As we are making a module to catch all the Messages that occur on a HL DoD Server the first thing we need to do is create a structure to keep all the data that we will use.  This structure will be called StructUserMsg and will contain two members the id of the message which can be anything from 0 - 256 messages and the name of the message.  We can get these names from [http://wiki.dodplugins.net/index.php/Meta_Game Meta Game].  These will be the messages that will pop up.  Now that we have this done the file should look like so:
   #ifndef DOD_MM_H

@@ Line 133: / Line 133: @@
   #define FN_WriteEntity_Post					WriteEntity_Post
-These are the actual messages that will be caught.  Finally we need to catch the registering of those messages we can see in [http://wiki.dodplugins.net/index.php/Meta_Game].  This is the function we are going to expose next:
+These are the actual messages that will be caught.  Finally we need to catch the registering of those messages we can see in [http://wiki.dodplugins.net/index.php/Meta_Game Meta Game].  This is the function we are going to expose next:
   #define FN_RegUserMsg_Post					RegUserMsg_Post

@@ Line 133: / Line 133: @@
   #define FN_WriteEntity_Post					WriteEntity_Post
-These are the actual messages that will be caught.  Finally we need to catch the registering of those messages we can see in [[Meta_Game]].  This is the function we are going to expose next:
+These are the actual messages that will be caught.  Finally we need to catch the registering of those messages we can see in [http://wiki.dodplugins.net/index.php/Meta_Game].  This is the function we are going to expose next:
   #define FN_RegUserMsg_Post					RegUserMsg_Post

@@ Line 157: / Line 157: @@
   #endif
-So this will ensure that all the code we put between those two comments are only loaded once into the compilation process.  Now that we have this part complete we will start coding.  As we are making a module to catch all the Messages that occur on a HL DoD Server the first thing we need to do is create a structure to keep all the data that we will use.  This structure will be called StructUserMsg and will contain two members the id of the message which can be anything from 0 - 256 messages and the name of the message.  We can get these names from [[Meta_Game]].  These will be the messages that will pop up.  Now that we have this done the file should look like so:
+So this will ensure that all the code we put between those two comments are only loaded once into the compilation process.  Now that we have this part complete we will start coding.  As we are making a module to catch all the Messages that occur on a HL DoD Server the first thing we need to do is create a structure to keep all the data that we will use.  This structure will be called StructUserMsg and will contain two members the id of the message which can be anything from 0 - 256 messages and the name of the message.  We can get these names from [http://wiki.dodplugins.net/index.php/Meta_Game].  These will be the messages that will pop up.  Now that we have this done the file should look like so:
   #ifndef DOD_MM_H
@@ Line 474: / Line 474: @@
 The only thing weird about this one is the flush...this just ensures the data we just collected gets sent to the file.  Well thats it...we're done...all thats left is the compile and moving the module to the addons/amxmodx/modules/ directory then adding it to the addons/amxmodx/configs/modules.ini file at the bottom.  Remember to name it dod_mm not dod_mm_amxx.dll just the first part.
-−
 == In Conclusion ==

← Older revision		Revision as of 02:42, 9 July 2007
Line 1:		Line 1:
−	AMX Mod X Modules are written in C or C (the API is C compatible).	+	AMX Mod X Modules are written in C or C++ (the API is C compatible).

−	For more information, look in: [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx /svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx] or [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk.tar.gz?root=amxmodx	+	For more information, look in: [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx /svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx] or [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk.tar.gz?root=amxmodx&view=tar click here] to download a tarball of that directory.
		+
		+	Copy these files into a new folder. The amxxmodule.h/cpp files are the Module SDK backend. You only need to edit the moduleconfig.h file to customize your module.
		+
		+	You can read howto.txt for some brief information.
		+
		+	{{Template:Stub}}
		+
		+	[[Category:AMX_Mod_X]]

← Older revision		Revision as of 19:47, 8 July 2007
Line 1:		Line 1:
−	AMX Mod X Modules are written in C or C++ (the API is C compatible).	+	AMX Mod X Modules are written in C or C (the API is C compatible).

−	For more information, look in: [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx /svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx] or [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk.tar.gz?root=amxmodx~~&view=tar click here] to download a tarball of that directory.~~	+	For more information, look in: [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx /svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk/?root=amxmodx] or [http://svn.tcwonline.org/viewvc.cgi/trunk/amxmodx/sdk.tar.gz?root=amxmodx
−
−	~~Copy these files into a new folder. The amxxmodule.h/cpp files are the Module SDK backend. You only need to edit the moduleconfig.h file to customize your module.~~
−
−	~~You can read howto.txt for some brief information.~~
−
−	~~{{Template:Stub}}~~
−
−	~~[[Category:AMX_Mod_X]]~~