Back to the current journal
Watercolor illustration of a hand arranging anime article images on a website layout.
An existing journal illustration of selecting anime coverage for I Crave Anime.

I Crave Anime · Rankings

Why an 8.5-rated anime sits sixth on our board

Published by Derek

The sixth entry on I Crave Anime’s October 15 seasonal snapshot has the highest displayed score of the six: 8.5 out of 10. The first has 7.5. Sorting the list by those scores would put them in a different order. It would also change what the list measures.

The board labels its positions as a trending snapshot and displays community ratings beside them. Sixth means sixth in that saved order, not sixth-best by score. That distinction is stated in the row descriptions, but the page title—“Full seasonal rankings”—still asks a small word to do quite a lot of work.

I prefer rankings that finish the sentence: ranked by what? This board offers a useful example of why the answer belongs beside the numbers, rather than being left for the reader to infer.

The position and the score answer different questions

In the dated board, Reincarnated as a Sword Season 2 appears first with a saved community score of 75/100, displayed as 7.5. The Apothecary Diaries Season 3 appears sixth with 85/100, displayed as 8.5. These are the titles and values recorded on our page, not a fresh check of their current scores or release status.

The board’s updater is configured to request AniList’s trending-descending order and separately read each entry’s average score. It preserves the returned entries’ order when numbering them, rather than sorting them by score. That explains the intended distinction between position and rating. The code and saved board support this explanation, but the original October 15 AniList response has not been authenticated for this article; the historical positions here are the board’s recorded, labelled order.

AniList’s field definitions explain the difference. trending describes related activity in the past hour. averageScore is a weighted average of users’ scores. AniList also has a separate popularity field for the number of users with a title on their list. Its sorting options distinguish trending, score and popularity rather than treating them as interchangeable.

None of that makes trending a count of people watching an episode. Nor does the documentation identify which particular activity explains these saved positions. A new announcement or a much-discussed episode might be something to investigate, but the board supplies no evidence for either explanation here. I would leave the cause open rather than write a plausible little story around the order.

What those two rows actually let you say

The sixth entry has a higher saved community score than the first. That is a direct comparison of the values shown. It does not establish that the sixth entry had more viewers, more recent activity or a larger voting sample.

The board does not show the score sample sizes. Without those, I would not describe the difference as equally well established across the two titles, or infer how many voters separate them. The weighted score also should not be described as a simple arithmetic mean: AniList gives that its own field, meanScore.

There is a smaller trap in saying that the first title “beat” the sixth. Beat it at what? The first occupies a higher position in the board’s labelled trending order. The sixth has the higher displayed rating. Both statements can hold without either number being wrong.

For someone deciding what to watch, the distinction changes how to use the page. Trending can supply a discovery list to investigate. A community rating supplies another piece of information about those entries. Neither can tell you whether you like the premise, need to watch earlier seasons or want that particular kind of show tonight. I would use the board to find a candidate, then follow its source link and look into the title—not treat the row number as a recommendation tailored to me.

A smaller scale does not create a new verdict

I Crave Anime displays the saved scores on a ten-point scale. A value of 75 out of 100 becomes 7.5 out of 10; 85 becomes 8.5. Dividing both by ten changes the notation, not their order or their meaning.

The illustrated bowls are another representation of that same score. On the five-bowl scale, 75/100 corresponds to 3.75 bowls and 85/100 to 4.25, with partial fills. They are not an extra staff rating that confirms the number beside them. Counting the bowl illustrations without noticing their fill would lose information the decimal score retains.

That is why the page’s explanation—community scores, not I Crave Anime review verdicts—matters. A distinctive visual treatment can make a borrowed measurement look like the site’s own judgment. The artwork should help someone read the score, not quietly add another apparent vote of confidence.

The date limits the whole comparison

The snapshot is labelled October 15. The wording above deliberately keeps that date attached to its values. A page remaining available later does not turn its saved trending order into a report of the past hour now.

That matters especially for a field AniList defines through recent activity. A saved order can describe the captured list; it cannot establish what is trending today. Likewise, a score beside it can have changed since the snapshot. The public page itself warns that trending order and community scores may change after publication.

An old snapshot is not inherently useless. It can preserve what a board displayed at a particular point. The mistake would be selling it as a live answer. If a reader wants today’s order, the next task is a new source check and an honestly dated update—not simply removing the old date or relabelling the same data “current.”

Decide which list you mean to build

For a small publication, there are several defensible choices here. They serve different purposes:

  • A trending snapshot answers which entries appeared in a particular activity-based order when captured. Keep its capture date and explain the signal.
  • A community-score list answers which entries in a defined set have the higher saved ratings. Name the set and date, and explain any eligibility rules rather than implying it ranks every anime.
  • An editorial recommendation list answers what the publication recommends and why. It needs reasons about the works, not just a new label pasted onto community scores.

I would not “fix” the existing board by silently sorting its scores. That would replace its question while leaving a reader to guess what changed. If a score-sorted alternative is useful, give it an explicit label and explain the comparison pool. Nor would I turn this six-entry board into a claim about the best anime of the season: the evidence here does not establish that broader contest.

The unresolved design question is whether the explanation is prominent enough. A useful next test would ask someone to explain why the 8.5 entry appears sixth using only the page. If they conclude that the site rated it below the 7.5 entry, the labels have not done their job. That is a proposed comprehension check, not a test result or a claim that readers have complained.

For this snapshot, the answer is straightforward: the position is labelled as trending order, the decimal displays a saved community score, and neither is a staff review. Keep those three facts together and an apparently contradictory ranking becomes readable.