x15987856/anime-fighting-simulator-codes

Anime Fighting Simulator codes, as data

A small, CC0 dataset of reward codes for the Roblox experience Anime Fighting Simulator, published as a flat CSV so it can be diffed, joined, or charted without scraping a web page first.

The point of this repository is not the list. Plenty of sites publish the list. The point is that this one records what is known and what is not, as separate facts.

What is in here

File	What it is
codes.csv	The data. One row per code.
DATA.md	Field definitions, the meaning of each status value, and an explicit list of what is missing.
LICENSE	CC0 1.0 Universal.

Why another codes dataset

Three things most published code tables do that this one tries not to:

1. They silently resolve disagreements. When trackers contradict each other, the usual move is to pick one and publish it as fact. Here a contradiction is recorded as disputed, with the date attached.
2. They treat absence of evidence as evidence of absence. If nobody published a level requirement, a reader cannot tell whether that means "no requirement" or "nobody checked". The conditions field distinguishes the two.
3. They drop the conditions. A code and its reward are only half the story — the update it shipped with and whether a gate applies are what make the row usable six weeks later.

Source and verification

• Source site. This table is compiled and maintained at https://animefightingsimulators.com/, an independent reference site. It is not affiliated with Roblox Corporation or with the game's developers. codes.csv is the machine-readable export of that table, byte for byte.
• How a row is verified. A code is marked active only when more than one independently maintained list, dated within a few days of each other, agrees it is working. Where those lists disagree on the same date, the row is marked disputed and left unresolved rather than settled by picking a side. Where no source publishes a fact — a level gate, an expiry timestamp, a region or platform restriction — the field says so explicitly instead of filling the gap with a plausible number.
• How often it changes. There is no fixed schedule. Codes in this title rotate alongside game updates; per the maintained page, numbered updates have historically landed roughly once a month, with additional compensation codes issued after unscheduled downtime. This dataset is refreshed when the maintained table changes, so treat verified_on as the freshness marker: if the newest row is more than about a week old, re-check before relying on the active set.
• Maintainer. x15987856 on GitHub.

Using it

Anything that reads CSV:

import csv

with open("codes.csv", newline="", encoding="utf-8") as f:
    for row in csv.DictReader(f):
        if row["status"] == "active":
            print(row["code"], "->", row["reward"])

# active codes only
awk -F',' '$2 == "active" { print $1 }' codes.csv

The reward field is semicolon-delimited inside a quoted CSV field, so split on ; after parsing, not before.

Status values at a glance

• active — multiple independent sources agreed on the verified date.
• disputed — sources disagreed on the same date. Not resolved, because it cannot be.
• expired — no source still lists it as working.

Refresh cadence

Codes in this game rotate quickly, sometimes within days. Treat verified_on as a shelf life, not a timestamp of glamour. If you are reading this more than a week after the date on the newest row, the active set has probably changed.

License

CC0 1.0 Universal — public domain. Do what you want, no attribution required.

A maintained, human-readable version of this table is published at https://animefightingsimulators.com/.