Skip to content
Lemon Bot
Dashboard

Help & FAQ

Short answers to the things that most often get in the way of running Lemon Bot.

Members get an error when they press a role button

Discord only lets a bot hand out roles that sit BELOW its own role in the server's role list. Lemon Bot creates its roles at the bottom of that list, which is also where Discord puts a newly invited bot — so until its role is moved up, it can create roles but not give them to anyone.

Administrator does not override this

Role hierarchy is separate from permissions. A bot with Administrator still cannot touch a role that sits at or above its own — that rule is what stops any bot from promoting itself to the top of your server.

The fix — about fifteen seconds

  1. 1Open Server Settings → Roles.
  2. 2Drag Lemon Bot above every role it manages. Dropping it just under your own top staff role is a good place.
  3. 3Close settings and press the role button again.
Before — buttons fail
  • Admin
  • Commander
  • Anti-Move
  • Solidera Fullbless
  • Solidera Nemesis Boss
  • Lemon Bot✕
After — buttons work
  • Admin
  • Lemon Bot✓
  • Commander
  • Anti-Move
  • Solidera Fullbless
  • Solidera Nemesis Boss
Order is what matters: everything Lemon Bot hands out has to sit below Lemon Bot's own role.
The bot finishes the job itself

The moment you move it, Lemon Bot slides the roles it created back underneath its own and confirms in its commands channel. There is nothing to re-run — though /repair does the same thing on demand.

Still failing after the drag?

  • If your server requires two-factor authentication for moderation, role changes fail until the bot's owner account has 2FA enabled — the error mentions code 60003.
  • Check that the bot's role still has Manage Roles. If its permissions were edited after the invite, that one may have been removed.
  • A role that someone created above the bot by hand has to be moved down, or the bot moved above it — run /repair afterwards to re-check.

How do I add the bot to my server?

Open the dashboard and press Add to Discord. You need Manage Server on the Discord you're adding it to — Discord only lists servers where you have that. Lemon Bot creates its channels on join, and the dashboard notices as soon as it lands.

The bot joined but nothing is happening

Joining only creates the channels. The bot starts tracking once you tell it which Tibia world to watch — run this in its commands channel:

/setupworld

Setup builds that world's channels and notification roles. Until it runs, the dashboard shows the server as still needing setup.

How do character links and auto-nicknames work?

Members link their own Tibia characters to their Discord account, server by server, pick which one is their main there, and Lemon Bot keeps their nickname in step with the character they are playing (the main when none is online). Links are per server: what you link here is not visible in any other Discord, so someone in two servers links in each — and can be a knight in one and a druid in the other.

The commands

  • /charlink <name>Claim a character. If this server has no main for you yet, the character you just linked becomes it.
  • /charlistShow everything linked to you, with ⭐ on this server's main and 🔒 on characters whose ownership was verified.
  • /charmain <name>Change which of your characters is the main in this server.
  • /charsync enabledTurn the nickname on or off for you, here. Turning it off restores the nickname you had before.
  • /charunlink <name>Give a character up. Any nickname based on it is put back, and if exactly one character is left it becomes your main.
You only get asked when there's a real choice

With one linked character, the bot never asks which is your main — it is that one, set the moment it can be. You are only asked to pick when you own several and this server has no main yet, because choosing a favourite for you is not the bot's call.

What the nickname looks like

A synced nickname is the level bracket, then the character name, then the vocation emoji. Long names lose their trailing words before anything is cut mid-word, so the nickname always fits Discord's 32-character limit.

Member list
  • [500+] Bubble ⚔️actually level 523 · Elite Knight
  • [450+] Dash Baby 🏹actually level 471 · Royal Paladin
  • [250+] Nqrido ❄️actually level 250 · Elder Druid
The level is a bracket, not your exact level

Levels round down to the nearest 50, and the + says so: level 523 shows as [500+] until you reach 550. An exact level would mean rewriting every member's nickname on every advance, which Discord rate limits — and [500+] is what people actually read when they're putting a team together.

Someone else already linked my character

