This community is the place to discuss and ask questions about anime, anime news, and related topics.
Currently airing show discussion threads are created by our resident bot, [email protected]. If it doesn't make a thread for an episode that you want to discuss, see the user guide on the wiki for instructions on how to request that rikka make a thread for you to use.
Check out our wiki to find:
T・P Bon, episode 13
Alternative Names
Time Patrol Bon, タイム・パトロールぼん
Additional Links
Reminder: Please do not discuss plot points not yet seen or skipped in the show. Failing to follow the rules may result in a ban.
All discussions
| Episode | Link |
|---|---|
| 1 | Link |
| 12 | Link |
| 13 | Link |
This post was created by a bot. Message the mod team for feedback and comments. The original source code can be found on GitHub.
This is the second batch of the episodes that have been released. Due to the batch release, the bot only makes a thread for the first episode and later episodes are not requestable via pm. If you want a thread made for a later episode, let me know and I can manually create one. Sorry for the inconvenience!
Thanks. Have only watched 1 ep so far, will let you know if I need threads for other eps.
Question: Must episode numbers always be in sequence? Netflix seems to number them from 1 again for this season (so ep 13 is ep S2E1), is that something this anilist API / rikka would be able to handle?
The difference between a new season vs. an additional cour of the same season often just depends who you ask. Different databases will have it presented in different ways. The AniList api presents this as the second cour of the first season, so that is how rikka sees them. The first batch and second batch share the same AniList id number, so there isn't any way to separate them in rikka's database since the AniList id number is the unique identifier for each show and the database doesn't allow multiple (show, episode #) listings due to a uniqueness constraint in the SQL.
So, short answer to your question is that, like most software issues, it could be solved. However, it would basically require completely rewriting rikka from the database up and finding a different api to pull from.
Thanks.