TR@X Guide Back to TRAX

Activities

An activity is a reusable template for a thing your guild does repeatedly — the roster it needs, plus optional automation that fills it for you.

Find them at Guild → Manage → Activities. An activity belongs to one guild and one game, and carries a list of character slots.

Activity, event, LFG. The activity says what you run and who it needs. An event is one dated instance of it. LFG is the list of people currently available for it. Automation joins the three together.

Default activities

You do not have to invent these from scratch. Every game ships with a set of default templates, and the Default Activities dialog opens automatically when you create a guild and when you add a game. You can reopen it any time from Manage → Integrations.

It is a sync view, not an add-only list: activities already in your guild come pre-ticked and tagged Added. Tick one to add it; untick an added one to remove it (you are asked to confirm). The footer button tells you what will happen — Add 3, Remove 1, or both.

Creating one by hand

  1. Create Activity. Give it a Name (e.g., Guild Raid), pick the Game, and optionally describe it.

  2. On the right, build the Character Slots — this is the roster. See below.

  3. Optionally configure auto-match underneath the details.

  4. Create.

Character slots

A slot is one seat in the roster. Press Add Slot and fill in:

FieldMeaning
Slot Name Required — e.g., Tank, Healer, DPS.
Required Tags A character must carry all of these to be eligible. This is the core matching rule — see Characters.
Capacity How many people the slot takes. Leave it unset and it counts as one seat.
Renown Reward Points granted for completing the event in this slot. See Renown. Disabled if you lack renown rights.
Level Range / Gear Score Range Optional minimum and maximum. Characters outside the range cannot take the slot.

Slots are optional on an activity but required on an event. Defining them on the activity means you never have to retype them — picking the activity as a template when creating an event copies the whole roster across.

Auto-match

Auto-match reads who has declared LFG for this activity and seats them. It is two nested switches plus a number:

  1. Auto Match — off by default. On, TRAX matches interested characters into slots.

  2. Auto Create Events — only appears once Auto Match is on. Off: TRAX only fills unfilled slots in events you created yourself, and partial fills are fine. On: TRAX also invents the events, reading candidate times out of your members' declared availability.

  3. Duration (minutes) — only when Auto Create Events is on. How long a generated event should last. Minimum 15, in 15-minute steps.

Auto-created events are all-or-nothing. With Auto Create Events on, an event is only created if every slot fills to capacity. A raid needing 10 people will never half-appear. If nothing is being generated, that is almost always why — either loosen the slots or fall back to creating events yourself with Auto Create Events off.

How seats are assigned

Slots are filled greedily, in the order you defined them: TRAX walks the slot list and gives each one the first eligible character it has not already seated. A character is only ever seated once, so a flexible player cannot make several slots look full at the same time.

Put your most restrictive slots first. If your flexible Healer/DPS player gets consumed by an early DPS slot, the Healer slot behind it can go unfilled.

Timing

Availability is matched at hour granularity, in UTC — minutes are ignored. A character declared free at 20:00 UTC matches an occurrence anywhere in that hour.

Matched characters receive an event invitation: a Discord DM each, plus a summary posted to the guild channel. See Discord.

The activity page

Clicking an activity opens its own page with:

You cannot declare LFG from the activities table. Activities are templates and automation; declaring availability happens in the LFG hub, reached from the cyan pill in the sidebar.

Schedules

The Schedules switch next to Activities lists your recurring event patterns — the repeating rules that generate events on a rolling basis. They are created from the event dialog; see Events.