|
darope@0
|
1 |
<!-- vi: set ts=4 sw=4 : --> |
|
darope@0
|
2 |
<!-- vim: set tw=75 : --> |
|
darope@0
|
3 |
|
|
darope@0
|
4 |
<HTML> |
|
darope@0
|
5 |
<head> |
|
darope@0
|
6 |
<title>About Metamod</title> |
|
darope@0
|
7 |
</head> |
|
darope@0
|
8 |
<body> |
|
darope@0
|
9 |
|
|
darope@0
|
10 |
<h1>Metamod |
|
darope@0
|
11 |
</h1> |
|
darope@0
|
12 |
|
|
darope@0
|
13 |
<h2>a Half-Life utility mod</h2> |
|
darope@0
|
14 |
|
|
darope@0
|
15 |
<pre> |
|
darope@0
|
16 |
<b>meta</b> /me't*/ <i>or</i> /may't*/ <i>or</i> <i>(Commonwealth)</i> /mee't*/ <i>adj.,pref.</i> |
|
darope@0
|
17 |
<i>[from analytic philosophy]</i> <b>One level of description up.</b> |
|
darope@0
|
18 |
</pre> |
|
darope@0
|
19 |
|
|
darope@0
|
20 |
<p> The purpose of MetaMod is to function "one level up" from the normal |
|
darope@0
|
21 |
Half-Life game mod DLL. Sitting between the mod game DLL and the Half-Life |
|
darope@0
|
22 |
engine/binary, it intercepts the function calls between the two, with the |
|
darope@0
|
23 |
option of passing them along untouched, as well as passing them on to as |
|
darope@0
|
24 |
any number of <b><i>additional mod-like DLLs</i></b>. |
|
darope@0
|
25 |
|
|
darope@0
|
26 |
<p> Thus, you can actually have multiple "mod-like" DLLs in operation at |
|
darope@0
|
27 |
one time. I say "mod-like" because these additional DLLs (we'll call them |
|
darope@0
|
28 |
"plugins") are not intended to provide a full "game"; that functionality is |
|
darope@0
|
29 |
still provided by the "game dll". However, these plugins can <b><i>add |
|
darope@0
|
30 |
to</i></b> or <b><i>modify</i></b> the functionality provided by the game |
|
darope@0
|
31 |
dll, or by the engine itself - for instance, adding new server commands, or |
|
darope@0
|
32 |
new client commands, or even disabling commands built into the game dll. |
|
darope@0
|
33 |
Although the plugin isn't intended to provide full HL-game functionality, |
|
darope@0
|
34 |
since it's receiving the same information given to the game DLL, it has the |
|
darope@0
|
35 |
opportunity to do <b><i>anything</i></b> the game DLL can do (given enough |
|
darope@0
|
36 |
coding effort of course). |
|
darope@0
|
37 |
|
|
darope@0
|
38 |
<p> This is very similar to the way Alfred Reynolds' |
|
darope@0
|
39 |
<a href="http://www.adminmod.org">AdminMod</a> works, as it also sits |
|
darope@0
|
40 |
between the engine and game dll, catching routines, and passing them on. |
|
darope@0
|
41 |
thus modifying functionality. However, rather than providing just the |
|
darope@0
|
42 |
additional server features builtin to AdminMod DLL, MetaMod allows you to |
|
darope@0
|
43 |
add features from multiple, separate DLLs. Under that framework, AdminMod |
|
darope@0
|
44 |
can be a plugin itself, and be run alongside numerous other plugins. And, |
|
darope@0
|
45 |
as of version 2.50 of AdminMod, AM has now transitioned to running as a |
|
darope@0
|
46 |
Metamod plugin. |
|
darope@0
|
47 |
|
|
darope@0
|
48 |
<p> |
|
darope@0
|
49 |
<hr> |
|
darope@0
|
50 |
|
|
darope@0
|
51 |
</body> |
|
darope@0
|
52 |
</html> |