Home ยป Forum ยป Bug Report and Feature Requests

Forum: Bug Report and Feature Requests

Request - "This story is complete"

doctor_wing_nut ๐Ÿšซ

I know all authors have different posting schedules, which can lead to some frustration for those of us born without the 'Patience' gene, but that's just how it goes. However, I would LOVE to see a notice in the description area that the story is actually finished. Knowing that there will eventually be an ending would make the wait more tolerable, and avoid the dreaded 'Readus Interruptus' syndrome. It could be as simple as a check box on the submission form. Anyone else think this might be useful?

Replies:   joyR  Keet
joyR ๐Ÿšซ

@doctor_wing_nut

Anyone else think this might be useful?

Unless it was 'triggered' by an author uploading every chapter for delayed posting of a completed story, it would be meaningless.

It is not unknown for a story to be marked as complete only to have an epilogue added some time later.

Currently every story is either marked, in progress, incomplete, or completed, so a further check box seems redundant.

Ernest Bywater ๐Ÿšซ

@joyR

The few of us that finish a story before we start to post it usually mention that in a blog entry when we start to post the story. Also, most of us that do that tend to load the story with delayed posting dates so you get the rest of the story on schedule, even if we go on holidays etc.

Replies:   joyR
joyR ๐Ÿšซ

@Ernest Bywater

Indeed.

Switch Blayde ๐Ÿšซ

@joyR

Currently every story is either marked, in progress, incomplete, or completed, so a further check box seems redundant.

I think doctor_wing_nut is talking about stories that the author finished but is posting a chapter at a time over a period of time.

That would differentiate the two types of "in progress" stories: 1) finished but not all chapters posted yet and 2) the author is writing it as he's posting it so it might get finished or it might not. The reader doesn't know.

Replies:   joyR
joyR ๐Ÿšซ

@Switch Blayde

I think doctor_wing_nut is talking about stories that the author finished but is posting a chapter at a time over a period of time.

I think so too. However there is no certainty that every author using that feature will do so diligently and if they don't the new feature would be pointless.

awnlee jawking ๐Ÿšซ

@joyR

It is not unknown for a story to be marked as complete only to have an epilogue added some time later.

I can recall a story subdivided into three books. At the end of each book, the 'complete' marker was set. Then when the next book started, the 'complete' marker was unset. Confusing!

AJ

Replies:   Switch Blayde
Switch Blayde ๐Ÿšซ

@awnlee jawking

I can recall a story subdivided into three books. At the end of each book, the 'complete' marker was set. Then when the next book started, the 'complete' marker was unset. Confusing!

If the first book truly ended, I would have left it complete and started a new book. If the reader shouldn't read the second book without reading the first, I would have made them an ordered series.

Replies:   awnlee jawking
awnlee jawking ๐Ÿšซ

@Switch Blayde

In this example, the term 'book' was used as a story partition. All three books were part of a single SOL story.

AJ

Replies:   Switch Blayde
Switch Blayde ๐Ÿšซ
Updated:

@awnlee jawking

All three books were part of a single SOL story.

Then he shouldn't have listed the first one as complete.

But the "Lord of the Rings" trilogy is 3 separate books.

Keet ๐Ÿšซ

@doctor_wing_nut

It would be a welcome addition but only if the author has uploaded all chapters with delayed posting. That is the only way that such an indication would be reliable for readers.

Replies:   Switch Blayde
Switch Blayde ๐Ÿšซ

@Keet

It would be a welcome addition but only if the author has uploaded all chapters with delayed posting. That is the only way that such an indication would be reliable for readers.

I always finish a story before posting the first chapter. But I never upload all chapters using the delayed posting.

Why?

1. Sometimes the whole story is written, but I do the final edit to a chapter right before posting it (only minor changes).

2. I determine when to post a chapter on the fly. Going in, I plan on posting a chapter a week on the same day of the week. But sometimes when I'm ready to post I decide to post two chapters instead of one. Sometimes I post on a different day of the week thinking I might find a new reader. Sometimes I post a chapter earlier than I had originally planned. That just happened with the novel I'm posting now. I had three chapters that were rather dark โ€” rape, abuse, etc. โ€” that didn't go over well with some readers. So I posted the next chapter earlier than expected as it's more representative of the novel as a whole.

