A fair system starts before the first booking
People should not need private Discord lore to understand a public-world schedule. Publish the policy before asking anyone to follow it, make role differences visible, and give newcomers a correction route that does not depend on knowing an administrator.
CipSoft publishes the official Tibia Rules. Your community may coordinate voluntary hand-offs, but it should never present its own schedule as CipSoft policy or use Dominando to threaten, harass, or falsely report another player.
The template below is a starting point, not universal law. Replace every bracketed field with a choice your group can explain and actually follow.
Scope and authority
State what the schedule can—and cannot—do
Name the Dominando group, Tibia world, and hunting grounds covered. Say whether participation is for a private team, guild, or open community, and publish the date the policy takes effect.
Then state the boundary in plain language: Dominando records community bookings and queue state. It does not see who is physically occupying a hunting ground, control the Tibia client, grant a right to a spawn, or enforce a community decision inside the game.
Equal notice
Publish eligibility before enforcing it
Explain how somebody joins the group, where the current policy lives, and which linked character they should use. Dominando rechecks group membership and requires the character to match the group's current Tibia world.
Character verification matters for scheduling: an unverified character can reserve only within the current server-save day. A verified character can schedule future days, subject to the account's role limits. Never ask for a Tibia password, recovery key, or account credentials.
Predictable capacity
Choose limits people can see before they book
In Group Settings → Members → Daily limits per role, administrators can configure hours per character and per Discord account between server saves. Under Upcoming inventory per Discord account, they can limit total upcoming claims, reserved hours, and claims for the same spawn.
Write the selected values into the policy for every role. Dominando permits claims up to 24 hours, but your community can choose a lower maximum. Finished and cancelled claims release inventory; linked characters on the same Discord account cannot hold overlapping claims.
Use the Tibia server save time planner when members need the same 48 half-hour blocks translated into local time.
No hidden privilege
Disable overrides or disclose exactly how they work
Each role has a Can override lower roles setting. When enabled, a higher-priority role may place an overlapping claim; Dominando removes only the overlap from lower-priority claims, which can shorten, move the remaining start, split, or delete those records.
This behavior is powerful and easy to misunderstand. A transparent policy names every role that can override, the lower roles affected, the narrow reason for using it, and where a displaced member can ask for review. If the group cannot explain that difference fairly, disable the override.
Release, queue, review
Define what happens when plans change
Members can shorten, split, or cancel their own claim. Group owners and admins can cancel another member's claim and may shorten it, but cannot move or extend it. Ask people to release time as soon as they no longer intend to use it.
For a busy spawn, the Dominando queue processes entries in creation order for that group and hunting ground. It finds the earliest half-hour slot that fits the first member's requested duration, sends a private ten-minute Discord offer, and advances after a decline, expiry, or failed delivery. Administrators cannot manually reorder the queue.
A no-show decision still needs human facts because Dominando does not prove physical occupancy. Define the evidence, waiting period, administrator action, and correction route before the first disagreement—without harassment, retaliation, or pretending a community dispute is an official Tibia Rules decision.
Select, copy, and replace every bracket
Copy-ready Tibia spawn reservation policy
Paste this into a public Discord channel or rules page. Replace every bracketed field; remove any option your group does not use.
Small real-world test
Pilot one hunting ground for seven days
Choose one busy hunting ground and three to ten members, including somebody who did not help write the rules. Ask them to find the policy, make or cancel a claim, read their limits, and use the queue once.
Review confusion, cancellations, expiries, overrides, and administrator interventions. If a newcomer could not predict an outcome from the written policy, fix the policy or configuration before adding more spawns.
Then follow the complete spawn claim setup guide to connect the group, publish one quiet live board, and test the schedule across web and Discord.
Tibia spawn policy questions
Are Discord reservations official Tibia rules?
No. CipSoft publishes the official rules. A booking records community coordination and does not create an in-game right.
Must every role use identical limits?
No, but every difference should be public before booking. Configure and publish the exact limits for each role.
Can an admin reorder the queue?
No. Administrators may remove an ineligible or mistaken entry, but cannot drag members into a preferred order.
Does Dominando detect a no-show?
No. The policy must define how people confirm physical occupancy and request a factual correction.
Make the first outcome predictable
Publish the rules, then open one real schedule
Dominando's core coordination workflows are free. Start with one world-bound group, one written policy, and one seven-day pilot.