Skip to content

@mergeuser

Permission: ADMIN

Repair one player who is split across two accounts, folding the duplicate into the original. Points for every period, streaks, question records, kudos payout history and hostmask ownership move to the keeper; the duplicate row is deleted.

Splits happen when a player's hostmask changes shape — a Gazelle cloak that temporarily falls back to an IP cloak, or a user-class promotion that rewrites the host. Since v0.10.1 the bot links a new hostmask to the existing account instead of duplicating it, so this command exists to clean up accounts that split before that, or in edge cases the linking cannot resolve.

Syntax

@mergeuser <keeper> <loser>

Each argument is a nick or an account id written id:N (a bare 34 works too — IRC nicks cannot start with a digit). Duplicates share a nick, so id:N is usually required; passing a nick that matches several accounts lists the candidate ids and their hostmasks instead of guessing.

Why id:34 and not #34

Limnoria reads a leading-# word as an explicit channel argument and removes it before the command runs, so @mergeuser #34 #62 would arrive as a single argument in channel #34.

The command shows a preview of everything that will move and waits for @confirm. Previews expire after 5 minutes. The merge cannot be undone.

Example

@mergeuser id:34 id:62
Merge preview on ptp: id:62 scroll ([email protected], 3,140 pts) INTO id:34 scroll (ScroLL, 147,920 pts)
Moves: 82 score rows, 112 question records, 1 hostmasks. Result: 151,060 pts.
This cannot be undone. To confirm, type: @confirm

@confirm
Merged id:62 scroll into id:34 scroll: 151,060 pts, 112 records moved.

Notes

  • Both accounts must be on the same network.
  • Merging two accounts with different nicks deletes another player's record, so it is refused when the loser holds MANAGE or higher permission — the same protection @points combine applies. Two accounts sharing a nick are one person's split identity, so that check does not apply to them.
  • Hostmask ownership moves to the keeper, which is what stops the duplicate from reappearing the next time that cloak is seen.
  • @points combine merges two different players, discarding the source's daily/weekly/monthly scores so period leaderboards stay honest. @mergeuser sums every period instead, because both accounts are the same person.