Replies:   Grey Wolf  Keet
Grey Wolf ๐Ÿšซ

@Switch Blayde

I'm very much the same here. Mind you, I'm still posting my first story, but the story was 'done' before posting. That said, more editors joined the project, so what was 'done' is not 'done' now. But, if I had to post the whole thing in its current form, it's work I'd be proud of.

I also sometimes adjust posting. I don't intend there to be cliffhangers; the work was written with the assumption that a reader could just read on. I don't want to create an artificial cliffhanger with major suspense, so a few chapters have needed to be posted together.

I wouldn't have started posting if it wasn't 'done' to my basic satisfaction; that's not good for readers.

Ernest Bywater ๐Ÿšซ

@Grey Wolf

Fixing typos and improved editing is the main reason behind my re-posting stories and chapters of stories as I re-post them once I'm aware of them and fix them. That's one of the advantages of being an e-publisher on sites like SoL, I can be responsive with changes.

Switch Blayde ๐Ÿšซ

@Grey Wolf

I wouldn't have started posting if it wasn't 'done' to my basic satisfaction; that's not good for readers.

It's also not good for authors. Since I don't do a detailed outline, I often have to go back to make changes in previous chapters to make later chapters work. Kind of hard to do when those chapters are posted.

Replies:   Grey Wolf
Grey Wolf ๐Ÿšซ

@Switch Blayde

Definitely. Mine would have 'worked'. They're better with changes I made pre-posting but couldn't after.

Keet ๐Ÿšซ

@Switch Blayde

1. Sometimes the whole story is written, but I do the final edit to a chapter right before posting it (only minor changes).

I'm almost certain you can update scheduled chapters before they are posted so that shouldn't be a problem

2. I determine when to post a chapter on the fly. Going in, I plan on posting a chapter a week on the same day of the week. But sometimes when I'm ready to post I decide to post two chapters instead of one. Sometimes I post on a different day of the week thinking I might find a new reader. Sometimes I post a chapter earlier than I had originally planned. That just happened with the novel I'm posting now. I had three chapters that were rather dark โ€” rape, abuse, etc. โ€” that didn't go over well with some readers. So I posted the next chapter earlier than expected as it's more representative of the novel as a whole.

That is different, you can't schedule that. As with everything, the exception confirms the rule.

The basic idea is that a reader must be able to rely on a 'official' marking that the story is complete and that can only be done if the full story is uploaded to SOL for (scheduled) posting. Following your no. 2 remark you could say it's complete in the story description but not 'officially' mark it as complete because you didn't upload the full story yet.

richardshagrin ๐Ÿšซ

@Keet

complete

com = with
("com- a prefix meaning "with," "together," "in association," and (with intensive force) "completely," occurring in loanwords from Latin (commit): used in the formation of compound words before b, p, m: combine; compare; commingle.")

"pleat
/plฤ“t/

noun
a double or multiple fold in a garment or other item made of cloth, held by stitching the top or side

Definitions from Oxford Languages"

So compleat means with a garment fold.

Grey Wolf ๐Ÿšซ

@Keet

I tend to agree - but SOL's tools for posting would need a boost, in that case.

My story goes 89 chapters, almost all of which will be posted separately. Queueing all that would be a minor nightmare. Then, if I wanted to, say, decide to put out chapter 43 as a bonus chapter, now I need to requeue 46 chapters.

If SOL had a tool that you could feed X chapters into and say "post these M-8am/W-8am/F-8pm/Sat-8pm every week until done" and could also say "ok, pull the next off the queue and post it X" and could also easily replace queued chapters with updated versions without breaking the whole thing, we'd be in business.

With the current situation, the temptation for most people would be to queue up several chapters 'properly' and dump a wall of text after that to claim 'completeness', knowing they would always cancel the wall-of-text. What really is the point of that? And, are moderators going to vet the giant blob-of-chapters as to whether it meets a requirement for 'completeness'?

