Purpose before monitoring
Write a factual, correctable case policy
Before adding anybody, record the group’s legitimate coordination purpose, required evidence, accountable reviewer, audience, review date, retention limit, and a route for correction or removal. A public Tibia character name can still be personal data when it is collected into an operational profile.
No threats, harassment, retaliation, sensitive real-world details, or instructions to interfere with somebody’s play. Reasons and evidence should be factual, proportionate, and limited to the group purpose. Review the Privacy Policy and keep the privacy contact available to people who cannot reach a group administrator.
CipSoft publishes the official Tibia Rules. A Dominando case records one community’s own operations; it cannot bind outsiders, certify wrongdoing, or replace an official game decision.
Smallest necessary audience
Connect the correct group and restrict visibility
Install Dominando in the intended Discord server and link the world-bound group. In Group Settings → Operations settings → Access and visibility, enable Hunting list for administrators only unless a broader member audience has a documented need.
Group owners and administrators—not ordinary members—create and update cases. Other members may only read records when the saved Hunting list audience permits it. Discord server permissions do not replace the group role check.
/dominando link group:ABCDEF
/dominando status
Use the purpose-specific Discord setup guide before adding a shared alert destination.
Verified identity
Create one case with evidence and a review state
An administrator enters a character, reason, optional evidence, and one priority: Low, Normal, High, or Critical. Dominando confirms that the character exists on Tibia.com and belongs to the group’s current world before saving its canonical name, level, vocation, and verified state.
/dominando hunted add character:Target reason:Reason priority:normal
Only one active case for that character exists inside a group. The case can move between Active, Pardoned, Resolved, or Cancelled; status and priority changes create audit events. Read the exact syntax in the hunted command reference.
Dominando rechecks active characters every 24 hours. Alerts and optional restrictions require an active, currently verified case; a missing character or world mismatch stops active enforcement while verification is retried or reviewed.
Deliberate destination
Enable offline-to-online alerts separately
In Automation and enforcement, enable hunted-character online alerts. Then choose an installed Discord server and bot-visible channel under Discord alert delivery. Saving the destination does not silently enable another automation.
The first observation establishes a baseline and does not alert. After that baseline, only an offline-to-online transition for an active, currently verified case can queue a notice. This is periodic public-world observation—not real-time game-client tracking or guaranteed instant delivery.
The notification keeps the saved group, world, installed server, channel, reason, and priority. If the automation is disabled or its destination disappears, Dominando does not silently fall back to another channel.
Hunting-list visibility, online alerts, and claim restrictions are separate controls. Claim restrictions are a separate, optional administrator setting; they affect only the group’s Dominando claims and queues, never the Tibia client or players outside the service.
Safe first evidence
Test one complete transition without targeting a stranger
Use your own character or a participant who has agreed to the test. Create the case with a plainly labeled test reason, keep claim restrictions off, and wait for Dominando to record the initial presence without sending a notice.
- Confirm the case shows the canonical character and the correct group world.
- Confirm the first observation creates no Discord message.
- After a recorded offline state, log the consenting character in and wait for the next observation.
- Confirm one notice reaches only the saved restricted channel.
- Disable alerts and close the test case when the route is proven.
If no notice arrives, inspect the verification state, saved automation, installed server, selected channel, bot visibility, and recorded presence transition. Do not generate repeated public cases to test delivery.
Accountable closure
Review disputes, corrections, and stale cases
Review active cases on a fixed schedule. Check whether the reason and evidence remain current, whether access is still necessary, whether the character remains on the group world, and whether the record should be pardoned, resolved, cancelled, or deleted under the applicable retention decision.
Give the affected person a route to see and challenge the facts. Preserve the request and outcome, correct inaccurate data, and pause disputed restrictions while a correction is reviewed when the risk justifies it. Use Dominando’s privacy contact when a direct group route is unavailable.
For transfer-originated cases, keep transfer review and hunted-list status distinct. The incoming-transfer guide starts with review only and no hunting action.
Tibia hunted-list alert questions
Does adding a case alert immediately?
No. The first observation establishes the presence baseline. Only a later offline-to-online transition may create a notice.
Can an ordinary Discord member add a case?
No. Dominando requires a persisted group owner or administrator role for case creation and changes.
Does a case enforce anything in Tibia?
No. It is group-scoped service state. Optional claim restrictions affect only Dominando’s own claim and queue workflows.
Does delivery fail over to another channel?
No. Repair the saved destination or permissions; Dominando does not reroute a sensitive alert somewhere else.
Pilot one consenting character
Prove the restricted alert path before adding real cases
Connect one group, keep the first audience small, verify baseline and transition behavior, then document review and correction ownership.