Move over from another bot

Moving from another levelling bot takes three steps, all in Levelling history on Import, under Settings: bring members' levels over, let members try Colossus beside the old bot, then switch. Nothing is announced and no role moves until you switch, so you can take your time.

You need permission to change levelling, which the Manager and Admin presets have. Moving over is on every plan.

Bring levels over

Press Bring levels over. The bots still in your server are listed first, then every other bot Colossus knows, then Another bot for one it does not. Pick the bot you used, and Colossus shows the ways its levels can come over, the Most accurate first. Each way says what it brings, and, where it cannot be taken yet, what it needs.

For a bot without a file way of its own, Upload a file it exported is offered last, under its ways, and takes a file anyway.

What each way needs

• A leaderboard is read straight from the bot. MEE6 and Lurkr share only a public leaderboard: in MEE6's dashboard turn on "Make my server's leaderboard public", and in Lurkr's set the leaderboard's visibility to Public. Kiai answers only an application your server has authorised: run the /application authorize command the dialog shows, allow it to read levels, then read. Tatsu's own levels are global rather than your server's, so its server score comes over instead, counted as XP on your curve. The sentence under the picked way says which level the read starts from; raise it to skip members below that level.
• Level-up messages are read from your server's history: each member's level from the last level-up the old bot announced about them. Anyone it never announced, or whose message is gone, is missed. Colossus needs the Message Content intent to read them; see Server settings. If you changed the old bot's wording, type it into the sentence under the picked way, with {user} where it named the member and {level} where it named the level. For Another bot, type the bot's user ID.
• A file is a CSV or JSON export with a userId column and a level or XP column for each member, exact for everyone in it. Rows with only XP are placed on levels by the curve under Read XP with, which starts on the bot's own curve. If anyone in the file is above the highest level your curve reaches, raise it on Earning XP first.
• Reward roles lift every member holding one of your reward roles to at least its level. Add the roles the old bot gave at each level as rewards first. This counts at once, with no review.
• Members telling you their level is for a bot Colossus cannot read at all: each member types the level they had, and you approve it; see Catch who's missing.

Some reads carry the old bot's settings too, such as its reward roles, its pace, its level curve, where its level-ups posted and its level-up message. Each waits, faded, on the page it belongs to until you use it or turn it down, and Levelling history links to them.

Review a run before it counts

A leaderboard, messages or a file start a run, which reads in the background and then waits in Levelling history for you. Press Review to see what counting it would do: how many members it lifts, lowers or leaves where they are, filtered by Going up, Going down, Unchanged, Never seen and Left, with what the old bot said beside each member's level now and with the run. It also lists the reward roles counting it would give and take; none move before you switch.

Press Count these levels to count it, or Discard run to throw it away. A counted run can still be switched off with Counts toward members' levels, or set to count only a share of what it brought, as the XP for each member's old level or as their old XP, then saved.

A member never ends up lower than what Colossus counts from their own history here. With a run counted, they stand at whichever is more: what the old bot said of them, plus everything they earned here since it was read, or what their activity here adds up to. Where several runs name the same member, the one that places them highest counts.

Catch who's missing

Once levels are in, Catch who's missing offers what catches the members a read missed:

• From reward roles: lift members to the reward roles they hold, as above.
• Let members claim: a member types the level they had with /claim in your server. Nothing counts until you check it: each claim waits in Level claims under Requests, beside the member's level here now, for you to Approve or Deny. Check it against the old bot first, for example with its /rank on that member while it is still in your server. A member has one claim waiting at a time; a new /claim replaces it. Members can claim once you save and levelling is on, as it is during the trial. The claims row in Levelling history turns them off.

Let members try it

The move's two steps show in Levelling history once there is something to move from: another levelling bot in your server, or levels brought over. There, Start the trial turns levelling on as a trial. Members can use /rank, /leaderboard and level claims beside the old bot, and Colossus keeps counting, but nothing is announced and no role moves. Use the trial to check levels look right and to fix your rewards; the section warns about reward roles Colossus cannot hand out yet. If levelling is already live, going back to a trial asks first, since it stops level-ups and role moves until you switch.

Switch over

When you are ready, press Switch…, then Switch now. From that hour on, Colossus runs levelling in place of the old bot: members keep the levels they have, level-ups are announced, and reward roles move. Count any run still waiting for review before you switch, so members start with it.

Then turn off the old bot's levelling, or remove the bot, so members do not get two level-ups and two sets of roles. The section reminds you while the old bot is still in your server.

Undo the switch takes you back to before the switch. No member's XP or level changes, and level-ups and reward roles keep running; start the trial again if you hand levelling back to the old bot.