The smallest useful team-hunt plan
A dependable plan answers five questions before anyone travels: where are we hunting, when do we start, which character is coming, which vocation is missing, and what happens if somebody is late?
Dominando keeps that event and roster available on the web and through Discord commands. Use the public Shared Experience checker to validate the entered party's level boundary and vocation bonus. The event does not enforce that result, choose the best hunting ground, or automatically match random players. Check the final party inside Tibia.
Start with one fixed-time hunt your team already coordinates in chat. If it removes repeated pings, use the same lightweight routine for the next session.
Before the event
Agree the hunt and one fixed start
Write down the hunting ground, world, fixed start, expected duration, level guidance, meeting point, supplies, and a fallback if the spawn is occupied. Put local conventions in the description instead of assuming every returning player knows them.
If schedules are still uncertain, agree the time in chat first and create the event after the team settles on a start. Dominando can record an availability window, but it does not currently collect each participant's time vote.
One-time setup
Connect the team to the correct Discord server
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
The Discord install and group link are separate. Group owners and admins create events; group members join with their own eligible linked characters.
One hunt, one record
Create a fixed team-hunt event
A group admin can create a fixed run directly in Discord. The start accepts a relative value such as +2h or an ISO-8601 timestamp, and duration is in minutes:
/dominando event create title:Buried Cathedral Team Hunt start:+2h duration:120 description:Meet at the entrance public:false
Use the web event builder for a registration deadline, richer instructions, or public visibility. Keep a regular guild hunt private; choose public only when players outside the group are genuinely invited.
Creating an event can publish through the linked server's bot-owned event feed. Event creation and cancellation are shared; participant and payment details remain private. The event feed stays separate from the live board, hunted-online alerts, and transfer-rule destinations.
Member self-service
Fill vocation roles without counting reactions
Members find the event slug, then join with a linked character and the role they intend to fill:
/dominando event list
/dominando event join event:buried-cathedral-team-hunt character:Your Character role:EK
Available choices are ED, EK, RP, MS, Monk, Bench, Late, Tentative, and Absence. These labels communicate the plan; they do not certify level range, quest access, or shared-experience eligibility.
If plans change, a participant deliberately removes their signup:
/dominando event leave event:buried-cathedral-team-hunt character:Your Character confirm:true
Before travelling
Confirm the actual party inside Tibia
The organiser reads one current roster instead of reconstructing it from messages:
/dominando event roster event:buried-cathedral-team-hunt
Check the linked character names, missing vocation, tentative or late status, level range, access, and Shared Experience eligibility. Enter the party's levels and vocations in the public Shared Experience checker, then confirm the live party inside Tibia. Event signup does not automatically validate or enforce the calculator result.
Use Tibia's Team Finder as an additional in-client notice when the team still has an open slot; Dominando does not automatically find random teammates.
For a world or guild Discord lf-team channel, use the free team-hunt post generator to publish the open roles and one start time that Discord renders for each reader's timezone.
Separate coordination
Coordinate the hunting ground after the team is confirmed
An event signup does not reserve a spawn. If the hunting ground is shared through your community's schedule, create the claim only after the party is ready. For a busy spawn, use the fair queue workflow instead of negotiating priority in chat.
Dominando records the group's coordination; it does not grant or enforce hunting-ground rights inside Tibia. Publish the rules first and keep a fallback hunting ground in the event description.
Team hunt planner FAQ
Can Dominando check Shared Experience levels?
Yes. The public checker validates the entered party's level boundary and vocation bonus. Event signup does not enforce it; confirm the live party inside Tibia.
Does it replace Tibia's Team Finder?
No. Team Finder provides an in-client notice; Dominando provides a persistent schedule and roster for a guild, regular team, or public organiser.
Does joining reserve the spawn?
No. Event signup and hunting-ground claims are separate workflows. Confirm the team, then create a claim or join the queue when needed.
Can it find random players automatically?
No. It helps an existing organiser publish a plan and maintain the roster. It does not provide automatic matchmaking.
Start with one real hunt
Make the next roster easier to trust
Dominando's core coordination workflows are free. Plan one fixed team hunt, let members maintain their own signup, and keep the spawn decision separate.