CS:GO plugin does not load: dependency-first diagnosis

CS:GO plugin does not load: dependency-first diagnosis. Version-specific steps, checks, rollback, and upstream sources for Source 1 (CS:GO branch).

Counter-Strike: Global OffensiveSource 1Legacy

SHORT ANSWER

Diagnose Counter-Strike: Global Offensive plugins from the loader outward: stock server, framework, extension/runtime dependencies, then the plugin. Use `meta version`, `sm version`, and `sm plugins list` in the server console and the first load error; repeatedly overwriting files without reading the loader result destroys useful evidence.

Before you change anything

A legitimate Steam installation or dedicated-server installation for Counter-Strike: Global Offensive.
A backup of every file that will be changed.
Access to the local client console or the dedicated-server console, as appropriate.

Version-specific procedure

Reproduce the failure on a maintenance instance cloned from the current server.
Disable the failing plugin and confirm that the framework itself loads.
Run `meta version`, `sm version`, and `sm plugins list` in the server console and save the complete output.
Check the plugin’s upstream release notes for the current game build, operating system, architecture, and dependency versions.
Reinstall the plugin into a clean staging copy and enable it alone before restoring other plugins.

Verify the result

The framework baseline succeeds without the plugin.
The first explicit loader/dependency error is identified.
The plugin is tested alone on the current game build.

Rollback

Keep the plugin disabled and restore its config/data from the pre-test copy if the staged upgrade is incompatible.

Common pitfalls

Do not download replacement binaries from forum mirrors when the upstream project provides releases.