Metamod 1.19 has been released.


2006-04-17 1.19

  - Added support for new HLSDK API functions QueryClientCvarValue2() and
    ClientCvar2(). The helper function IS_QUERYING_CLIENT_CVAR() is now
    deprecated as the old functions QueryClientCvarValue() and
CvarValue()
    are considered obsolete and their use is strongly advised against.
    The helper function IS_QUERYING_CLIENT_CVAR() cannot be used in
    conjunction with the new API function QueryClientCvarValue2().
  - Added GET_HOOK_TABLES() to let plugins make interceptable engine/dll
    calls.
  - Added MAKE_REQUEST_ID() to assist plugins in generating request ids
    for QueryClientCvarValue2().
  - Added mod support for Move In! 1.0.
  - Added mod support for Special Death Match Alpha 2.0.
  - Fixed a bug where Windows DLL load failures produced an empty
message.
  - Fixed a bug where plugins could not catch NewDLL calls for GameDLLs
that
    do not provide NewDLL information.
  - Fixed a bug corrupting memory when using Metamod with engines or game
dlls
    with a different interface than the one compiled against, e.g. older
engines.

--
Florian Zschocke

Metamod 1.20 has been released

Changes:

2013-02-16 1.20

  - Changed loading of Linux game dll to first try to find the dll under
    known name with the last '_*' part stripped out. Falls back to the
    old known name if a file with the stripped name is not found.
  - Added Mod support for Half-Life 1.5: Weapon Edition version 1.5.0.5.
  - Added additional entities for Stargate TC 1.0g.


Note:

New versions of HalfLife do not use '_i386' in the names of the Linux
game dll anymore. The HalfLife engine strips anything after an
underscore
from the dll name found in the liblist.gam file. That means that it will
look for metamod.so, even if the liblist.gam file lists metamod_i386.so.
Unlike Metamod, the engine will not fall back to the old name and will
fail to load Metamod if it can not be found under metamod.so.
Therefore we added a symbolic link to the tarball. When you unpack the
tarball to your dlls directory you will get a link of name metamod.so
to metamod_i386.so, so that engine loading keeps working with the new
and
old engines.
Should you install/update your Metamod dll by hand, you will need to
make
sure that a newer engine can find the dll under metamod.so, either by
renaming the file or by creating a link to it.
This does only apply to Linux. The Windows file is still called
metamod.dll.

--
Florian Zschocke