Skip to content

IsAy15/anime-relations

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 

Repository files navigation

Anime Relations

This repository includes anime relation data for Taiga. It is used to redirect an episode to another, which is required to handle special episodes and the case where fansub groups use continuous numbering scheme in their releases.

Rule syntax

10001|10002|10003:14-26 -> 20001|20002|20003:1-13!
└─┬─┘ └─┬─┘ └─┬─┘ └─┬─┘    └─┬─┘ └─┬─┘ └─┬─┘ └─┬─┘
  1     2     3     4        1     2     3     4
  1. MyAnimeList ID
    https://myanimelist.net/anime/{id}/{title}
  2. Kitsu ID
    https://media.kitsu.io/anime/{id}/poster_image/{size}.jpeg or
    https://kitsu.io/api/edge/anime?filter[text]={title}
  3. AniList ID
    https://anilist.co/anime/{id}/{title}
  4. Episode number or range
  • ? is used for unknown values.
  • ~ is used to repeat the source ID.
  • ! suffix is shorthand for creating a new rule where destination ID is redirected to itself.

Example

The first season of Fate/Zero has 13 episodes, yet it is possible to encounter filenames that go beyond this number:

[Coalgirls]_Fate_Zero_14_(1280x720_Blu-ray_FLAC)_[E56A8415].mkv

To handle this case, we create the following rule:

# Fate/Zero -> ~ 2nd Season
- 10087|6028|10087:14-25 -> 11741|7658|11741:1-12!

Here we declare that 14th to 25th episodes of Fate/Zero are to be identified as the 1st to 12th episodes of Fate/Zero 2nd Season:

S1 14 15 16 17 18 19 20 21 22 23 24 25
S2 1 2 3 4 5 6 7 8 9 10 11 12

By appending an ! to the rule, we also handled the cases such as Fate Zero S2 - 14. This basically creates another rule:

# Fate/Zero 2nd Season -> ~
- 11741|7658|11741:14-25 -> 11741|7658|11741:1-12

How to contribute

  1. Look up MyAnimeList, Kitsu and AniList IDs of both anime.
  2. Create a new rule and place it in alphabetical order, using the main title from MyAnimeList.
  3. Update the last_modified date in YYYY-MM-DD format.
  4. Make sure the rule is working, by testing it before sending a pull request.
  5. In the pull request description, indicate which fansub groups' releases require the new rule.

License

This repository is in the public domain.

Releases

No releases published

Packages

No packages published