What a useful Tibia event workflow should answer
Before the team logs in, every participant should be able to answer: what are we doing, when does it start, which character am I bringing, which roles are still missing, and where will changes appear?
Dominando keeps event details, linked characters, signup roles, the public event page, and Discord interactions on the same group data. Members do not have to rebuild the roster from reactions or copy character names between a spreadsheet and chat.
This workflow fits access quests, finals, world events, boss rotations, service teams, and recurring guild runs. Start with one event the organiser already runs manually; the tool should reduce work instead of inventing a new ceremony.
Before sign-ups
Define the run members are joining
Write a short event brief before creating the listing:
- Quest, boss, access mission, or service objective.
- Fixed start time, or a window when the team is choosing availability.
- Expected duration and registration deadline.
- Required access, supplies, level guidance, and meeting point.
- Whether the event is private to the group or useful on the public world calendar.
- Any fee or payment instruction, stated before signup.
Use public visibility only for an event that is genuinely open to the wider world. Private group events are not included in the public API or sitemap.
One-time setup
Connect the correct Tibia group to Discord
Open Dominando, sign in with Discord, link a character on the group's Tibia world, and create or join the group. A person allowed to add apps installs Dominando; a server manager then links the existing group:
/dominando link group:ABCDEF
/dominando status
Group owners and admins can create or cancel events. Members of a group linked to the current Discord server can list events, inspect rosters, join, and leave with their own eligible linked characters.
Simple or advanced
Create a fixed event in Discord or plan it on the web
For a fixed run, a group admin can create the event without leaving Discord. The start accepts a relative value such as +2h or an ISO-8601 timestamp; duration is in minutes:
/dominando event create title:Library Final start:+2h duration:90 description:Bring supplies public:true
Use the web event builder when the organiser needs a registration deadline, richer instructions, a public listing, or service pricing and payment notes. The web and Discord event views read the same record.
Use a clear title that will still make sense in a roster and public URL. Put access and supply requirements in the description rather than assuming every returning player knows them.
One shared source
Publish the event where members already coordinate
If the group wants shared event announcements, open Group Settings → Discord setup and confirm the linked server shows an event feed. A created event can then publish the start time with Discord's local and relative timestamps, host, group, world, duration, signup command, and event link.
The event feed is bot-owned and purpose-specific. Participant signups and payment details remain private; creation and cancellation messages go only to each linked server's configured event channel.
Public events also appear on the Tibia events calendar and their world page. A private group event remains out of the public listing.
Member self-service
Collect characters, vocation coverage, and attendance
Members list upcoming events and copy the short event slug:
/dominando event list
They join with an eligible linked character and choose a vocation or attendance role:
/dominando event join event:library-final character:Your Character role:EK
Command choices cover ED, EK, RP, MS, Monk, Bench, Late, Tentative, and Absence. The organiser checks one current roster instead of counting reactions:
/dominando event roster event:library-final
A participant who can no longer attend removes their own signup deliberately:
/dominando event leave event:library-final character:Your Character confirm:true
After the run
Run the event, handle changes, and review the process
Before the meeting time, compare the roster with the required roles and contact only members who chose a role needing confirmation. If the run must be cancelled, a group admin uses the event slug and an explicit confirmation:
/dominando event cancel event:library-final confirm:true
After the run, ask three practical questions: Did members understand the time? Did the roster show the missing roles early enough? Did announcements reach the intended channel without duplicate chat work?
Keep the parts that saved organiser time. For a regular hunting party, use the focused Tibia team hunt planner. For busy spawn coordination around any event, use the separate Tibia spawn claim and queue guide; an event signup is not a hunting-ground reservation.
Common setup problems
The event command is denied
Creating and cancelling requires the owner or admin role in the linked Dominando group. Discord server permissions do not replace group authorization.
A character cannot join
Confirm the character is linked, verified, on the event's Tibia world, and belongs to a member of the linked group.
No announcement appears
Open Discord setup and confirm the linked server still has its event channel and bot access. Delivery does not silently fall back to the live board.
Members see the wrong time
Use a future ISO-8601 start when precision matters. Discord announcements render local and relative timestamps for each reader.
Start with one real run
Give your next Tibia event one current roster
Dominando's core coordination workflows are free. Link one group, create the next event your team already runs, and let participants maintain their own signup.