Troubleshooting
Fixes for the most common KRISPSHOT Loadouts setup problems.
Start with these two console commands; they say what's loaded and what isn't:
server console
css_studio_status
css_license| What you see | What to do |
|---|---|
| "The loadout menu is unavailable on this server right now" | The licence isn't valid. css_license says why; see Your licence key. |
| "The loadout menu is still starting up" | The item list or database isn't ready. css_studio_status says which. Usually the database login is wrong. |
You need to setup Database credentials | Fill in DatabaseHost, DatabaseUser, DatabasePassword and DatabaseName. |
| Typing !skins does nothing at all | The plugin didn't load. Check css_plugins list and that CounterStrikeSharp is 1.0.375 or newer. |
| The menu doesn't appear, or the cursor appears without a window | The player doesn't have the Workshop addon. Check WorkshopAddonId is <Workshop ID from your portal>, that MultiAddonManager is loaded (css_studio_status), and reconnect. |
| Players see an older menu version | They have an old Workshop download. Make sure the server uses the current ID; the player can delete steamapps/workshop/content/730/<old ID>. |
| Signature errors, or skins stopped applying after a CS2 update | Update CounterStrikeSharp and the plugin. See Updating. |
| Skins flicker or reset | WeaponPaints is still installed. Remove it. |
| The website changes don't show in game | The website must write to wp_player_refresh. See Website sync. |
css_license says offline | The server can't reach the licence server over HTTPS. Ask your host whether outbound connections on port 443 are blocked. |
css_license says limit | The key is in use on another server, perhaps your old one or a changed port. Release it in the portal. |
Still stuck? Contact us with the output of both commands.