Metamod:Source VDF Files

2008-04-25T03:10:11Z

Smoke66: all

As of Metamod:Source 1.4.3, there is a new automated plugin loading mechanism. This was designed such that plugin authors could distribute uniform packages without any configuration needed on behalf of the user.

The file's extension must be <tt>.vdf</tt> and it must reside in <tt>addons/metamod</tt> (or whatever <tt>mm_basedir</tt> is set to). Plugin authors should choose uniquely identifying names.

The contents of a <tt>.vdf</tt> file must be in Valve's KeyValues format ('''not''' SourceMod's SMC format, which has subtle differences). The file must have a root section called "Metamod Plugin" with one or more properties. The allowed properties:
*"file" - Specifies the file to load as it would appear in <tt>metaplugins.ini</tt>.
*"alias" - Specifiesf the alias as it would appear in <tt>metaplugins.ini</tt>.
admin_menu
The "file" directive is required and "alias" is optional. If an alias is chosen, it should be uniquely identifying (i.e., SourceMod uses "sourcemod" rather than "sm," which could reasonably collide with another plugin).

Example reference contents of <tt>sourcemod.vdf</tt>:
<pre>
"Metamod Plugin"
{
"alias" "sourcemod"
"file" "addons/sourcemod/bin/sourcemod_mm"
}
</pre>

Metamod:Source will auto-correct path separator characters for the platform it's running on.

[[Category:Metamod:Source Documentation]]
[[Category:Metamod:Source Development]]

AlliedModders Wiki - User contributions [en]

Metamod:Source VDF Files