You need to agree to share your contact information to access this dataset

This repository is publicly accessible, but you have to accept the conditions to access its files and content.

Log in or Sign Up to review the conditions and access this dataset content.

RinBot Anime Guessing Rounds

Every round of the RinBot anime-guessing game from four Discord channels, 2018–2026: 317,098 rounds · 638,819 caps · ~9,800 anime · 98 GB.

In a round, RinBot posts screenshots ("caps") from an anime one at a time. Cap 1 is usually a tight crop, and later caps show more. It keeps going until a player types the right title or time runs out, then it reveals the answer. One row = one round: the caps in the order they were shown, plus the answer and everything the reveal said.

Quick start

from datasets import load_dataset

ds = load_dataset("markjouh/rinbot-anime-rounds", split="train", streaming=True)  # all sources
row = next(iter(ds))
row["title"]   # the answer: the anime's title
row["caps"]    # list of PIL images, in the order they were revealed

small = load_dataset("markjouh/rinbot-anime-rounds", "animeultima", split="train")  # one source, 3 GB
anime_only = small.filter(lambda t: t == "anime", input_columns="round_type")

Video caps come with the original clip:

import io, av  # pip install av
for image, clip in zip(row["caps"], row["clips"]):
    if clip is not None:            # this cap was an mp4; `image` is a still from its midpoint
        video = av.open(io.BytesIO(clip))

Sources

config channel period rounds caps notes
rinbig #🧩・rin 2022-05 → 2026-06 248,595 495,003 jpg/png stills (3.5k mp4); 51,927 are character rounds
rinbot #rinbot (Peak Productivity) 2023-07 → 2026-06 51,915 96,892 jpg stills, then 5 s mp4 clips from 2025 on
testing #1–#10 of a "testing" category 2024-05-31 → 06-03 10,801 33,223 four days of bulk games spanning 6,635 different anime
animeultima #guess-the-anime 2018-11 → 2020-03 5,787 13,701 older bot version: text-only reveals, up to 5 caps, 10 s mp4 clips

Files live at data/<config>/<config>-NNNNN-of-NNNNN.parquet, with rows in chronological order. all (the default) is all four sources together. Everything is in a single split called train (the Hub's default name); there is no held-out split.

Round types

  • anime (262,072 rounds): name the anime from the caps. The answer is title.
  • character (55,026 rounds): name a character. These are either a bonus right after an anime round was won ("now guess a character from that anime") or from RinBot's character-quiz mode. The caps show the character (a scene crop and/or their AniList portrait). The answer is character.name, and title is the anime the character is from.

Fields

field description
round_id <source>-<reveal message id>-<a|c> (a = anime round, c = character round)
caps the caps as images, in reveal order. For an mp4 cap this is a still from the middle of the clip
clips aligned with caps: the original mp4 bytes for video caps, null for image caps
cap_info aligned with caps: cap_num (the bot's "Cap N"; 0 = untitled character portrait), kind (image/video), mime, sha256 and bytes of the original file, width, height, duration and has_audio (video only), quality_flag
n_caps caps shown before the round ended. A round stops as soon as someone guesses, so for won rounds this is how many caps the winner needed
title canonical anime title (RinBot's catalog title)
revealed_title the title exactly as that round's reveal showed it (titles change over the years)
alt_titles alternative titles from RinBot's reveals of this anime (English, Japanese, abbreviations)
anime_id RinBot anime UUID
mal_id, anilist_id, anidb_id MyAnimeList, AniList and AniDB ids
difficulty RinBot's difficulty tier for the anime: EASY, NORMAL, HARD, EXTREME, NIGHTMARE
year, format, aired start year; TV Series/Movie/OVA/Web/TV Special/Music Video/Other; air date as the bot shows it
nsfw RinBot's rating: SAFE, NOT_SAFE, QUESTIONABLE
poster_url cover image URL from the reveal
character character rounds only: name, character_id (RinBot UUID), url, image_url
outcome won, noone (time ran out), or unknown (the reveal had no result banner)
winning_guess exactly what the winner typed, abbreviations and typos included (e.g. sxf, rezero)
winner_id pseudonymous player id: the first 12 hex chars of sha256("rinbot-anime-rounds|" + username)
source, channel which scrape and which Discord channel
reveal_msg_id Discord message id of the reveal
started_at, revealed_at UTC timestamps (started_at is missing for 82 rounds)
label_match how the row was linked to RinBot's catalog: rinbot_id or mal_id (from the reveal's link), title or alt_title (by name, for reveals without a link), or unmatched
repairs fixes applied to this row during cleanup (see below); empty for 94% of rows

At a glance

difficulty anime rounds distinct anime
EASY 26,333 192
NORMAL 35,688 377
HARD 61,194 1,091
EXTREME 109,544 3,093
NIGHTMARE 29,246 4,755

Caps needed in anime rounds: 1 cap in 109,728 rounds, 2 in 43,849, 3 in 48,774, 4 in 58,564, and 5 in 1,157 (5-cap games exist only in animeultima). Anime rounds were won 219,863 times, and nobody got 42,209 of them.

How it was cleaned

Every media file in the raw scrape was checked against its SHA-256 (none missing or altered), and the packed dataset was re-verified byte for byte. Fixes are recorded per row in repairs:

  • split_from_character (10,014 rounds, 2 rows each). When a won anime round triggers the character bonus, RinBot postpones the anime reveal until after the bonus. The scraper therefore glued the anime round's caps onto the following character round. These were split back into the anime round (outcome won; the winner and guess weren't recorded) and the character round. Both halves share reveal_msg_id.
  • label_from_meta (67 rows): character reveals whose anime title the scraper failed to parse, recovered from the reveal text.
  • dropped_unrevealed_caps (13): cap numbering restarted mid-round because an earlier round was never revealed. Only the caps of the revealed round were kept.
  • deduped_double_post (12): the same cap was recorded twice in a row.
  • dropped_broken_media (7): empty or corrupt video files were removed.

Also:

  • quality_flag marks 263 caps as blank (solid black or white frames) and 16 as RinBot's "NO IMAGE" placeholder. They are kept, just flagged.
  • alt_titles, format, aired and poster_url are merged across all reveals of the same anime, so every row of that anime carries the same values.
  • The 2018–2020 bot (animeultima) revealed only a title, with no link. Those titles were matched to RinBot's catalog by name for 99.4% of rounds; 37 rounds are unmatched and have no ids.
  • Player usernames are replaced by winner_id.

Things to know

  • Sequels, seasons and movies are separate anime, exactly as RinBot scores them (e.g. Shingeki no Kyojin vs Shingeki no Kyojin Season 2).
  • n_caps reflects the players, not the puzzle. Rounds that ran to 4 caps are mostly ones people found hard. One winner_id holds 64% of all wins and is very likely an autoplay bot.
  • Caps get reused. The 638,819 caps are 609,037 distinct files, and cap_info.sha256 identifies repeats (a few appear under sequels of the same show).
  • Some caps show on-screen text (title cards, logos) that gives the answer away.
  • 1,693 rounds are from anime RinBot rates NOT_SAFE.

Provenance

Scraped with a Discord user account from channels its owner could read, for personal archival and research. The images and clips are frames of copyrighted anime. Keep this dataset private and don't redistribute it. It was built from the local scrape folders dataset/ (→ rinbot), rinbig/, category_rounds/ (→ testing) and animeultima/ by the scripts in ~/discord-scrape/hf/scripts/.

Downloads last month
23