Crypto-Strike Plugin Downloads
Install the Crypto-Strike Metamod-P plugin on an approved Counter-Strike 1.6 Linux HLDS server. The public bundle gives you the plugin binary and helper scripts. The private setup packet activates your specific server.
Servers MUST be whitelisted on chain through Discord before they can connect to the Crypto-Strike network. Public download first, approved activation second.
Download cryptostrike-plugin-v0.0.0-71c56735aa32-linux-i386-hlds.zip ⬇️
- Build ID
- v0.0.0-71c56735aa32
- Version
- 0.0.0
- Platform
- linux-i386-hlds
What You Get
cryptostrike_mm.so- the Linux i386 Metamod-P plugin.preflight.sh- checks your server folder, Metamod install, plugin artifact, and bridge reachability before copying files.install.sh- copies the plugin/config/key files and safely adds the Metamod loader line.cryptostrike.cfg.template- a public example only. Use the approvedcryptostrike.cfgfrom your private setup packet for a live server.
Recommended and Tested Stack
- Counter-Strike 1.6 Linux HLDS, tested with server build 10211.
- Metamod-P v1.21p109, built and validated against the bundled HLSDK headers from that tag.
- Linux i386 plugin loading enabled on the host/container.
- Writable cstrike/addons/metamod/plugins.ini with liblist.gam routed through Metamod-P.
- Outbound HTTPS access to https://crypto-strike.eterra.online for bridge health and settlement posts.
- Optional AMX Mod X with CSX/stats_logging.amxx for accuracy and rival stat enrichment.
Before You Touch Files
- Know your HLDS root path. It is the folder that contains cstrike/. Common examples are /home/steam/hlds, /opt/hlds, or the mounted server directory inside your Docker project.
- Confirm Metamod-P is already installed. Crypto-Strike is a Metamod plugin, so plain HLDS cannot load it by itself.
- Have permission to edit cstrike/addons/metamod/plugins.ini and restart HLDS.
- Keep the private setup packet private. Do not publish server.key or paste it into public issue trackers, Discord channels, or screenshots.
Install Flow
- Join Discord and request Crypto-Strike server operator onboarding.
- Provide your operator wallet, public server IP, connect/query port, server display name, region, contact handle, and desired launch window.
- Wait for on-chain whitelist activation and a private setup packet. The setup packet includes your server ID, a ready-to-use cryptostrike.cfg, and server.key.
- Download the public zip. This zip is safe to share, but it cannot activate a server by itself.
- Unzip the bundle, run preflight, then run install with the private setup packet files.
- Restart HLDS and verify Metamod sees Crypto-Strike RUN, the build ID matches this release, and the server appears online in ops.
Commands
Run this from the directory where you downloaded the public bundle, such as ~/Downloads or your server operator working folder:
Run this from inside cryptostrike-plugin-v0.0.0-71c56735aa32-linux-i386-hlds before installing. Replace /path/to/hlds with the HLDS server root that contains cstrike/.
Run this from inside cryptostrike-plugin-v0.0.0-71c56735aa32-linux-i386-hlds after Discord approval, using the private setup packet files. The server cannot join the network until the server ID and operator wallet are whitelisted on chain.
What install.sh Changes
- Copies cryptostrike_mm.so into cstrike/addons/cryptostrike/dlls/.
- Copies cryptostrike.cfg and server.key into the Crypto-Strike config folders.
- Appends the Metamod plugins.ini line only if it is not already present.
- Does not whitelist your server, create your private key, or restart HLDS for you.
After restarting HLDS, enter these commands in the HLDS console or through RCON to confirm the plugin is loaded and reading the deployed build.
The Metamod plugins.ini line is added automatically by install.sh. It is shown here only for manual repair or troubleshooting:
If Something Fails
- If preflight fails, fix that first. It is designed to stop before changing server files.
- If meta list does not show Crypto-Strike RUN after restart, check cstrike/addons/metamod/plugins.ini and the HLDS console log.
- If the plugin loads but the server does not appear online, confirm Discord approval, chain whitelist activation, server.key, cryptostrike.cfg, and outbound HTTPS.
- If you are using Docker, run the commands from the host path that maps to the HLDS filesystem, not from a random shell inside a stopped container.