Inventory before install
List every bot and the job members actually use
Open Server Settings → Integrations and inspect installed apps, roles, channel access, webhooks, and active feeds. Ask members which commands or notifications they used in the last month. An installed app with no named owner and no current job is maintenance work, not proof of value.
Do not remove anything yet. Record the current route first so a useful lookup, moderation, voice, or news bot is not lost while the team evaluates a separate coordination workflow.
| Bot or tool | Repeating job | Source of truth | Destination | Admin owner | Keep, change, or remove |
|---|---|---|---|---|---|
| Existing lookup bot | Character and item commands | Current public game data | Command response | Named server admin | Keep if members use it |
| Existing notification bot | Level or death feed | One selected feed | #tibia-news | Named server admin | Disable any identical second feed |
| Dominando pilot | One claim, queue, event, or review workflow | Group-scoped Dominando record | Purpose-specific destination | Group owner or admin | Keep only after a real pilot |
Copy these six headings into a private administrator channel or document. Do not post bot tokens, private member records, or credentials in the matrix.
One accountable route
Separate complementary alerts from duplicates
Complementary alerts can coexist. A boosted-creature notice and a team-hunt roster answer different questions. A character lookup and a spawn schedule also serve different moments.
Duplicates repeat the same decision. Two bots publishing the same level or death feed into one channel create noise. Two editable boards claiming to show one visible spawn state create ambiguity about which one members should trust.
For every repeating signal choose one source, one owner, and one destination. If two products overlap, keep the route that is understood, permissioned, recoverable, and used; disable only the duplicate feed, not automatically the whole app.
Keep together
Lookup commands + a separate event roster; news + a separately owned spawn board.
Choose one
Two identical death feeds; two level feeds; two messages claiming to be the current schedule.
Keep private
Command replies, queue offers, attendance, payment details, and administrator evidence that do not need a public feed.
Smallest necessary access
Review each bot's permissions separately
Do not grant Administrator to avoid understanding an app's needs. Start in a test server, read the authorization prompt, inspect the bot role, and use channel overrides so each app can see only its intended destinations.
Some configured feeds need Manage Webhooks; channel-creation features may need Manage Channels. Those are separate capabilities. Grant each only when the chosen workflow explains it, and remember that permission does not itself authorize an app to create or reroute community channels.
Dominando's manual install keeps the smaller permission set. Its optional automatic-setup path requests Manage Channels, but channel provisioning still requires an explicit owner/admin setup action. Review the current Dominando commands and setup actions before authorizing it.
Failure and exit drill
Know what happens before a channel disappears
In a temporary test destination, remove one permission or hide the channel from the bot. Trigger only the expected safe test. The route should fail visibly and must not silently fall back to another server, group, or channel.
- Record the owner who receives or checks the failure.
- Restore access and prove delivery returns to the same saved destination.
- Document the product's disable, data correction, deletion, and export or exit path.
- Disable a repeating feed before removing its bot so a replacement does not overlap during migration.
Dominando does not silently fall back to a different purpose-specific destination. If a saved channel becomes unavailable, repair that exact route. Review the purpose-specific setup guide and privacy notice before moving real group operations.
One-workflow pilot
Add Dominando only for a separate current problem
Keep an existing lookup, moderation, voice, or news bot when it is useful. Choose Dominando only when a guild, team, or world community needs one shared operational record across web and Discord: a spawn claim and queue, event roster, incoming-transfer review, or governed hunting case.
Dominando's Discord bot does not automate loot splitting, boss cooldown timers, or nickname sync. Its separate browser-only Party Hunt Analyser calculator suggests manual transfers but does not store a hunt or pay players. Keep another focused tool for persistent or automated versions of those jobs rather than forcing a replacement story.
Run a seven-day pilot with one group and one workflow. Count a completed claim, event, or operations review; record duplicate messages, permission surprises, failed deliveries, and manual cleanup. Installation is not adoption. Recheck the existing 30-day activity signal before expanding to another workflow or Tibia world.
Current configuration sources
Reviewed 14 August 2026. These sources illustrate configurable feeds and permissions; they are category evidence, not a ranking, endorsement, completeness claim, or claim that a named product causes duplicate alerts.
- NabBot getting started recommends a dedicated level/death notification channel and explains selecting its slash commands among installed apps.
- NabBot permissions documents channel visibility and Manage Webhooks for configured announcement feeds.
- NabBot administration documents separately configurable event and level/death channels.
- LemonBot publicly describes channel setup, roles, and real-time notifications for its monitoring category.
Keep the useful stack · Add one missing workflow
Make every repeating message accountable
If connected group operations are the missing job, test Dominando beside the tools your community already trusts and expand only after real use.