Use a claim for a known time; use a queue for the next fitting time
A claim reserves an exact start and duration. A queue entry asks Dominando for the earliest future half-hour slot that fits the requested duration after existing bookings.
Queue order is durable and scoped to one Dominando group, Tibia world, and hunting ground. Only one offer is active for that queue at a time. The offered interval is held during the response window so another booking cannot take it while the member decides.
This guide focuses on the hand-off after a hunting ground is busy. For installation, schedule rules, live boards, and exact-time bookings, start with the complete Tibia spawn claim guide.
Before the first entry
Publish a queue policy members can predict
Dominando processes entries in creation order for each group and hunting ground. The tool makes that order consistent; your community still needs to explain the surrounding policy:
- Which hunting grounds use a queue rather than direct claims?
- Who may join, and which linked character should they use?
- Which durations are reasonable for the group?
- What should a member do when they no longer want the slot?
- When may an owner or admin remove an ineligible or mistaken entry?
Do not promise manual priority that the product does not implement. Administrators can remove an entry after the server rechecks their current group role, but they cannot drag members into a preferred order.
Shared identity and world
Connect the correct group before opening the queue
Each member signs in with Discord, links a Tibia character, and joins the Dominando group for that character's world. A person allowed to add apps installs Dominando, and a server manager links the existing group:
/dominando link group:ABCDEF
/dominando status
The service rechecks membership, linked-character ownership, the group's current Tibia world, and active hunting restrictions when somebody joins and again when they accept. A Discord server role alone does not bypass group authorization.
One clear request
Choose the character and duration, then join once
Open Spawns in the web app or Discord Activity, choose the hunting ground, then open View queue or any booking's details. The same panel shows current positions, requested durations, and active-offer state.
Select an eligible linked character and the time you want. Requests support 0.5 to 24 hours in half-hour increments; the interface gives common choices from 30 minutes through 24 hours.
One Discord account may hold one active entry for the same group and hunting ground. If the duration changes, leave the existing entry first and join again. This prevents one person from filling several positions with linked characters.
Visible shared state
Read the order without searching Discord history
The queue lists each position, linked character, requested duration, and whether an offer has been sent. Members can leave their own entry. Owners and admins can remove another member only through the group-scoped server action.
Dominando looks for the earliest fitting interval, rounded to a half hour, after existing bookings. A longer request may therefore start later than a shorter one would, but the system still processes the first queued member before considering the next.
The optional live board summarises queue activity in one edited message. Detailed membership and removal actions stay inside the authenticated web or Activity view instead of becoming channel spam.
Private hand-off
Accept or decline the ten-minute Discord offer
The private message identifies the hunting ground, requested duration, start time, Dominando group, Tibia world, and originating Discord server when known. It uses the member's saved English, Polish, Spanish, or Portuguese response language.
Accept
Dominando rechecks eligibility, limits, restrictions, and conflicts, then creates the claim and closes the queue entry.
Decline
The entry closes without a claim and the next queued member can be considered.
If ten minutes pass, the offer expires and an Activity inbox notice records the result. If Discord cannot deliver the DM, Dominando marks delivery failed, records a missed-offer inbox item, and advances rather than silently blocking the queue.
The service also reconciles queues on a durable scheduled cycle. Treat the message as a time-bounded offer, not as a promise of an exact notification second.
Seven-day test
Pilot one busy hunting ground before expanding
Choose one ground with repeated waitlist questions and three to ten real members. Ask each participant to join once, check their position, and deliberately accept, decline, or leave an offer during the week.
Review four signals with the organiser:
- How many members received an offer and how many accepted?
- Were expiries caused by unclear expectations or unavailable DMs?
- Did an admin need to remove entries, and was the reason documented?
- Did the queue reduce chat pings and manual hand-offs?
Keep the policy that members understood, fix the part that caused missed hand-offs, and only then add more hunting grounds. A retained queue on one real spawn is stronger adoption than a large unused install.
Spawn queue questions
Can one member join more than once?
Not for the same group and hunting ground. Leave the active entry before requesting another duration.
What if the DM cannot be delivered?
The delivery is marked failed, a missed-offer Activity inbox item is recorded, and the queue advances.
Can an admin reorder members?
No manual reorder is exposed. Administrators may remove an ineligible or mistaken entry after current-role authorization.
Does acceptance guarantee the spawn in Tibia?
No. It creates a Dominando booking under community rules; it does not create or enforce in-game rights.
Start with one real queue
Stop making members watch chat for a free slot
Dominando's core coordination workflows are free. Link one group, choose one busy hunting ground, and test the complete request-to-offer hand-off.