darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: Metamod Release Notes
darope@0:
darope@0:
darope@0:
darope@0: Release Notes
darope@0:
darope@0:
ds@275:
ds@275: Major changes with Metamod 1.20
ds@275:
ds@275:
ds@275: - New versions of HalfLife do not use '_i386' in the names of the
ds@275: Linux game dll anymore. Metamod changed the lookup for game dlls in that
ds@275: it first tries to strip anything after the last underscore ('_') in the
ds@275: game dll and load that dll. If that file does not exist it falls back
ds@275: to the old name for backwards compatibility.
ds@275:
- The HalfLife engine employs this stripping of the dll name on the
ds@275: setting found in the liblist.gam file, too. That means that it will
ds@275: look for metamod.so, even if the liblist.gam file lists
ds@275: metamod_i386.so. Unlike Metamod, the engine will not fall back to the
ds@275: old name and fail to load Metamod if it can not be found under
ds@275: metamod.so. Therefore we are adding a symbolic link to the tarball.
ds@275: When you unpack the tarball to your dlls directory you will get a link
ds@275: of name metamod.so so that engine loading can work with the newer
ds@275: engine, too. Should you install/update your Metamod dll by hand, you
ds@275: will need to make sure that a newer engine can find the dll under
ds@275: metamod.so, either by renameing the file or by creating a link to it.
ds@275: This does only apply to Linux. The Windows file is still called
ds@275: metamod.dll.
ds@275:
ds@275:
ds@275:
ds@275:
darope@250:
darope@250: Major changes with Metamod 1.19
darope@250:
darope@250:
darope@250: - New API version, with one new API function for client cvar querying and another
darope@250: for calling hook functions.
darope@250:
darope@250:
darope@250:
darope@250:
darope@248:
darope@248: Major changes with Metamod 1.18
darope@248:
darope@248:
darope@248:
darope@248:
darope@248: - New API version, with three new API functions for loading and
darope@248: unloading plugins from other plugins, and one new function for checking client cvar queries.
darope@248:
darope@248:
- Support for new HLSDK API engine functions QueryClientCvarValue and CvarValue for querying client cvars.
darope@248:
darope@248:
- Console command "meta version" shows the plugin interface version.
darope@248:
darope@248:
darope@248:
darope@248:
darope@248:
darope@0:
darope@0: Major changes with Metamod 1.17
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: - New cvar "metamod_version" that can be queried from
darope@0: client game browsers.
darope@0:
darope@0:
- New console commands available to clients (much like the existing
darope@0: server console commands):
darope@0:
darope@0:
darope@0: - "meta version" prints out version information
darope@0: (date, compile type, etc).
darope@0:
- "meta list" shows a list of the plugins running on
darope@0: the server (name, author, version, etc).
darope@0:
darope@0:
darope@0: - New file config.ini to provide a
darope@0: more reliable and flexible method of specifying configuration options.
darope@0: At the moment, the recognized options mirror those from +localinfo, ie:
darope@0:
darope@0:
darope@0:
darope@0: - debuglevel <number>
darope@0:
- gamedll <path>
darope@0:
- plugins_file <path>
darope@0:
- exec_cfg <path>
darope@0:
darope@0:
darope@0: Default path is "addons/metamod/config.ini" but can be
darope@0: overridden with "+localinfo mm_configfile".
darope@0:
darope@0:
Also, new console command "meta config" to display this
darope@0: information.
darope@0:
darope@0:
- New console command "meta require" to force the
darope@0: server to exit if the specified plugin isn't loaded/running. Intended for
darope@0: use in server.cfg or metaexec.cfg, to keep the server from starting up if
darope@0: desired plugins don't load. For example:
darope@0:
darope@0:
darope@0:
darope@0: - meta require adminmod
darope@0:
- meta require 1
darope@0:
darope@0:
darope@0: The former requires that a plugin with the substring "adminmod" is found
darope@0: loaded and running. The latter requires that the plugin in slot 1 is
darope@0: loaded and running.
darope@0:
darope@0:
- If an override gamedll is specified and found to be invalid or
darope@0: missing, Metamod will now exit with an appropriate error message, rather
darope@0: than just falling back to the auto-detected gamedll. This should provide
darope@0: more immediate and useful feedback, and help prevent some confusion.
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: Incompatible changes with Metamod 1.13
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: - Config file metagame.ini is no longer supported. This
darope@0: file was deprecated in Metamod 1.08 (2001/06/16). Use instead the "+localinfo mm_gamedll" option.
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: Major changes with Metamod 1.13
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: - New config file names and locations, per the Addon
darope@0: Development Standard rev 1.00, developed on the hlds_apps
darope@0: list.
darope@0:
darope@0:
Default config file locations are now:
darope@0:
darope@0: - $gamedir/addons/metamod/plugins.ini
darope@0:
- $gamedir/addons/metamod/exec.cfg
darope@0:
darope@0:
darope@0: Previous config file locations are also supported for backwards
darope@0: compability:
darope@0:
darope@0:
darope@0: - $gamedir/metamod.ini
darope@0:
- $gamedir/metaexec.cfg
darope@0:
darope@0:
darope@0: Note that the pathnames in plugins.ini are unchanged, and are still
darope@0: relative to the gamedir.
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0:
darope@0: