ODO Account Sharing Report

Reads a txAdmin playersDB.json and pairs up player records that look like the same hands behind different accounts — one Discord on several players, several Discords on one player, and different players on the same PC.

Drop your playersDB.json here

The file is read inside your own browser. Nothing is uploaded, and your file is never changed.

This page carries no player data of its own — it only ever reads the file you give it. On a txAdmin host the file sits in txData/.

How these are worked out, and what they do not prove
  • A player record is one entry keyed by its license — one game account. Two records mean two game accounts.
  • Two records are compared on two things: the discord: IDs they hold, and their hwids (machine fingerprints). Every record in this file has hardware data, so "no hardware in common" is real evidence rather than a gap.
  • Both active in the same period means the two records' first-seen → last-seen windows overlap. It does not prove they were online at the same moment; the database only keeps a first and last connection, not a session log. Treat it as "worth checking", not as proof.
  • Sequential means one record went quiet before the other started. That is the normal shape of one person moving to a new PC or a new game account, so it is ranked lower.
  • Names are compared after stripping tags and punctuation, so OLG | AKKRUMON matches AKKRU MON. A matching name pulls confidence down — it points at one person, not at sharing.
  • Hardware IDs can legitimately collide for people on the same prebuilt machine or the same household PC. A single matching token is weak; several matching tokens is strong.
  • Bans and warns are matched from actions[] on any identifier the record holds. A ban is active if it has no revocation and has not expired.