In the end, the reader really has to rely on the author's statement that the story is complete.

Replies:   Ernest Bywater
Ernest Bywater ๐Ÿšซ
Updated:

@Grey Wolf

If SOL had a tool that you could feed X chapters into and say "post these M-8am/W-8am/F-8pm/Sat-8pm every week until done" and could also say "ok, pull the next off the queue and post it X" and could also easily replace queued chapters with updated versions without breaking the whole thing, we'd be in business.

last year Lazeez started a system where you can upload a single file with multiple chapters with code (spaces added to stop it running). In his post about it Lazeeze said:

So you can submit a serial story and have chapters posted at defined dates in one shot.

there is now a { date } tag for chapters or relative date { date :+3a } for 8AM release after three days, or { date :+5p } for 8PM release after 5 days. How to use it:

Under the chapter title put the tag like so:

< p > { p } Chapter xx < / p >

< p > { date: 2019-10-20a } < / p > or < p >{ date:+1a } < / p >

That makes the chapter appears on the site on the 20th of October, 2019 at 8am.

< p > { date :2019-11-10p } < /p > or < p > {date :+2a } < /p >

That makes the chapter appears on the site on the 10th of November, 2019 at 8pm.

You can schedule multiple chapters to show up at the same time, but each scheduled chapter must contain a tag.

Limitations:

1 - Works only on whole story submissions. The timing script will mark a story completed when it runs out of scheduled chapters.

2 - First chapter can't be scheduled. You schedule the first posting with the wizard's current scheduler.

3 - Format is rigid. No spaces inside tag. Any syntax error makes the system ignore tag and chapter end up on the site on the initial posting and the tag remains in the text.

4 - Dates earlier than processing time are ignored. If you schedule your story to post on the 20th of October and chapter 2's schedule is for the 18th, the tag is removed and the chapter is posted with chapter 1.

The number of days in the tag is the number of days after the previous post. So:

chapter 1

chapter 2

{ date : +3a }

chapter 3

{ date :+3a }

Chapter 3 posts 6 days after chapter 1.

...........

If you use the +1 option then wish to amend the schedule at any point you need only change the date information of the first chapter affected by the revised date to a specific date and let the rest go with the rotation you already set.

Edit to add: I forgot to mention that the code I provided above is used when submitting the file in HTML, when submitting in Tagged Text don't use the html code of < p > < / p > listed above.

Replies:   Keet  Grey Wolf
Keet ๐Ÿšซ

@Ernest Bywater

That is indeed a pretty complex system but it does give the author a very flexible way for scheduling. I think a system with fixed intervals would have been much simpler for authors. Without the need to enter a code at the start of each chapter. For example [startdate] - Tue[1] and Thu[1] (before Chapter 1 or in the submit wizard)
or
[startdate] - Wed[2]

The startdate could default to when the story is submitted or a given date by the author. [1] or [x] are the number of chapters to release if that interval is released. With a default [1] you wouldn't have to enter it.
This way the most simplest form for scheduling could be
[Tue,Thu]
which would mean that from the date the story is submitted every Tue and Thu a chapter will be released on SOL. Much easier to code and you can submit edited chapters as much as you want because they wouldn't have to contain the scheduling codes. You could even insert chapters because they would just shift the queue of chapters to post yet.

Grey Wolf ๐Ÿšซ

@Ernest Bywater

Thanks for posting this! Is this documented somewhere (other than in the forums)? i.e. am I the idiot for not knowing this existed?

I may try to make use of this. I'm still not sure I like it, given the amount of work it'd be to update a posting, but, maybe?

Replies:   Ernest Bywater
Ernest Bywater ๐Ÿšซ

@Grey Wolf

I agree in that I think it should be mentioned in the Text Formatting Page as well as the Author Help and FAQ Page. However, to the best of my knowledge, it's only mentioned in the forums in the post where Lazeez announced it. Maybe seeing this post may get him to add it to them.

Back to Top

 

WARNING! ADULT CONTENT...

Storiesonline is for adult entertainment only. By accessing this site you declare that you are of legal age and that you agree with our Terms of Service and Privacy Policy.


Log In