How to run a fair Tibia spawn claim system in Discord

A bot cannot make an unclear policy fair. Write down the smallest workable rule set before configuration:

• Which linked characters and group roles may claim?
• What are the maximum daily hours, upcoming claims, reserved hours, and claims for one spawn?
• How far ahead can members book, and does ownership verification affect that horizon?
• Can a higher-priority role pre-empt a lower-priority booking?
• How should cancellations, no-shows, disagreements, and rule changes be handled?

Keep these rules visible to members and review them after the pilot. Group owners and admins can configure role-aware limits in Dominando, but the written explanation is what gives those settings context.

First, open Dominando, sign in with Discord, link a Tibia character, and create or join the group for the correct Tibia world. Copy the group invite code from Group Settings.

Next, a person allowed to add apps installs Dominando. A server manager with Discord’s Manage Server permission then links the existing group and confirms the result:

/dominando link group:ABCDEF /dominando status

Installation and group linking are separate on purpose. The link proves which Dominando group belongs in this Discord server; it does not expose unrelated groups. If the server coordinates several teams, link each one and choose the normal default:

/dominando default group:ABCDEF

See the complete installation walkthrough when you need character verification or multi-group setup.

Create or choose a Discord text channel the installed bot can view and send messages in. A server manager configures the group’s live board:

/dominando board group:ABCDEF channel:#spawn-claims

Dominando publishes one message and edits it as claims, queues, hunt time, and AFK state change. Members can read the shared state without every reservation creating another channel message.

The live board is optional. The spawn Forum, event feed, hunted-online alerts, and transfer-rule alerts are separate bot-owned delivery paths and may use different destinations. Verify each enabled route with one real test and never assume a fallback channel.

Members can ask Dominando for suitable hunting grounds using the level and vocation of a linked character. Add a query when you already have a place in mind:

/dominando spawn find query:sphinx character:Your Character

Before booking, inspect one complete Tibia server-save day. Use the free Tibia server save local-time planner when you need to convert all 48 half-hour offsets for members in different timezones. The command response contains the same bounded 48-block timeline plus exact existing bookings and open gaps:

/dominando claim schedule spawn:Issavi Sphinx

Add date:YYYY-MM-DD when you need another server-save date. Then create a booking now, after a relative delay, or at an exact ISO-8601 time:

/dominando claim create spawn:Issavi Sphinx duration:120 start:+2h character:Your Character

Dominando applies the same overlaps, eligibility, role limits, account inventory, queue holds, and group-world boundaries used by the web calendar. List bookings and keep the short reference if a cancellation is needed:

/dominando claim list /dominando claim cancel claim:REFERENCE confirm:true

The full syntax and optional fields are in the Discord command reference.

Open the booking details from the web schedule or Discord Activity and join the queue for that hunting ground. Queue order and offer state are stored with the same group and world as the claim.

When an eligible slot opens, Dominando sends the next member a private Discord offer. The offer names the hunting ground, group, world, start time, and expiry. The member has ten minutes to accept or decline; expiry or decline safely advances the queue.

A queue offer is not a public announcement and does not grant a place inside the game. It is a private coordination step under the rules your community agreed in step one.

For FIFO policy, requested durations, offer holds, delivery failure, admin boundaries, and a focused pilot, follow the dedicated fair spawn queue guide.

Start with three to ten members and the few spawns that create the most scheduling friction. Ask each member to complete one real task from their preferred surface: read availability, create a claim, change or cancel it, or join a queue.

At the end of the week, review:

• Did members understand local time and the server-save-day timeline?
• Which written rule or permission was unclear?
• Did the live board reduce repeated questions or channel noise?
• Did any notification reach the wrong channel or audience?
• Could members remove the old spreadsheet or booking message?

Adjust the rules and settings from evidence, then invite the next team. A small retained workflow is more useful than a large installation nobody uses.