Metamod:source Development - Revision history

SaberUK: Half-Life 2: Deathmatch now uses the Orange Box engine.

2010-12-15T16:00:40Z

Half-Life 2: Deathmatch now uses the Orange Box engine.

Asherkin: Removed RTTI warnings, this does not create a libstdc++ dependency.

2010-11-11T16:27:50Z

Removed RTTI warnings, this does not create a libstdc++ dependency.

Asherkin: /* Plugin API */

2010-08-30T17:54:31Z

‎Plugin API

Asherkin: /* Plugin API */

2010-08-30T17:48:42Z

‎Plugin API

Asherkin at 17:47, 30 August 2010

2010-08-30T17:47:55Z

BAILOPAN at 07:29, 26 November 2008

2008-11-26T07:29:41Z

BAILOPAN at 07:29, 26 November 2008

2008-11-26T07:29:31Z

BAILOPAN at 07:12, 26 November 2008

2008-11-26T07:12:14Z

BAILOPAN at 07:11, 26 November 2008

2008-11-26T07:11:45Z

BAILOPAN at 07:10, 26 November 2008

2008-11-26T07:10:59Z

@@ Line 21: / Line 21: @@
 *[http://www.metamodsource.net/dox-1.4.3/ 1.4 API], contained in <tt>core-legacy</tt>.  This is the API you should use if you're building a plugin to run on the following Source engines:
 **Original (The Ship)
-**Episode 1 (HL2:DM, Older third party mods).
+**Episode 1 (Older third party mods).
 *[http://www.metamodsource.net/dox/ 1.6 API], contained in <tt>core</tt>.  This is the API you should use if you're building against the following Source engines:
 **Orange Box (Garry's Mod, Newer third party mods)
-**Orange Box Valve (Team Fortress, Day of Defeat, CS:S)
+**Orange Box Valve (Team Fortress, Day of Defeat, CS:S, HL2:DM)
 **Left 4 Dead
 **Left 4 Dead 2

@@ Line 153: / Line 153: @@
 *<tt>-Wno-non-virtual-dtor</tt> - This is kind of a useless warning from GCC (not all classes need destructors).
 *<tt>-fno-exceptions</tt> - You should not use exceptions because this creates a <tt>libstdc++</tt> dependency.
 *<tt>-fno-strict-aliasing</tt> - By default, GCC does not allow certain type casts which were perfectly legal in previous versions, and are perfectly legal in almost every other C/C++ compiler.  These type casts are prevalent and without this option, GCC '''will''' generate incorrect code.
 There are a few flags you should generally not add, ever:
-*<tt>-lstdc++</tt> (same as using <tt>g++</tt>) - Even if you use the exact same compiler build as Valve, linking against the <tt>libstdc++</tt> will be painful.  Not all Linux distributions use the same version, and in general ABI compatibility on this library is frequently broken.  You will find that users report load failures or even crashes, and the problem may be very difficult to trace.  As such, you should avoid using RTTI, exceptions, and any part of the Standard Template Library (STL).  Valve provides many abstractions that should suffice, and SourceHook provides some as well.
+*<tt>-lstdc++</tt> (same as using <tt>g++</tt>) - Even if you use the exact same compiler build as Valve, linking against the <tt>libstdc++</tt> will be painful.  Not all Linux distributions use the same version, and in general ABI compatibility on this library is frequently broken.  You will find that users report load failures or even crashes, and the problem may be very difficult to trace.  As such, you should avoid using exceptions or any part of the Standard Template Library (STL).  Valve provides many abstractions that should suffice, and SourceHook provides some as well.
 **''Note:'' Statically linking to <tt>libstdc++</tt> is not an option.  It will cause many problems.
 *<tt>-m64</tt> - Don't try to build 64-bit software off the SDK.  Valve doesn't even have a 64-bit port of the server yet.

@@ Line 21: / Line 21: @@
 *[http://www.metamodsource.net/dox-1.4.3/ 1.4 API], contained in <tt>core-legacy</tt>.  This is the API you should use if you're building a plugin to run on the following Source engines:
 **Original (The Ship)
-**Episode 1 (HL2:DM, and third party mods).
+**Episode 1 (HL2:DM, Older third party mods).
 *[http://www.metamodsource.net/dox/ 1.6 API], contained in <tt>core</tt>.  This is the API you should use if you're building against the following Source engines:
-**Orange Box (Team Fortress, Day of Defeat, Garry's Mod, CS:S)
+**Orange Box (Garry's Mod, Newer third party mods)
-**Left 4 Dead
+**Orange Box Valve (Team Fortress, Day of Defeat, CS:S)
 **Left 4 Dead 2
 **Alien Swarm

@@ Line 20: / Line 20: @@
 Metamod:Source has two separate APIs:
 *[http://www.metamodsource.net/dox-1.4.3/ 1.4 API], contained in <tt>core-legacy</tt>.  This is the API you should use if you're building a plugin to run on the following Source engines:
 **Episode 1 (HL2:DM, and third party mods).
 *[http://www.metamodsource.net/dox/ 1.6 API], contained in <tt>core</tt>.  This is the API you should use if you're building against the following Source engines:
 **Orange Box (Team Fortress, Day of Defeat, Garry's Mod, CS:S)
@@ Line 31: / Line 31: @@
 More information is available in the article [[MM:S API Differences]].
 =Starting a plugin=

@@ Line 20: / Line 20: @@
 Metamod:Source has two separate APIs:
 *[http://www.metamodsource.net/dox-1.4.3/ 1.4 API], contained in <tt>core-legacy</tt>.  This is the API you should use if you're building a plugin to run on the following Source engines:
-**Episode 1 (CS:S, and third party mods).
+**Episode 1 (HL2:DM, and third party mods).
 **Original (The Ship)
 *[http://www.metamodsource.net/dox/ 1.6 API], contained in <tt>core</tt>.  This is the API you should use if you're building against the following Source engines:
-**Orange Box (Team Fortress, Day of Defeat, Garry's Mod)
+**Orange Box (Team Fortress, Day of Defeat, Garry's Mod, CS:S)
 **Left 4 Dead
 It is important to get this right.  The two APIs are not compatible, and if you wish to write a plugin that work across all engines, you must take special care in your plugin as a few API calls were renamed along the way.

← Older revision		Revision as of 07:29, 26 November 2008
Line 15:		Line 15:

	While a stub Metamod:Source plugin may look bare, it is easy to re-implement the functionality provided by <tt>IServerPluginCallbacks</tt>, and this is done so in the [[Sample Plugins (Metamod:Source)\|Sample Plugins]].		While a stub Metamod:Source plugin may look bare, it is easy to re-implement the functionality provided by <tt>IServerPluginCallbacks</tt>, and this is done so in the [[Sample Plugins (Metamod:Source)\|Sample Plugins]].
		+

	=Plugin API=		=Plugin API=

← Older revision		Revision as of 07:12, 26 November 2008
Line 27:		Line 27:
	It is important to get this right. The two APIs are not compatible, and if you wish to write a plugin that work across all engines, you must take special care in your plugin as a few API calls were renamed along the way.		It is important to get this right. The two APIs are not compatible, and if you wish to write a plugin that work across all engines, you must take special care in your plugin as a few API calls were renamed along the way.

−	More information is available in the article [Engine Portability and MM:S Plugins].	+	More information is available in the article [[Engine Portability and MM:S Plugins]].

@@ Line 16: / Line 16: @@
 While a stub Metamod:Source plugin may look bare, it is easy to re-implement the functionality provided by <tt>IServerPluginCallbacks</tt>, and this is done so in the [[Sample Plugins (Metamod:Source)|Sample Plugins]].
-=Plugin API=
+It is important to get this right.  The two APIs are not compatible, and if you wish to write a plugin that work across all engines, you must take special care in your plugin as a few API calls were renamed along the way.
-In order to write a plugin, you must implement the ISmmPlugin interface, similar to IServerPluginCallbacks.  An example of implementing this can be seen in the <tt>stub_mm</tt> sample plugin/
 Once you've implemented the interface, you must also have a global singleton of your plugin available. There are a few macros to assist you in properly exposing the interface as a DLL and setting up the API states.