A Discord bot dashboard is a UI still, not a community clip

The listing is the settings grid: commands, permissions, latency. Qwen holds the UI type. Discord community clips are a different object.

A bot that sells is a screen: slash commands, role gates, a latency number a buyer will proof against the live panel. That screen is already a still. Motion is optional. A constructed moderator laughing in a voice channel is a community clip. It is not the dashboard.

The settings grid is the listing

Digital tools have no unboxing. The fear is a thin file and a fake panel. Capture the real dashboard you would ship: command names matching the docs, permission strings matching the bot, latency matching a reading you will stand behind. Crop chrome that is not the SKU. Crop other people’s server names if a test guild leaked one. The still is a document. Treat it like one.

Do not prompt a video model to “show a premium Discord bot dashboard with a glowing latency badge.” It will invent a cousin client, a cousin command list, a cousin millisecond. A buyer who lands on the real panel and sees a different slash set is not looking at creative. They are looking at a lie.

If you do not have a screenshot yet, you still do not invent a community. You typeset a mock of the grid. Quote every string a buyer will proof: /ban, Manage Messages, the latency as you will actually show it. A photoreal founder pointing at a laptop is a host. The SKU is the screen.

Qwen holds the UI type

Qwen Image 3 Text to Image is the stills row when the letters have to read. Catalog facts: Qwen’s third-generation image model, strong prompt adherence, complex text rendering in Chinese and English, intelligent prompt rewriting on by default, 4 credits, 2K max, qualities 1K and 2K. No audio. No duration. Aspects include 1:1, 16:9, 9:16, and 21:9.

Write the exact strings. If a command name or a permission line must stay verbatim, say so in the prompt and inspect the still. Rewriting is a help for scene language, not a licence to paraphrase /kick into /remove. Set 1K while the words are in draft. Set 2K when the grid is the grid. There is no 4K chip on this row.

A video model is a bad typography engine. It will give you almost-commands and a panel you cannot ship. Approve the characters. Then consider motion.

Generate an image from text is the named agent job: you describe the still, the agent asks about style, aspect ratio, and count, then picks a model. Cost is priced per model, shown before you confirm. Name Qwen. A bare “make a Discord dashboard” will land on a portrait row. Quote the grid. Scout at 1K. Keep at 2K when someone will zoom. Proof at 100%. One wrong character in a command name is a regenerate. Qwen typesets a picture of a screen. It is not your bot.

Overlay the number that will change

Latency, guild count, a version chip, a sale line — those strings move. Generated type inside a video is a misspelled millisecond you cannot edit without a new generate. Burn the string after picture lock.

Add a text overlay burns one authored line for the whole clip: hook, headline, CTA, the latency, the command that is the hook. You write the line. Position is top, center, or bottom. It does not transcribe. A mute screenshot has nothing to listen to.

The agent verb is add a text overlay to my video: give it the file, the exact line, and the position. One string, whole duration. Cost is a flat per-video fee, shown before rendering. If you needed three different lines at three timestamps — “commands,” then “permissions,” then the latency — that is timed overlays, not one persistent badge.

Crop to the ratio you will ship before you overlay. Do not overlay a latency you cannot point at a real reading for. If the printed ping is already sharp, you may not need an overlay. Do not let a video model “enhance” the glyphs.

Community clips are a different object

Discord server promo is already the community object: events, a reel of the living room, the clip as a file you share in a channel that allows it. Community-manager work is that object. This page is the bot dashboard. Do not twin a server-promo playbook onto a settings grid. Do not generate a voice hang with invented faces so the bot “feels social.” Those faces are a cast you did not clear. Empty panel. Letter the commands. Overlay the ping.

A cinematic “mod team reacting to a raid” is talent and a likeness problem. You do not need that mouth. The grid already is the CTA. If a human must speak, it is a real named maintainer on a different day.

Do not text-to-video a neon lounge with a glowing “Add Bot” button. Do not bake the ping into the generate so a better reading forces a new take. Change the number with an overlay. Change the command set with a new screenshot or a new Qwen still. Keep the community off this plate.

FAQ

Can I generate a prettier dashboard instead of capturing the live panel?

You can typeset a mock on Qwen Image 3 at 4 credits, 2K, if you quote the real strings and proof them. You cannot invent commands, permissions, or a latency. The live screenshot is the honest SKU. Overlay the production number if the mock is only a crop.

Should the agent pick the image model for me?

Generate an image from text will pick a fitting row unless you name one. For a settings grid, name Qwen. A portrait model will give you a mood of a server, not a panel you can proof.

Is overlay the same as auto-captions on a voiceover?

No. Overlay burns a line you wrote. Auto-captions transcribe speech. A mute dashboard has nothing to transcribe. If you later record a real maintainer, caption that file separately.

Is a Discord community clip the same job as this listing?

No. Community clips are events, hangouts, a server-promo file. This listing is the settings grid: commands, permissions, latency. Qwen letters the UI. Overlay the number that will change. Do not populate the panel with generated members.