Unclaimed characters link instantly, with no proof asked for. A character somebody else already holds can still be taken back, but only by whoever controls the Tibia account:

  1. 1Run /char link with the character's name. The bot replies with a one-time code.
  2. 2Log in on tibia.com, open that character's page and paste the code anywhere in its comment. Save.
  3. 3Run /char link again. The character moves to you, and you can delete the code from the comment.
Why the comment

Only the account holder can edit a character's comment on tibia.com, so it proves ownership without anyone handing over a password. The code expires after 30 minutes, and the bot reads the comment live rather than from its cache — so it sees your edit straight away.

Admins: turning it off

Nicknames sync from the moment a member links a character. An admin can switch the whole feature off for a server with /char settings nicknames:false — nobody's nickname is touched after that. Members can turn it off for themselves with /char sync, which puts their old nickname back, and only they can turn it on again.

The nickname isn't changing

  • Discord refuses to rename anyone whose highest role sits at or above Lemon Bot's own role. This is the same drag that fixes role buttons — see the role hierarchy answer.
  • Lemon Bot needs the Manage Nicknames permission. If it was unchecked at invite time or removed later, nothing is renamed and /char sync says so.
  • Discord never lets any bot rename the server owner — not even one with Administrator. Owners have to set their own nickname by hand.
  • Nothing changes between brackets. If you were level 512 and are now 540, the nickname is correct and was never meant to move — it changes when you cross 550. Levels are re-checked roughly every ten minutes.

What does /bazaar tell me about a character?

The Char Bazaar is where characters are auctioned on tibia.com. Point the command at a name and the bot fetches that character's live listing and lays it out as one panel — the auction itself, the character sheet behind it, and the seller's own pitch.

  • /bazaar<name>The character's current auction, in full.

What's on the panel

  • Level, vocation, world and sex, with the outfit the seller chose for the listing.
  • The current or minimum bid in Tibia Coins, and when the auction ends.
  • Gold carried, charm points, bestiary and bosstiary progress, hirelings, prey and hunting-task slots, imbuements and blessings.
  • The seller's sales arguments — the bullets tibia.com shows under a listing — each with the icon for its category.
  • Whether Soul War and Primal Ordeal are still open to a buyer, which depends on the quest lines already finished and the character's level.
Tibia Coins invested is a floor

The bot prices the store items a character carries against TibiaWiki's Store page. Three things keep the number under the truth rather than over it: potions, runes, casks and kegs are stock rather than an investment and are never counted; a product the wiki does not price is skipped instead of guessed at; and where the store sells several pack sizes the cheapest per unit is assumed. Read it as the least the character cost, not as a valuation.

Live auctions only

The command can only see auctions running right now. tibia.com's past-auctions page ignores a name search, so there is no way to ask what a sold character went for — and the bot says plainly that it could not find out rather than pretending it looked.

The Up For Auction post

You do not have to run the command to find out. When a tracked player is put up for sale, the activity scanner posts a summary to the activity channel by itself — the same sales arguments, and a link straight to the auction.

Why some players are never checked

CipSoft will not accept a character for auction while it is in a guild or owns a house, so the scanner only asks the bazaar about tracked players who have neither. Everyone else is skipped without a request — which is what makes checking a whole list affordable at all.

How do the item cooldown reminders work?

A few Tibia items can only be used once every so many days, and nothing in the game tells you when one comes back. The tracker is a private panel: a line per item, a button that stamps it as used, and a direct message the moment it is ready again.

  • /cooldownOpen your tracker panel.
  • /cooldowncharacter:<name>Keep a separate set of timers under one character's name.

Items tracked

  • Galthen's Satchel— 30-day cooldown
  • Jade Dragon Head— 14-day cooldown

Using it

  1. 1Run the command. The panel is ephemeral, so only you can see it — and only you can press its buttons.
  2. 2Press an item's button the moment you use it in game. The panel then shows when it comes back.
  3. 3Get on with your day. When the cooldown runs out the bot messages you, and you can stamp the next use straight from that message.
The reminder is a DM

Which means the bot has to be able to message you. If your Discord privacy settings block direct messages from server members, the reminder cannot arrive — the timer still runs, but you will have to open the panel yourself to see it.

Your timers follow you

