To copy paste from a post last month (MR search isn't working very well):
You can try
check_next_chapter and
meta_from_last_chapter.
Code:
## ffnet used to have a tendency to send out update notices in email
## before all their servers were showing the update on the first
## chapter. It generates another server request and doesn't seem to
## be needed lately, so now default it to off.
check_next_chapter:false
## ffnet sometimes doesn't update the metadata on the first chapter
## immediately. meta_from_last_chapter:true will instruct the adapter
## to take the metadata from the last chapter instead of chapter 1.
## It can generate another server request and usually isn't necessary,
## so it defaults to off.
meta_from_last_chapter:false
Beyond that, broken site is broken.
Note that if the last chapter is visible,
check_next_chapter will cause repeated attempted on a chapter that isn't there before failing.
Another (hopefully temporary) kludge option that was added last release for ffnet only is:
Code:
try_shortened_title_urls:true
This is for when random chapters are listed, but don't work. It's not currently documented in defaults.ini because temporary kludge.
Another option that can help when only a few chapters fail, but others work is:
Code:
## Errors on more common during long downloads. This way, at least
## the chapters the worked are saved. Often running an update will
## fix the error chapters.
continue_on_chapter_error:true
Bad chapters will be marked, but the entire download won't be discarded.