AQW Character & Items

AQW Character & Items

Render AQW characters and find items, on Raven-chan and AQWired (not Omni).

8 commands

Running a contest or a tournament

Both are staff events with the same shape: open it, let the field build, run it, close it. The commands in the order you’ll actually use them. The judging table and the full bracket live on this site, because Discord is bad at showing either.

A fashion contest, start to finish

/contest create <title> <mode>
Mods: open it in the contest channel, or from the site’s staff panel, which queues it for the bot to announce. Mode is chosen here and is per contest: voted (a 🗳️ button on every entry) or judged by staff.
/contest submit
Members enter their own images, a render of their character, or both, plus a title and description.
/contest info · /contest withdraw
What’s running and who’s entered · pull your own entry out.
/contest winner <member> <place>
Judged contests: set each placing by hand. Voted ones don’t need it, since the counts decide, but it can still override.
/contest close
Announce the winners in the channel. Entries and results move to the site’s archive.
/contest extend · /contest cancel
Move the closing date when it needs longer · scrap it entirely.

A tournament, start to finish

/tournament create <title> <format>
Mods: open it, here or from the site’s staff panel. Formats: single or double elimination, Swiss, or Swiss into either. Set signups: Staff-entered for a field collected by hand: no sign-up post, no Join button.
/tournament join or /tournament add
Open sign-ups: members join themselves. Staff-entered (or stragglers): you add them, with a user if they’re in the server or an entrant name if they aren’t.
/tournament roster <entrant> <user>
Teams: attach the players behind an entrant. Everyone on a surviving team carries the ping role; elimination strips the whole team. Editable mid-tournament, so subs swap in.
/tournament start
Seed the field (random, or sign-up order) and generate every match, from Discord or the staff panel’s Start button. The shape is fixed from here, so late entries can’t be added.
/tournament result <match> <winner>
Report each match, here or on the site’s staff panel. The bracket advances itself: next pairings announced, ping role pulled off the eliminated.
/tournament drop <user | entrant>
Mid-tournament no-show or DQ: forfeits their live matches to the opponent so the bracket keeps moving.
/tournament close
Finish it and delete the ping role. The bracket stays on the site, and can be embedded on another site with one script tag.
/tournament schedule · format · announce
Move the dates when it overruns · change the format until start · ping everyone still in.

/char

slash
Raven-chanAQWired

Render an AQW character image, a live SWF composite of a player’s gear.

/char [name] [item/format options]
Arguments
  • nameoptional string AQW in-game name (omit if you saved one with /charname).
Examples
/char name: Artix

Calls the charbot-flash-new render service via an async job API. Rate-limited to 4 renders / 60s per user.

/charname

slash
Raven-chanAQWired

Link your AQW in-game name so /char can omit it.

/charname name:<text> [clear:<bool>]
Arguments
  • nameoptional string Your AQW character name to save.
  • clearoptional boolean Remove your saved name.

Also what ties you to your in-game guild row in the officers' guild ↔ Discord report. Verifying, or a nickname that matches, gets you most of the way; this is the explicit link.

/closet

slash
Raven-chanAQWired

Browse saved /char fashion sets.

/closet [user]
Arguments
  • useroptional member Whose closet to view (defaults to you).

/contest

group
Raven-chanAQWired

Fashion contests: enter a look, vote, win. Everything happens in the channel the contest was created in.

Arguments
  • createoptional group Mods: open a contest. Pick a title, a mode (members vote, or judged by staff), an optional description, the channel it runs in, and optionally the date entries close.
  • submitoptional group Enter with up to four of your own images, a render of your AQW character, or both, plus a title and description if you want.
  • withdrawoptional group Pull your entry out.
  • infooptional group What is running and who has entered. Vote counts stay hidden until it closes.
  • winneroptional group Mods: set a placing by hand. This is how a judged contest is decided, and an override for a voted one.
  • extendoptional group Mods: move (or clear) the date entries close. This is the schedule, not the close itself. The site’s calendar follows it, and /contest close is still what ends the contest.
  • closeoptional group Mods: end it and announce the winners in the contest channel.
  • canceloptional group Mods: scrap it without announcing anything.
Subcommands
  • /contest create
  • /contest submit
  • /contest withdraw
  • /contest info
  • /contest winner
  • /contest extend
  • /contest close
  • /contest cancel

