Unique stories are supposed to appear in only one place (and no links in stories; the site eats them). I’m not sure if that applies to “teaser” chapters of sequels, but I did announce Radiance in advance, so hopefully people interested in it will know to look.
If you modify the end of Luminosity to mention the sequel is available, then post a new blank chapter to Luminosity, then delete that blank chapter… you haven’t broken the rules (or at least, nobody is going to notice that you broke the rules), people still get the notification, and the modification to mention the sequel gets noticed.
I did get an alert for Chapter 58 (nonexistent by the time I
followed the link). Did you put a mention of Radiance in
the FF copy of Chapter 57?
I don’t see it there (maybe a caching issue).
More importantly (I think), I got an alert for
“[FF New Story] Twilight: Radiance, by Alicorn24”
yesterday. Edit: I realized that this is because I have an author alert for you, and the problem you’re trying to solve is notifying people who have a story alert for Luminosity.
No, I didn’t edit chapter 57. The problem is that I can’t directly edit an existing chapter: I’d have to upload a new document, edit that, and replace the chapter with it. But since I re-did the chapter numbering, I don’t have the content that was 57 in its own file anymore. As with every other deficiency of the ff.net version, it’s just too annoying to fix.
Well, unless they can see the future, they couldn’t have known you were going to delete it before you did :P. If there is some delay baked in, and it cares about whether the chapter is still there, all it takes is a little experimentation (or data-gathering on how long it takes to get an alert from when the chapter is posted) to find the length of time you need to leave it up for. That said, I am unfortunately not signed up for the alerts, so I can’t confirm for you whether it worked.
Unique stories are supposed to appear in only one place (and no links in stories; the site eats them). I’m not sure if that applies to “teaser” chapters of sequels, but I did announce Radiance in advance, so hopefully people interested in it will know to look.
If you modify the end of Luminosity to mention the sequel is available, then post a new blank chapter to Luminosity, then delete that blank chapter… you haven’t broken the rules (or at least, nobody is going to notice that you broke the rules), people still get the notification, and the modification to mention the sequel gets noticed.
Tried this, but I’m not sure if the alert will go out for a chapter I deleted immediately. Somebody signed up for the alerts please let me know.
I did get an alert for Chapter 58 (nonexistent by the time I followed the link). Did you put a mention of Radiance in the FF copy of Chapter 57? I don’t see it there (maybe a caching issue).
More importantly (I think), I got an alert for “[FF New Story] Twilight: Radiance, by Alicorn24” yesterday. Edit: I realized that this is because I have an author alert for you, and the problem you’re trying to solve is notifying people who have a story alert for Luminosity.
By the way, though I’m signed up for the fanfiction.net alerts, I’m following your recommendation to read the story at http://luminous.elcenia.com/.
No, I didn’t edit chapter 57. The problem is that I can’t directly edit an existing chapter: I’d have to upload a new document, edit that, and replace the chapter with it. But since I re-did the chapter numbering, I don’t have the content that was 57 in its own file anymore. As with every other deficiency of the ff.net version, it’s just too annoying to fix.
Well, unless they can see the future, they couldn’t have known you were going to delete it before you did :P. If there is some delay baked in, and it cares about whether the chapter is still there, all it takes is a little experimentation (or data-gathering on how long it takes to get an alert from when the chapter is posted) to find the length of time you need to leave it up for. That said, I am unfortunately not signed up for the alerts, so I can’t confirm for you whether it worked.