Contents

Components

Versions of the latest stable release. Every release lists its own on the Changelog page.

The pack includes the language modules its plugins are written in, so when a plugin in another language joins the build, for example JavaScript, its language module joins too.

Layout on disk

The archive is extracted into the server's game/ folder. Example for the Launcher host on Linux:

Differences between hosts:

• Runtime: instead of s2launcher, the host is csgo/bin/linuxsteamrt64/libserver_valve.so.
• Metamod: nothing goes into bin/; csgo/addons/metamod/plugify.vdf loads csgo/addons/plugify/bin/<platform>/libplugify.

The translations of the base plugins in data/ come with the full archive only: mamba doesn't update them, and the host-only archive doesn't contain them.

Meta-packages

The build's set is recorded with conda itself. plugify-source2-plugins (in envs/plugins) and plugify-source2-modules (in envs/modules) are packages without files that depend on the exact versions of the build's packages. Their version is the build version. mamba list shows which build is installed, and mamba update moves the set to the next build, see Updating.

.condarc and build.json

addons/plugify/.condarc lists the build's conda channel first, then the channels of the components and of every language module. That is why these packages are installed by name, without -c. Packages from other channels need -c.

addons/plugify/build.json records which build the host came with, and the host and core versions.

Adding packages

envs/modules and envs/plugins are ordinary conda environments. Package operations run while Plugify is unloaded:

plg unload
mamba install -n modules plugify-module-python3
mamba install -n plugins -c "https://example.github.io/my-plugin/" my-plugin
plg load

If the build has a version of the package, that version is installed. Other packages come from their own channels: the ones listed in .condarc, or the one passed with -c.

You can also keep your plugins in an environment of your own, because Plugify finds packages in every folder of envs/:

plg unload
mamba create -n my-plugins
mamba install -n my-plugins <package>
plg load

Plugins without a package go into a folder of their own in envs/, for example envs/my_plugin/.

Packages you add this way are kept when you update the build. If you write plugins in a language whose module the build might drop later, install that module explicitly (mamba install -n modules plugify-module-golang), so it stays installed.