Parties & raid composition

How it works

The party planner is a drag-and-drop board for building an event's group composition. The members are listed on the left; you drag them into parties, or click an empty slot and pick who sits in it. It lives on the Party planner tab of the game's Parties page and on each event's own Parties tab, and it is free on every server, autofill and the posted picture included. The Parties module has to be on for the game, and building needs someone who can run that game's events: a server admin, the Events permission, or the game's Admin or Events permission.

The list is as wide as a party, and its corner of the bar above it holds its controls: the button that folds it away (the board's five columns then share the room) or brings it back, how many are still to seat out of everyone who could be, and the sort, which a click moves on from name to the Icon field to each Tag. Every change saves by itself. On the game's Party planner, Undo in the bar takes back the last bulk change, such as an autofill, its tip naming which.

How a member shows is set once for the game, on the Parties page's Settings: a Name (a text field such as the in-game name, shown instead of the Discord name), an Icon (a choice field such as the class, its emoji shown where the avatar goes), and up to two Tags on the right of the row, a choice as its emoji and a number short with its name, such as "IL 3,012". When the Icon's choices have colours, each member's row wears a soft wash of theirs, so the classes in a party read at a glance. The board, the statics and the posted picture all show members the same way. With an Icon set, a member with no value for it shows a ? there. Up to two Categories are choice fields a slot can ask for without showing on members, such as a role that the class already says: clicking an empty slot's icon then steps through their values, and sorting the list by one groups it under them.

Members cannot edit a composition, but they can view it on the event's Parties tab: the board alone, as you last set it, without the member list or any of the tools. The posted picture's Open on website takes them straight there, so everyone knows their group going in.

An event with signup options of its own gets a Build from switch, choosing whether its parties are described in the game's fields (what people are on the roster) or in this event's own options (what they signed up as tonight, on whichever character they brought). It is one or the other, never both, because the two answers compete: switching clears what the slots were asking for, since a slot that wanted a Healer from one list means nothing against the other.

Slots

A party is a fixed number of slots, not a list that grows as you drop people into it. Every slot is there from the moment the party is, so a half-built party reads as one list with holes in it rather than as rows and gaps. How many slots a new party gets is Party size on the game's Settings tab, or Party size in the toolbar when an event builds from its own signup options; either way, parties already on the board keep the size they have. What a new party and a new force are called is set there too (Party name and Force name, "Party 1" and "Force 1" to start with); changing one renames the parties or forces that still carry the old name.

Clicking an empty slot lists who is left to place, as wide as the slot: the people who fit that slot first and everyone else after them (on an event, the tentative and the bench come last). Type to narrow the list and press Enter to take the first one.

An empty slot is Any until you tell it otherwise. Its icon, where a member's avatar would be, is what it asks for: click the icon to step through your first field's values (a Healer, a Tank, a Bard, and back to Any), or the small arrow on its corner to pick from every field's. A slot that asks for something shows that option's emoji and says so in its colour, which is what turns "I have three and the fourth needs a healer" into something the board can hold instead of something you keep in your head.

What a slot asks for is a requirement, not a lock. You can still drop anyone into it, the slot simply says what the party is short of. Autofill reads those requirements and seats people against them, and Copy its seats in a party's ⋯ menu clones its shape, its size and what each slot asks for, with nobody in it.

Forces & leads

The board is a grid five columns wide. Every party sits in a cell and stays where you put it: drag it by its header to an empty cell and it moves there, drop it on another party and the two swap. Nothing else on the board moves. A new party goes into a cell too: hover an empty cell for + Party, or drop a member on an empty cell to start a party with them in it. The board grows a row at a time as you use it, up to twenty rows.

Parties that run together are a force: your two siege squads, your alliance's left flank. A force is a block of cells, outlined in its colour, and a party is in the force of the cell it sits in. Move a party into a force's cell and it joins, move it out and it leaves. To start one, hover an empty cell for New force (a party in no force has it in its ⋯ menu). Hover a force and a dot shows on each of its edges: drag a dot outward and the cells it passes join the force, drag it back and they leave. The edge follows your pointer, and a dashed ghost shows what letting go now would give: a cell joins once the edge is past its middle. Dragging across another force's cells takes them over, parties and all. A force cut in two by a drag becomes two forces, and a force can hold cells with no party in them yet.

Each force has a label on its outline, over its top-left cell, as on the posted picture: the force's colour (click the dot to change it), its name (click it to rename) and its lead. The × under the pointer removes the force and leaves its parties where they are. The bar and the member list stay where they are while the board scrolls.

Anyone seated can be made a lead. Click the crown on their avatar (it shows when you point at the row): once makes them the party's lead, again (inside a force) promotes them to the force's lead, and again clears it. A party lead's crown and the ring round their icon are grey, a force lead's are in their force's own colour, so the two stay told apart at a glance. Both appear on the posted picture and are named in the post itself, and a re-post never pings the same lead twice.

A lead is a label, not a permission. It grants nothing, gates nothing, and no attendance, points, loot or signup rule reads it. The same goes for a force: it is a way of saying which parties run together, and nothing more.

Templates & autofill

The game's Party planner works on templates: your standard raid setup, your siege layout. Pick one in the bar to build on it; New template is the picker's first row, and the pencil and the bin on a row rename or delete it. A template keeps its parties, their forces, what each slot asks for and who sits where.

On an event's Parties tab built from the game's fields, Load layout... lists the game's templates and replaces the event's board with the one you pick. The people come along only where they fit tonight: anybody not signed up, and anybody whose signup differs from their profile, stays in the list rather than being seated. Its first row, Save this board as a layout, keeps the event's board as a new template in the game's list.

A repeating event remembers its board: the next event its template makes opens on the board the last one was saved with, whoever signed up again sitting where they sat, so a weekly raid starts from the composition you settled on. Last board from this template in the layout list puts it back if you have rearranged it.

Autofill takes everyone still in the list and seats them into the empty slots, matching each one against what that slot asks for, so you start from a sensible draft instead of an empty board and just tweak from there. A slot nobody matches is left open and autofill tells you how many, rather than filling it with the nearest warm body and letting you find out on the night.

It fills the gaps in your layout and never takes it over: nobody already seated is moved, no party is invented, and what each slot asks for is left alone. On an event it seats the people who said Attending or Late; tentative and benched signups stay in the list for you to place by hand.

A game with more than one roster has the roster switch in the top bar on the planner. Pick a roster and the member list, the seat picker and autofill only offer that roster's members, so you can build one guild's composition. The template itself stays the game's: switching never changes it, and anybody already seated from another roster stays where they are, dimmed.

Posting

When the composition is ready, post it to the event's channel as an image with Post to Discord in the event's Image menu, which also copies or downloads it. It is free on every server: a clean rendered layout everyone can read at a glance in Discord, the board's own grid with every party in its cell, members in their class colours, forces outlined in their colours with their name (and lead) on the outline, and every lead wearing a crown. Names in any script, Japanese or Korean as much as English, draw as they are. Re-post to refresh it if the roster shifts.

The post names the leads above the picture, party leads on one line and force leads on another, and mentions each of them so they know they are running something. A re-post never pings anyone it has already pinged, so refreshing the board is quiet.

Under the picture, Find me tells whoever clicks it, and only them, where they sit: their party and force, their seat, their lead and who is with them. It reads the board as it is now, so it stays right after a change, and says so when the board has changed since it was posted. Open on website goes to the event.

From a game's own Parties page there is no event channel to post to, so the board is taken away as a picture instead: its Image menu's Copy image puts it on your clipboard, and Download saves it, splitting a board too tall for one picture into several.

Statics

A static is a group of members who play together and stay together: your Tuesday dungeon four, your siege core. Turn statics on for a game on the Parties page's Settings, and choose there Who can create one (anyone, or officers only), how many a member may be In at most and Lead at most, the Largest static, and which Join settings a leader may pick. With statics on, every member of the game can open the Parties page for its Statics tab; the planner and Settings stay with the officers.

The Statics tab lays the statics out as a board, each drawn like a party: its members, its leader's crown and its open places. Yours come first, then the ones with room, then the full ones. Everything happens on the box: join or ask to join in its first open place; a request waits in the static's next open place, where the leader accepts or declines it; the leader invites by clicking an open place, hands the crown over by clicking someone's crown, and edits or disbands it from its ⋯ menu, where a member can also leave it. A static has a name, a colour, an optional description and its number of places.

A leader picks who can join: Open lets anyone in the game join while it has room, On request means people ask and the leader decides, and Invite only means the leader invites. When someone asks, the leader gets a DM from Qutie with who asked, their details and Accept and Decline; the request also waits on the Statics tab. An invited member gets a DM from Qutie with Accept and Decline, and can answer on the website too; if their DMs are closed, the invite waits for them on the Statics tab.

Pick a Statics panel channel in Settings and Qutie keeps one message there listing every static with its leader and how full it is. Members join one from its dropdown, or make their own with its Create a static button, without opening the website.

On the party planner, each static with someone in the list is a row at the top of it, under Statics. Hold it over a party to see which slots its members would take, then drop it there; anyone who does not fit stays in the list. Place statics in the toolbar does it for several at once, into empty parties, the empty parties of one force, or new parties, and shows where each would go before anything moves. With Match the seats on, a static only goes into a party whose slots it can fill.

A party filled from a static remembers it: a small square in its header says how many of the static are in that party, with a warning while some are missing (hover it for who and where). Click it to light the static's members up across the board.

A static is a fact about who plays with whom, and nothing more. Being in one grants no permissions, signs nobody up for anything, and changes no attendance or points.