The !Specs Command: Answer the Question You Get Every Stream

What Does the !Specs Command Do?

The !specs command posts your PC hardware into chat — CPU, GPU, RAM, and usually your monitor and peripherals. It's a static text command, the simplest kind there is: no API, no authorisation, no live data. You write the string, the bot repeats it.

What makes it worth its own guide isn't the setup, which takes ninety seconds. It's what goes in the string. A spec command is one of the few pieces of copy on your channel that gets read by nearly every new viewer who sticks around, and most streamers waste it — either by dumping an unreadable wall of part numbers, or by writing it once in 2022 and never updating it after two upgrades.

It also sits at the crossover between an informational command and a commercial one. Unlike !rules or !uptime, this one answers a question where the asker is often about to spend money — they're asking because they're considering the same part. That makes it the single most monetisable static command most channels have, and the last section covers how to handle that without annoying anyone.

The command usually arrives with siblings: !setup, !pc, !gear, !mic, !cam, !keyboard, !chair. Some should be aliases of the same command and some should be their own, and getting that split right is most of the work.

Why This Question Never Stops

Ask any streamer what chat asks most and the hardware question is at or near the top, alongside the game name and how long you've been live. There's a structural reason: it's the safest possible question for a new viewer to ask. It's factual, it can't be a wrong opinion, it doesn't require having watched for any length of time, and it's a genuine conversation-starter with someone whose setup you can see working.

Which means the question isn't really about your PC. It's about entering the conversation, in the same way !8ball gives people something safe to type. That's why answering it out loud never stops the asking: you're answering the surface question for the people currently listening, while the underlying need — a low-risk way to say something — keeps producing new askers all stream.

Answering by voice has three specific failure modes. It only reaches whoever is listening at that second; it interrupts whatever you were doing, which on a competitive game means dying mid-sentence; and it forces you to recite eight part numbers you half-remember, so you skip details and the follow-up questions start. A command fixes all three at once and, crucially, it's asynchronous — the person who arrives twenty minutes later gets the identical answer without costing you anything.

There's a secondary benefit worth naming. When a viewer types !specs instead of asking you directly, your regulars learn to point newcomers at commands too — “just type !specs” becomes a thing chat says to each other. That's a small piece of your community starting to answer its own questions, which is exactly the direction you want a chat to move in.

Formatting a Spec List That Chat Can Actually Read

Start with the hard constraint: chat messages have length limits, and they differ per platform. Twitch caps a message at 500 characters, YouTube Live is considerably shorter at roughly 200, and a bot response that exceeds the limit gets truncated or dropped entirely rather than politely wrapped. If you stream to more than one platform, write to the shortest limit — a spec list that works on Twitch and vanishes on YouTube is worse than a short one that works everywhere.

Then cut ruthlessly. Nobody needs your PSU wattage, your case model or your RAM timings. The parts people ask about are CPU, GPU, RAM capacity, and — separately, and more often than you'd expect — your microphone and camera. Everything else is padding that pushes the useful information off the end of the message.

Use a consistent separator so it scans in one pass. Pipes or bullets beat commas, because commas already appear inside part names: CPU: Ryzen 7 7800X3D | GPU: RTX 4070 Ti | RAM: 32GB DDR5 | Mic: Shure SM7B reads faster than the same content in a sentence. Drop marketing words — “NVIDIA GeForce RTX 4070 Ti Super Founders Edition” is four words longer than anyone needs.

When the list genuinely won't fit, split it rather than truncating it. !specs for the internals, !gear for audio and video, !peripherals for keyboard, mouse and chair. Then make the obvious singles into their own tiny commands — !mic, !cam, !keyboard — because a viewer who only wants your microphone shouldn't have to read your GPU to find it. Keep !setup and !pc as aliases of !specs rather than separate commands with their own drifting copy.

Finally, put a date or a link at the end. “Full list: yoursite.com/gear” costs 30 characters and absorbs every follow-up question, and it means the chat command never has to carry the complete answer. Diarise an update after every hardware change — a spec command listing a GPU you sold last year is the kind of small inaccuracy that quietly costs you credibility with exactly the audience most likely to notice.

Turning !Specs Into a Gear Page

People asking about your hardware are, disproportionately, people about to buy hardware. That makes a gear page one of the more natural revenue additions available to a small channel — no sponsorship negotiation, no minimum audience, and the traffic arrives with intent already formed.

The pattern that works: keep the chat response short and factual, and point at a page that carries the detail and the links. Retailer affiliate programmes are the usual mechanism, and the page format is simple — part name, one line on why you use it, link. Doing it this way also solves a practical problem, since bots posting long URLs into chat get caught by link filters and shorteners get flagged as suspicious. One clean link to your own domain avoids both.

Two things to get right. First, disclose the relationship. Affiliate arrangements generally have to be disclosed to your audience, and the specific requirements depend on where you and your viewers are — a plain line on the page saying the links earn you a commission is the baseline, and worth checking against the rules that apply to you. Second, only list what you use. The value of this command is that it's an honest answer to an honest question; recommending a headset you've never worn converts once and costs you the trust that made anyone ask in the first place.

If you're not ready for affiliate links, the page is still worth having. It's a permanent home for information that would otherwise live only in a chat command, it gives you somewhere to put photos and reasoning that a 200-character message can't carry, and it's a page search engines can find — unlike a chat message, which is invisible to everything except the people in the room.