Server plugin installed
The FSHost server plugin is installed under CounterStrikeSharp and can refresh equipped Inventory Simulator items.
What matters: Find CS2 teammates through verified account data and checked lobby flow.
Start LFGBuild and equip cosmetic loadouts in CS2 Inventory Simulator, then refresh those items on the TrustedQueue server with the installed CounterStrikeSharp plugin. This is a cosmetic server feature, separate from verified trust, FACEIT context, reports, and teammate reliability.
TrustedQueue can check the public Inventory Simulator equipped-loadout endpoint for your SteamID after Steam sign-in. This does not require your Steam password or personal Steam API key.
The server plugin is the live part. TrustedQueue now gives players a clean route to the simulator and clear instructions for refreshing cosmetics in game.
The FSHost server plugin is installed under CounterStrikeSharp and can refresh equipped Inventory Simulator items.
Players use !ws in game. The plugin controls cooldowns and whether changes apply immediately or after respawn.
The live flow points players to inventory.cstrike.app, where they sign in, choose skins, and refresh them on the server.
Skin choices are not trust, skill, reliability, or moderation data. They should not affect queue eligibility.
Follow this order when you want your simulator loadout to appear on the server.
Use the simulator to sign in with Steam and build the cosmetic inventory or equipped loadout you want to use.
Set the weapon, knife, glove, agent, music kit, graffiti, and other supported cosmetic choices inside the simulator.
Load into the CS2 server after your simulator inventory has been saved and your Steam account is the same one you use in game.
Type !ws in chat to ask the server plugin to refresh your equipped simulator items.
After joining the server, type the command below in CS2 chat. The server plugin fetches your equipped simulator items from the configured Inventory Simulator service.
Cooldowns, immediate refresh behaviour, and spray features are controlled by the server plugin config.
TrustedQueue will not ask for Steam passwords or personal Steam API keys.
Inventory Simulator API keys must stay server-side and never be exposed to the browser.
Cosmetic simulator data is separate from verification, reports, reliability, and risk profile decisions.
If simulated skins are shown, the site should describe them as server cosmetic loadouts rather than owned Steam inventory.
The first page is live guidance. Deeper controls need either a self-hosted Inventory Simulator instance or a provider-issued API key if one becomes available, stored server-side only.
If the simulator provider later offers API keys, TrustedQueue can add a private signed-in handoff without changing the player flow.
TrustedQueue can show a player-safe overview of equipped simulator items without exposing raw third-party payloads.
Admin pages can hold simulator base URL, plugin status notes, and sync health without showing private configuration publicly.
Any future add-item, sign-in, or sync action should be logged so server cosmetic changes are traceable.
Your current plugin setup points at the public simulator and is already enough for players to choose skins, join the server, and refresh with !ws. Website-controlled inventory actions can be added later if a private API key or self-hosted simulator becomes available.