Vanguard

Feedback

Report a bug or ask for a feature. No account or email is needed, and you see exactly what's sent before it goes.

Send a report

The form needs JavaScript. Turn JavaScript on to send a report from this page. Until then, get your report ready with the steps and templates below, and keep it.

What would you like to send?

For example: Raid frames go blank after a reload. 8 to 100 characters.

Bug report

No Vanguard version has /vg report yet, so paste the lines of /vg status and /vg errors: see the steps below. Up to 20,000 characters.

Up to 2,000 characters.

Up to 1,000 characters.

Up to 2,000 characters.

Screenshots can't be sent with this form yet: describe what you see instead.

Where your report goes
  • No account or email is needed.
  • Your report is sent to the private repository the Vanguard maintainers use. Only the project's maintainers can read it. It is not posted anywhere public.
  • A pasted report can hold character or profile names, chat, or guild details. Check the preview, and take out anything you'd rather not send.
  • If you tick "OK being contacted", your Discord tag or email is kept privately for 90 days and is never put in the report.
  • Your IP address is never stored or put in a report. To stop floods, the site keeps a scrambled key made from it for an hour or two, and that key changes every day.
  • To have a report removed, send another report with the title “Remove VG-…” and your reference. A maintainer deletes it.
  • Every report gets its own reference, shown only to the person who sent it. If yours was added to an earlier report of the same error, your reference is on your part alone, so a removal request covers only what you sent.

Get your report ready

steps and templates

Report a bug

  1. Write down what you did, what you expected, and what happened instead.
  2. Type /vg status and copy all of its lines. In v0.3.0 it prints 2 lines: the version, profile and module count, then skins, painted frames and changes waiting on combat. Next release prints 5, adding the client, what it has, and your UI scale and text size.
  3. Copy any error lines. v0.3.0 has no /vg errors yet; if chat showed “module … failed to load: …”, copy that whole line. Next release /vg errors lists the errors Vanguard caught this session, with stacks and counts, ready for a bug report.

Can't copy text from chat? Type out the lines that matter, or describe them. In the next release, /vg copy opens the recent chat as plain text, ready to copy.

Bug report template

Vanguard bug report
What I did:
What I expected:
What happened instead:

/vg status (paste every line):

/vg errors (paste every line; on 0.3.0, paste any "failed to load" line from chat instead):

Screen resolution and UI scale (if you know them):

Request a feature

Tell us what would make Vanguard better for you. Please answer:

  1. What you want.
  2. Which part of Vanguard it touches: a module from Features, a command or a setting.
  3. Why it would help you.

Reviewed, not promised. Every request is read and considered, but there's no promise that it will be built, or when.

Feature request template

Vanguard feature request
What I want:
Which part of Vanguard it touches (a module from the Features page, a command, or a setting):
Why it would help me:

Before you ask, check Features: some things are already written for the next release (turn on Show what's coming in the sidebar to see them).

Source

Source: Core/Slash.lua (status, errors), Core/Modules.lua, docs/SMOKE-TEST.md (Report block), README.md in the Vanguard addon repository.