Every entry, and every past contest, is on the site at /contests. Ravens staff can also open a contest from the staff panel (and judge it there, entries side by side). The bot still posts the announcement in the channel, within about half a minute of the form. One contest runs at a time on free servers; premium servers can run several, and every command then gains a contest picker for which one you mean, with one running, nothing changes.

/tournament

group
Raven-chanAQWired

PvP tournaments: sign up, get seeded, play the bracket. The full bracket is drawn on the site.

Arguments
  • createoptional group Mods: open a tournament. Title, format, the channel it runs in, and optionally the entry window and dates. The bot makes a mentionable ping role for entrants. signups picks how the field is built: Open posts a sign-up embed with a Join button; Staff-entered posts nothing, and you build the field with /tournament add or the website, for entries collected by hand.
  • joinoptional group Enter the tournament taking sign-ups, or tap Join on its post. You get the ping role so announcements reach you. Refused, with a pointer, when the field is staff-entered.
  • leaveoptional group Withdraw while sign-ups are still open.
  • formatoptional group Mods: change the format: single elimination, double elimination, Swiss, or Swiss into either. Only while sign-ups are open; after /tournament start the bracket exists and its shape is fixed.
  • scheduleoptional group Mods: set or move the entry window and the tournament dates. Deliberately allowed at any time, so a tournament that overruns can have its end date pushed back. The site’s calendar follows.
  • addoptional group Mods: put someone into the field yourself. Give a user if they’re in this server, or an entrant name if they aren’t, for a field collected by hand or a game whose players aren’t all in the Discord.
  • dropoptional group Mods: take someone out, by user or by entrant name. Mid-tournament this is a forfeit: their live matches go to the opponent so the bracket keeps moving.
  • rosteroptional group Mods: attach Discord members to an entrant, meaning a team’s players. The entrant plays the matches; the roster is who the ping role reaches, so announcements hit the whole team and elimination strips the whole team. Editable even mid-tournament (a sub swapping in is the point), also from the site’s staff page.
  • startoptional group Mods: seed the field (random, or sign-up order) and generate every match.
  • resultoptional group Mods: report a match by its number. The bracket advances itself, posts the next pairings, and takes the ping role off whoever went out.
  • matchesoptional group The matches waiting to be played, with their numbers.
  • standingsoptional group The field and who is still in, or the Swiss table during Swiss rounds.
  • announceoptional group Mods: ping everyone still in the tournament with a message.
  • closeoptional group Mods: finish it and delete the ping role. The bracket stays on the site.
  • canceloptional group Mods: scrap it entirely.
Subcommands
  • /tournament create
  • /tournament join
  • /tournament leave
  • /tournament format
  • /tournament schedule
  • /tournament add
  • /tournament drop
  • /tournament roster
  • /tournament start
  • /tournament result
  • /tournament matches
  • /tournament standings
  • /tournament announce
  • /tournament close
  • /tournament cancel

Entrants can be a Discord user or just an entrant name, so a field collected by hand (a spreadsheet, or a game whose players aren’t all in the server) still gets a real bracket. Adding and removing are registration-only on both the bot and the site: once the bracket is drawn the match graph is fixed, so mid-tournament the answer is /tournament drop, which forfeits their live matches to the opponent. The bracket can be embedded on another site with a single script tag; the drop-in is linked from each tournament’s page. Results are reported by staff. The ping role tracks who is still alive, so you lose it when you are knocked out, so an announcement only reaches people with a match left. The bracket is public at /tournaments, and for the Ravens the staff panel can run the whole thing: create a tournament, move its dates, change the format, build the field and start it, as well as report results. The bot still does every Discord half (the ping role, the sign-up post, seeding, the pairings) within about half a minute of each change. One tournament runs at a time on free servers; premium servers can run several, and every command then gains a tournament picker for which one you mean, with one running, nothing changes.

/ioda

slash
Raven-chanAQWired

Time until you can get an IoDA from the Wheel of Doom.

/ioda [name]
Arguments
  • nameoptional string AQW name (defaults to your saved name).

/relay

slash
Raven-chanAQWired

Open the AQW chat-relay control panel. Bridges in-game chat to Discord.

🔒 Requires Manage Server

/relay

Bidirectional game↔Discord bridge via the AQW-Client relay service. Managing the in-game guild lives on the website, not here: one page per guild, however many relay accounts sit behind it, and each invite, kick, promote or demote goes out from whichever account is logged into the right AQW server. Anyone who can run /relay in a server can reach it.