One useful outcome
Choose the first workflow before creating channels
Ask the organiser which repeated job currently creates the most manual messages: checking spawn availability, handing over a busy-spawn queue, assembling an event roster, reviewing incoming transfers, or watching a visible hunting list.
Use that answer as the pilot. Dominando can coexist with lookup, moderation, voice, news, or other Tibia bots; it does not need to replace a server's existing stack. Disable duplicate feeds so members do not receive the same update twice.
Purpose before channel name
Use a channel map your administrators can explain
Channel names and emoji are your choice. Dominando stores the selected destination and its purpose, not a required hard-coded name. This low-noise map gives each shared feed one clear job:
#spawn-board
Live spawn board
One bot-owned message showing active and upcoming claims, queues, server-save progress, and an Open Dominando button.
#hunted-online
Hunted-online alerts
Offline-to-online notices for visible active hunting cases when the group deliberately enables that automation.
#incoming-transfers
Transfer-rule alerts
Each automatic transfer rule selects its own installed-server destination, so different review teams can receive different feeds.
spawn-directory
Searchable spawn Forum
One visual post per spawn with current availability, monster art, in-chat claiming, and the full schedule action.
#event-announcements
Bot-owned event feed
Creation and cancellation announcements include local timestamps, the signup command, and a direct event link. Participant details stay private.
Install, then link
Connect the correct world-bound group
A person allowed to add apps installs Dominando. A server manager then links the existing Dominando group using the invite code from Group Settings:
/dominando link group:ABCDEF
/dominando status
Installation permission and Dominando group authorization are separate. Discord's Manage Server permission proves who may configure the installation; group owners and administrators still control group-scoped product settings.
Installed-bot routes
Choose live-board and operations destinations on the web
Open Group Settings → Discord setup. For each connected Discord server, load the available channels and choose the live board, searchable spawn Forum, and event feed. Every destination must be visible to the Dominando bot and match the required channel type.
For hunted-online notices, open Operations settings, make the hunting list visible to the intended group audience, choose a Discord destination, then enable Hunted character online alerts. Valid changes auto-save.
For incoming transfers, open Transfer desk. Every automatic rule stores its own installed Discord server and channel. Use the review-first transfer-alert guide before enabling a destination. Do not assume that changing the live-board channel also moves transfer or hunted-online alerts.
The server validates the selected guild/channel pair before saving and again before delivery. If a channel is deleted or the bot loses access, repair that destination instead of silently falling back to another server.
Clear delivery boundaries
Keep shared updates useful and private details private
The live board and spawn Forum read the shared group claim ledger. Event creation and cancellation go to the selected event feed, while event signup and payment details remain private to commands and the web roster.
Hunted-online alerts and transfer rules remain independently controlled in Operations. A change to one route never silently redirects another workflow.
Prove the route
Trigger one real delivery before inviting everyone
Use a test group and a channel where every participant expects the message. Configure only the pilot route, trigger the matching action, and confirm that no copy appears in another server, group, or destination.
- Make one safe claim and confirm the live board edits one message.
- If hunted-online automation is enabled, test an eligible visible case and verify only its chosen channel.
- Use a controlled transfer rule and confirm its own saved destination.
- Create and cancel a test event only after Discord setup shows the event feed.
- Remove bot visibility from a temporary channel and confirm the product reports recovery work instead of leaking to another destination.
Record the revision, Discord server, group, expected channel, observed channel, and tester. Only then expand the workflow to more members or another Tibia world.
Tibia Discord setup questions
Must Dominando replace another bot?
No. Keep useful lookup, moderation, voice, or news bots and use Dominando for connected operations. Disable duplicate feeds.
Can all updates share one channel?
They can share destinations where supported, but separate purposes make noise, permissions, and failures easier to manage.
Which bot channels are eligible?
Text and announcement channels visible to the installed Dominando bot. The server revalidates the guild and channel.
Where do event announcements go?
To the linked installation's selected bot-owned event channel. Participant and payment details remain private.
Pilot one destination
Set up the channel your team will use this week
Dominando's core coordination workflows are free. Connect one group, route one real workflow, and keep direct setup help available during the first week.