Classic bot messages are an embed with a row of buttons stuck underneath. Discord Components V2 puts the text, images, buttons and dropdowns inside one container, so a ticket panel, a player card or a product listing reads as a single card instead of a box with controls bolted on. Noxyr supports both, lets you choose per feature, and reposts live panels when you switch so nothing breaks.

Side by side: the classic V1 embed with buttons underneath, and the V2 layout where buttons and menus live inside the card. A switch flips between them. V1 · classic embed Open ticket FAQ Choose a department ▾ buttons sit under the embed V2 · Components V2 container Open ticket FAQ Choose a department ▾ everything inside one card buttons and menus live in the card /style set

What Components V2 actually is

Components V2 is Discord's newer message layout system. Instead of the old split between "the embed" (text, colour, images) and "the components" (buttons and select menus in rows below it), a V2 message is built from layout blocks: a container with an accent colour, text blocks, sections that pair text with a button or a thumbnail, separators, media galleries and the familiar buttons and dropdowns, all nested inside. The result looks tighter, especially on mobile, and the controls sit next to the thing they act on.

The catch is that a single message cannot mix the two systems: a message with V2 components cannot also carry a classic embed. That is why bots have to commit per message, and why Noxyr tracks the choice per feature.

V1: the classic embed

  • Familiar to every Discord user since 2016; nobody has to learn a new shape.
  • Works everywhere, including older clients and bridges.
  • Buttons and menus sit under the embed in up to five rows.
  • Titles, fields and footers give a lot of structure for free.

V2: the container layout

  • Buttons and dropdowns live inside the card, next to the text they relate to.
  • Cleaner on mobile; less vertical space between the message and its controls.
  • Separators and sections make long panels (a catalog page, a help menu) easier to scan.
  • Some things move: the classic title/field grid is replaced by text blocks and sections.

How Noxyr handles it

Every server has a default style for buttons and a separate default for dropdown menus, plus optional overrides per feature: tickets, catalog and checkout, verification, reviews, suggestions, polls, the music player, welcome and leave messages, help and public commands, and direct messages. Servers that existed before V2 shipped stay on V1 until an admin changes it; servers that add Noxyr now start on V2. Giveaways always use the classic layout, since their message format depends on it.

Switching is one command or one dashboard page (Buttons & Menus under Control):

  • /style view: what every feature is currently using.
  • /style set feature:all buttons:v2 dropdowns:v2: whole-server default.
  • /style set feature:tickets buttons:v1: one feature only.
  • /style reset: drop the overrides so features follow the server default again.

By default a change reposts your live panels, ticket panels, the catalog, verification and the rest, so members see the new layout straight away rather than after the next edit. Pass repost:false if you would rather have panels switch the next time they are saved.

Which should you pick?

  • Public-facing panels (tickets, verification, catalog): V2. Members interact with these most and the in-card buttons are easier to hit on a phone.
  • Music player: V2. The controls belong on the card.
  • Welcome and leave messages: either; V1 if you rely on a big banner image with a field grid under it.
  • Anything a screen reader or an older client depends on: V1 is the safer choice.

Because the choice is per feature, you can move one panel at a time and ask members what they think before flipping the server default.

Common questions

Do I lose anything by switching? No settings change; only the layout of the posted messages does. Switching back is the same command.

Does my custom bot follow the same setting? Yes. The style is stored on the server, so your custom bot and Noxyr post the same layout there.

Why is a dropdown message using a different style than a buttons message? A message cannot mix systems, so a message with a dropdown follows the dropdown setting and a buttons-only message follows the button setting.

Try it: open the dashboard, go to Buttons & Menus, and switch your ticket panel to V2. The buttons vs dropdown guide covers what goes on the panel itself.