The real question is predictability, not letters versus bots
Players keep asking which worlds use Discord booking, whether remote claims are respected, and why a reservation was invisible until somebody arrived at the hunting ground. Other players prefer letters because they show an immediate hand-off without asking everybody to join another service.
Both approaches can fail. A letter can be stale, hidden, changed, or readable only after somebody travels to the spawn. A remote calendar can encourage advance hoarding, unpublished role privilege, or rules that outsiders never saw. A fair community should compare those costs openly instead of presenting one tool as automatic authority.
This guide helps an organiser choose a voluntary process that members can understand. It does not tell a player to leave an occupied spawn, identify any world or guild as fair or unfair, or replace CipSoft's official Tibia Rules.
Compare the actual hand-off
Choose the system that solves your current problem
Write down how members discover availability, ask for the next turn, understand timezones, cancel, and correct a mistake today. Then compare the trade-offs without pretending either side is perfect.
| Question | Letter at the spawn | Shared web and Discord schedule |
|---|---|---|
| Who can see it? | Usually the player who travels to the hunting ground and finds the current letter. | Eligible members can check the schedule remotely before travelling. |
| How far ahead? | Usually describes the current occupant and next hand-off, but local customs differ. | Can support future slots, so a visible booking horizon and inventory limits are essential. |
| How is the queue shown? | Names may be edited on one in-game item, with no private expiry workflow. | Creation-order entries, requested durations, and private offers can be stored together. |
| What can go wrong? | The letter may be missing, stale, moved, or hard to inspect without visiting. | Hidden access, advance hoarding, unpublished privilege, and exclusion can make remote booking unfair. |
| Does it prove occupancy? | No. A letter is evidence of an intended hand-off, not proof of who is currently hunting. | No. Dominando cannot see physical occupancy or control the Tibia client. |
Publish before asking
Make every important rule visible
A remote system creates trust only when a newcomer can predict the same outcome as an administrator. Publish the covered world and spawns, eligibility route, maximum duration, booking horizon, per-character and per-account inventory, role differences, queue order, cancellation/no-show rule, evidence standard, and correction route.
Say explicitly that the schedule is a community convention, not an official Tibia rule. It cannot bind a player who never joined it, and it must not be used for threats, harassment, retaliation, false reports, or collecting unrelated personal data.
Use the copy-ready spawn reservation rules template to make limits and overrides visible before the first booking.
One record, two interfaces
Keep web and Discord on the same booking ledger
Do not run one spreadsheet for organisers, one bot list for members, and another live-board message. Dominando's web calendar, Discord commands, Activity, queue state, and live board read the same group-scoped claim records. A booking created through one supported interface is read from the same ledger by the others.
Members can inspect one complete Tibia server-save day from Discord:
/dominando claim schedule spawn:Issavi Sphinx date:2026-08-15
They can create or list claims without turning every action into a public message:
/dominando claim create spawn:Issavi Sphinx duration:120 start:+2h character:Your Character
/dominando claim list
The optional live board edits one existing message as shared state changes. The server-save local-time planner explains all 48 half-hour offsets, while the complete claim guide covers group linking, permissions, and the first schedule.
Busy-spawn hand-off
Use a queue instead of hidden priority or chat pressure
For a busy hunting ground, process queue entries in creation order and give the first eligible member the earliest half-hour slot that fits the requested duration. Dominando keeps one active account entry per group and spawn and sends a private Discord offer with a ten-minute expiry.
Acceptance is revalidated against the current schedule. Decline, expiry, or delivery failure advances the queue safely. Administrators may remove an ineligible or mistaken entry after authorization, but cannot manually reorder members.
The queue still does not prove physical occupancy or guarantee a hand-off inside Tibia. Read the fair spawn queue guide before using it as a community rule.
Migrate without disruption
Pilot one hunting ground for seven days
Choose one busy hunting ground and three to ten members, including a newcomer who did not write the policy. Publish the start and end of the test, keep the old hand-off visible during the transition, and avoid claiming that an installation means the community adopted the process.
- Can every participant find the current schedule before travelling?
- Can they explain the booking horizon, role limits, and queue order?
- Did any booking remain after the member no longer intended to hunt?
- Could a newcomer request a factual correction without private connections?
- Did the shared ledger reduce duplicate lists and repeated chat questions?
Expand only when members can predict outcomes from the written policy. Dominando treats a world as active only after a real claim, service-event, or operations workflow—not after installation alone.
Discord booking questions
Are Discord claims official?
No. A booking is a voluntary community record. CipSoft's published Tibia Rules remain authoritative.
Can Dominando detect the current hunter?
No. It cannot see the Tibia client or prove physical occupancy. Define a factual no-show and correction process.
Does every player have to join?
No service can bind an outsider. Publish the convention, make entry understandable, and keep disagreement non-coercive.
Must letters disappear immediately?
No. Pilot one spawn, state the transition clearly, and retire duplicate records only after the shared process works.
Why this comparison exists
Public discussions show long-running demand for a Discord claim bot, current interest in worlds with booking, and recurring concern about invisible or advance reservations. These sources inform the questions above; they do not prove that any named community follows one universal policy.
Start with one transparent hand-off
Test one shared schedule before changing the whole community
Dominando's core coordination workflows are free. Publish the rules, link one world-bound group, and review one real seven-day pilot.