[RikCost]

Fixes the Ranobes multisrc template (Ranobes (RU) on ranobes.com and Ranobes on ranobes.net).

• Chapter order: the site's table of contents is newest first and the novel page only shows the latest chapters, so the app listed chapters backwards, starting from the newest page. Chapters are now paged by index from the first one: app page k holds chapters 25(k−1)+1…25k, built from the two neighbouring site pages (only the site's last page is partial). Because the table of contents is newest first, every new chapter shifts all its pages; each page request therefore re-reads the newest page, counts the chapters published since the last request, and places freshly fetched chapters by their index from the first chapter, so releases while paging do not repeat or skip chapters. latestChapter is the newest chapter. If the table of contents cannot be loaded, the error reaches the app (WebView hint) instead of silently showing the latest chapters as page 1.
• Table of contents URL: it is taken from the novel page's "Перейти в оглавление" link. Its slug can be shorter than the novel slug, and the URL derived from the novel path answered 404 for such novels.
• Summary (RU): the description block lost its itemprop="description" / moreless attributes, so summaries were empty. The plugin now takes the first cont-text block inside .r-desription, skips its inline <style> and keeps paragraph breaks.
• English domain: ranobes.top now answers 403; the same site works at ranobes.net. Its "One moment..." challenge page is now treated as a captcha, so the app asks to open the WebView instead of showing an empty list.
• English search: ranobes.net answers HTTP 404 when a search finds nothing, so every search without a match (e.g. any global search) failed with "Could not reach site (404)". A 404 from the search page now means no results.

Version 2.0.2 → 2.0.3.

Testing

• Ranobes (RU): live check that bundles the plugin and calls popularNovels, searchNovels, parseNovel, parsePage and parseChapter. On "Лабиринт монстров" all 652 chapters come out over 27 pages in increasing order without duplicates (page 1: 1–25, page 14: 326–350, last page: 652–653). Novels whose table of contents slug differs from the novel slug (e.g. "Мужчина во главе женского флота") load again. Summaries are plain text.
• Ranobes (EN): the site is behind a browser challenge from my network, so I checked it in a real browser. The table of contents is newest first with pages_count (page 1: chapters 691→666, page 28: 14→1), and the catalog and chapter links work on ranobes.net.
• Ranobes (RU) tested in the LNReader app on Android through a local plugin repository; the ranobes.net switch is not yet tested in the app.

Related: #1953 (next chapter jumps to the first chapter of the previous page). The chapter list is now in increasing order across pages, which should fix it; not yet verified in the app on the English source.

Checklist

• Update version code if an existing plugin was modified
• Test changes in Plugin Playground or the app
• Reference related issues in the PR body (e.g. Closes #xyz)
• Commit messages follow type(scope): description (e.g. feat(<generator>): add new source)

This change was written with an AI coding agent (Claude Code) and reviewed and tested by the author.

🤖 Generated with Claude Code

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The changes affect chapter reading and English browsing in the two Ranobes sources.

Fix chapter paging before merging; newly published chapters can make readers skip a chapter and see another twice.

Findings

1.  Growing novels skip chapters ▶

Summary

Updates both Ranobes sources to read chapters from oldest to newest.

• Ranobes chapter pages run from the oldest chapter to the newest.
• Russian summaries keep the text and paragraph breaks from Ranobes descriptions.
• English Ranobes uses ranobes.net and handles its site responses.

_{Reviews (2) · Last reviewed commit: "fix(ranobes): return no results instead ..." · Reviewed by Greptile}