Remove the Paged Layout from the Chapter List in the Novel Fire Plugin

[Pheonix-Flames]

The latest update of the Novel Fire Plugin (1.1.7) introduced a Paged Layout in the chapter list, which I dislike for several reasons. First, it complicates finding the total number of chapters in a novel and makes navigating more difficult, as I need to scroll to the bottom each time to switch pages. Additionally, it glitches: for instance, if I’m reading a chapter on page 3 and use the '<' navigation button to go back, it incorrectly jumps to chapter 100 instead of the previous chapter. This is quite frustrating since I have to repeatedly scroll to the end to change pages, and the functionality is unreliable. Please consider removing this feature.

[Rojikku]

It's always been an option to remove it.
I'm somewhat baffled everyone is complaining about an option that you can turn off.

If you don't see a gear, you may have to reinstall the plugin. Also not a big deal, I do that like 5 times while testing without losing reading progress.

For the setting to apply, you have to restart the app once you turn it on. Possibly also a main app bug.

Gear issue bug report - Like if it applies to you and comment if you have unique information.
You can open bug reports for other pages issues on main app repo. Those aren't my domain, outside the scope of what I've worked on.
Do check that no other loyal reader already did so, though! If they did, up vote it or add details in a comment so other devs know multiple people have that issue.

Anyway, once you turn that setting on, refreshing novels will convert them from paged back to what you expect.

Why did I default to paged? Novelfire reverted their website back three months. I wrote for the plugin to fall back to the old code, which worked this way, and fixed a couple bugs while I was at it. If novelfire updates again, it will automatically and silently return to using the new code. Assuming they update to the same way it was last week.
I have to query every page you see in paged, individually, in that code. Sending 20 requests should not be the default result of you opening any random novel.
It can get you rate limited, or possibly judged a spammer or something, which could result in an IP ban or timeout. I felt you'd hate that a lot more than the paged option.

Suggestion

If you're browsing for new novels, I suggest using paged until you've added the ones you want. Then switch back to monopaged and load all the chapters.
Otherwise you're sending one request per page of every single novel you check.