Updating

Update Plugify Source 2 packages with mamba and the host by extracting the host-only archive.

A build is updated in two parts:

  • Packages (language modules and plugins) are updated with mamba from the server console. No archive is needed.
  • The host is updated with the host-only archive, and only when a new build changes it. The Changelog marks such releases.

Your settings in configs/, data/ and logs/, the packages you added yourself and your other environments in envs/ are kept.

Updating packages

In the server console, one command at a time:

plg unload
mamba update -n modules --all
mamba update -n plugins --all
plg load

The build's set is a meta-package: plugify-source2-modules in envs/modules and plugify-source2-plugins in envs/plugins. Its version is the build version, and it depends on the exact versions of the build's packages. So mamba update moves the standard packages to the next build's versions, installs packages the new build added and removes the ones it dropped. Packages you installed yourself are updated from their own channels.

To see which build is installed:

mamba list -n plugins

The plugify-source2-plugins line shows the build version. Every other package that this meta-package doesn't depend on was added by you.

Updating the host

Needed only when the Changelog says the host changed. Update the packages first, then:

Stop the server

Save sentry.jsonc

With the Launcher and Runtime hosts, copy game/bin/<platform>/sentry.jsonc if you changed it. The archive replaces it.

Extract the host-only archive

Download plugify-source2-<host>-<os>-<version>-host-only for your host and OS on the download page and extract it into the server's game/ folder, replacing files. It has no envs/, so your packages stay as they are. It does replace addons/plugify/.condarc, so save it too if you added channels to it.

Start the server

Put back the files you saved, and start the server.

Other operations

Install a specific build version, for example to roll back:

plg unload
mamba install -n plugins plugify-source2-plugins=1.0.0
mamba install -n modules plugify-source2-modules=1.0.0
plg load

Keep a package newer than the build has it: first detach the environment from the build. The packages stay installed, and from then on you manage their versions yourself. The build's channel comes first in .condarc and holds only the build's versions, so take the newer version from the package's own channel with -c:

plg unload
mamba remove -n plugins --no-prune-deps plugify-source2-plugins
mamba update -n plugins -c "https://fr0nch.github.io/permissions-storage/" permissions-storage
plg load

To remove one of the build's plugins, also pass --no-prune-deps. Without it mamba removes the meta-package together with every package it depends on, that is the whole set of the build:

plg unload
mamba remove -n plugins --no-prune-deps plugify-plugin-dyncall
plg load

The meta-package goes away with the plugin, so the environment stops following builds. Installing plugify-source2-plugins again brings both back.

Edit this page on GitHub
Installation
Install Plugify Source 2 on a Counter-Strike 2 server with S2-Launcher, Runtime or Metamod.
Contents
Components of Plugify Source 2 with versions, the layout on disk and how to add your own packages.