Stamps belong to you rather than to a server, so the same cooldowns show up wherever the bot is. Adding a character name keeps a separate set under that name, which is how people track the same item on several characters.

How do I set up Tibia Observer, and why does it need a code?

Mini world changes and imminent raids are not public information. Tibia Observer reports them per account — what one account is entitled to see on its own worlds, and raids in the regions its own characters have explored. There is no server-wide feed to subscribe to, so Lemon Bot can only show a world's changes if somebody who plays there lends it their access.

One member is usually enough

This is not something everyone has to do. One linked account covers the worlds it plays on for everybody watching them, so a single well-travelled player is typically all a server needs.

Getting the code

  1. 1/observer in any channel of the server. The panel that opens is ephemeral — nobody else sees it.
  2. 2Press Add. A small form opens asking for an access token.
  3. 3In another tab, open your Tibia account page and follow Account Management → Tibia Observer → Connect.
  4. 4Copy the code the page gives you. It is short, it can be used once, and it expires quickly.
  5. 5Paste it into the form and submit. The reply tells you which worlds your link now covers.
Where the code lives on tibia.com
  1. Account Management
  2. Tibia Observer
  3. Connect
Open your Tibia account page
The code is never shown to the server

It is typed into a private form rather than given as a command argument, because a slash-command option is visible in the channel while you type it and this is a credential. The bot never echoes it back and never shows anyone else's link — the panel only ever shows your own.

If the code is refused

Codes can be used once and expire quickly, so the usual cause is simply that too long passed between generating one and pasting it. Generate a fresh one on the same page and try again.

What your link actually covers

The overlap between the worlds your account plays on and the worlds this server tracks — an account with characters everywhere still only covers what the server is watching. Tibia Observer also caps how many notification rules one account may hold, so the bot claims up to five worlds in priority order. If the reply says it covers nothing, the server has not set up any world your account plays on; an admin can add one with /setup.

Links are pooled

Every linked member's feed is merged, across every server. A world is covered if any linked member anywhere can see it, so a server whose own members have linked nothing still gets the feed for a world somebody else covers.

What linking changes on your account

Tibia Observer only reports what a notification rule asks for, so linking sets rules on your account: one mini world changes rule and one raid rule per covered world. Only rules carrying Lemon Bot's name are ever touched, so your own Observer notifications keep working exactly as they did.

Renewing and removing

The credential lasts about ninety days and the bot renews it daily on its own, so a link in use never lapses. If one does — after a long absence, or because you revoked it on tibia.com — the panel says it needs renewing and Add becomes available again for a fresh code.

Remove on the same panel unlinks your account and takes the bot's rules back off it. Nothing of yours is kept.

My server doesn't show up on the dashboard

The list only contains servers where all of the following are true:

  • The bot is in the server — an invite that was cancelled before authorising adds nothing.
  • You are the owner, an administrator, or hold a Discord role the owner granted dashboard access to.
  • The bot has finished creating its channels, which takes a few seconds after joining.

How do I give my team access to the dashboard?

Owners and administrators get in automatically. For everyone else, open Team Access on the server and pick which Discord roles grant access — a READ role lets holders view the data, a WRITE role lets them edit it too.

Access follows the Discord role: take the role away and dashboard access goes with it.

What needs premium?

The hunted and allied lists — players and guilds — and everything built on them: the ally and enemy tags on death posts, exiva lists, fullbless pokes, cross-server trophies, /hunted, /allies, /remove, /exiva, /guild-summary and the war feed. Premium also covers the respawn board, raids and mini world changes from Tibia Observer, the live online lists, guild activity, boss predictions, the /warfeed, /killfeed and /playerfeed analytics, the streamer list and go-live alerts for Twitch, Kick, YouTube and TikTok and the moderation panel. The death feed, trophies, boosted alerts, daily info, cooldown timers, the event planner, the dashboard and the other commands work on a server that never pays.

Nothing you set up is lost without premium. The lists and settings are kept, and come back exactly as they were when premium is active again.

New servers start with a trial so you can see the premium feeds before deciding. Run /premium in Discord to check what your server has left.

Still stuck?

If none of this covers it, bring the exact error message — the bot includes Discord's own error code, which usually names the cause outright.

Ask in the support Discord