Skip to main content

Incoming-transfer review · About 10 minutes

How to review incoming Tibia world transfers in Discord

Let Dominando check arrivals after server save, verify character facts before applying rules, and give administrators one accountable review queue with an optional focused Discord alert.

Start with review, not punishment: use the “Review every arrival” preset with no fee and no hunting action while the group proves its policy, access, data quality, and correction process.

Purpose before data

Set an accountable review policy

Write down why incoming transfers need review, who is accountable for decisions, which group roles may see the records, how long notes are kept, and how a person can request correction or removal. Keep notes factual and proportionate to the group’s legitimate operational need.

A public Tibia character or world fact may still be personal data when it is collected into an operational profile. Review the Privacy Policy and use the privacy contact for correction or removal requests.

Dominando coordinates a group’s own policy; it does not create or enforce rights inside Tibia. Do not present a group rule as an official CipSoft decision.

One destination world

Connect the correct world-bound group

Install Dominando in the intended Discord server, then link the existing group with its invite code. The group’s Tibia world is the destination used by the incoming-transfer workflow.

/dominando link group:ABCDEF

/dominando status

Confirm the linked group and its world before enabling operations. Follow the purpose-specific Discord setup guide if the installation or channel map is not ready.

Verified before rules

Enable Transfer desk for a restricted audience

Open Group Settings → Operations settings. Expand Access and visibility, enable Transfer desk, and choose the smallest audience that needs to review incoming transfers.

The automatic incoming-transfer scan checks the group world after every Tibia server save. Each discovered character is verified against TibiaData before any group rule runs. Transfer desk shows the last successful scan, the next attempt, and newly discovered records so an administrator can distinguish a quiet scan from a delayed one.

Verified input

Character and world facts are rechecked before rule evaluation.

Visible state

Last success, next attempt, and new-record counts stay visible.

No rule required

Verified arrivals still appear even before enforcement rules exist.

Safe first rule

Choose “Review every arrival” first

Create a transfer rule and select the Review every arrival preset. It sends every verified arrival to administrator review with No hunting action and no Tibia Coin fee. That gives the group a real operational feed without turning an untested rule into an automatic consequence.

Once the review path is reliable, a group can narrow a rule by source or excluded worlds, minimum and maximum level, vocation family, and priority. Every matched rule and resulting status is saved in the transfer audit trail.

Fees, payment windows, or stronger hunting actions are optional—not a setup requirement. Do not enable them without a documented lawful purpose, restricted access, a correction/removal route, fixed retention, and appropriate legal review.

Optional notification

Give the rule its own Discord destination

A verified arrival remains in Transfer desk even when Discord notification is off. Enable Notify Discord only if the review team needs a durable channel notice, then select an installed Discord server and a bot-visible text or announcement channel for that rule.

The server validates the selected guild/channel pair before saving and again before delivery. A deleted channel or lost permission requires repair; there is no silent fallback to another group, Discord server, or channel.

Keep the destination restricted to the intended reviewers. The live spawn board, spawn Forum, hunted-online alerts, transfer rules, and event feed use separate bot-owned configuration paths.

First real evidence

Verify one real arrival after server save

Wait for a real incoming transfer the administrators expect to review. Do not fabricate a person or production record to force a demonstration. After the next scan, compare the character, source and destination worlds, transfer time, matched rule, review status, and optional Discord destination.

  • Confirm the last successful scan advanced after server save.
  • Confirm the arrival was verified before the rule matched.
  • Confirm “Review every arrival” created review work but no fee or hunting action.
  • If notification is enabled, confirm one notice reached only the saved channel.
  • Record the reviewer, rule revision, decision, correction, and final status in the audit trail.

If there is no real arrival during the pilot, keep the rule in review-only mode and verify scan health. Absence of a new record is not evidence that delivery works.

Tibia transfer-alert questions

Is this a universal transfer-history database?

No. It is an operational feed for the linked group world after its scans, not a complete historical archive of every Tibia transfer.

When are arrivals checked?

After every Tibia server save. Transfer desk exposes scan health and the next attempt rather than promising an instant alert.

Do rules run before verification?

No. Dominando checks the discovered character against TibiaData first, then evaluates enabled rules.

Are fees or hunting actions required?

No. The recommended first preset requires human review with no fee and no hunting action.

Pilot one world

Review the next real arrival with your administrators

Dominando’s core coordination workflows are free. Connect one group, use the review-only preset, and keep direct setup help available for the first verified transfer.