On accident, I discovered that the site won't let you edit a chapter if its parent chapter is linked to it. For example, if Chapter 1.1 is linked to Chapter 2.1, then you can't edit Chapter 2.1 until you unlink Chapter 1.1
I've been getting a bunch of "This plugin isn't supported" messages when I try to follow links or open the sidebar on my phone. Chrome version 51.0.2704.81 Android version 5.1.1 I am not getting these errors on my PC using Chrome. It happens every time I hit a link. Opening a new tab bypasses the problem entirely.
Looks better, I reloaded and can navigate links and menu links without seeing the gray screen from the unsupported plug-in message.
When you create a link from a chapter that already has text, the system happily overwrites your story with the link. I think the site should generate a warning if the chapter text is not empty.
Not sure this is a bug, but at least it's a question for me: How are the "Top chapters" calculated? I assumed they are a ranking of the chapters with the most "likes". At the moment, #1 has 30 likes and #10 has 21 likes. One of my chapters recently gained a lot of likes, which should put it into the top10 list, but it does not show up there. The chapter is this one here: https://chyoa.com/chapter/Use-the-schoolgirl's-outfit.255217 Now, as I wrote here: http://forum.chyoa.com/threads/feedback-from-the-readers.618/ one of the reasons why the chapter probably got so many likes might be the fact that I added a friendly reminder at the end. I can see why someone could call this some sort of "illegal advantage" for a list like that. I did not put the reminder there to make it into the list. I put it there as what it is: A reminder to encourage readers to be more generous with likes in general. Anyhow, if someone tells me: "The figure here is distorted, that's why the chapter is not ranked", I'd understand. I don't believe that's the case here, though, because that would mean the chapter did climb the ladder, was hand checked and then deleted from the list by hand. I guess the admins have more important work to do. So I assume the chapter is not listed, because somehow the algorithm does not work? Or is it not about likes after all, but about something else? Views?
The top chapters are sorted by their weighted ratings. More here: http://forum.chyoa.com/threads/top-sex-stories.418/#post-7544 In addition top chapters are cached for seven days. That should be the reason why your chapter isn't listed yet. Your encouragement is totally fine
It did turn up today, so the seven day cache was indeed the reason. What's the reason for this anyway?
I seem to be having a few issues with variables. 1. I have trouble setting variables to zero. I can create a new variable with the value 0, but when I try to set the value of an already-existing variable to 0, it has no effect. For example, if I create the variable "coins" and set its original value to 0. Then the score sidebar will display "Coins 0". As expected. But if I create the variable "coins" with the original value of 90. Then, on the next page, set "coins = 0". The sidebar still displays "Coins 90". This issue seems to affect both numerical and percentage variables. 2. There's a slight inconsistency with numerical variables. Numerical variables can take negative values through subtraction. For example, if we create the variable "health" with original value "20". Then subtracting 30 health will give: "health -10". However, authors cannot create negative, numerical variables using the equals button. If we try to do so, we get the warning: "Please select a value that is no less than 0."
Has the algorithm for new stories displayed on the front page changed? They used to be ranked by activity: Write a new chapter and you are back top, no? Now it seems simply structured by date of first publication. I prefer the activity one: If you dedicate some time and effort to your new story, you get some important visibility for a rake-off.
I can verify that this is still an issue. On the follow up target chapter, the "Answer" field to name the chapter is missing, as long as the chapter directly preceding it has been turned into a link. When you try to edit this target chapter, it gives you an error message: "The title field is required." I stumbled upon the issue, when i wanted to set certain variables, but not directly on the target chapter itself, but on the one preceding it. I did this, so i have the option to link to the target chapter from another location as well, without messing up the variables. You can work around this issue by temporarily deleting the link, edit the target chapter, and enabling the link again. But if its not too much work, of course it would be great if that workaround wouldn't be needed.
This is a known issue. You can use two score changes as workaround: health = 0 health - 10 Thanks for reporting this issue. As a temporary workaround, you could do the same as described above. coins = 1 coins - 1
I just found a problem with scores and backtracking throughout a game. In most cases this works as intended, and the site simply deducts from your score as long as you're using the "previous chapter" button. However, in some cases it doesn't do this, and the score system goes out of hand as it continues climbing in numbers. (For example: You go through a number of chapters, constantly adding +1 coin for every chapter, until you reach the intended 20. Then you backtrack, to take another route, and suddenly find yourself sitting at 30 coins, when the maximum possible should only ever be 20, no matter what route you take.) I'm not entirely certain yet, but I believe it may have something to do with extensive use of linking between chapters. This seems to work just fine otherwise, but after you pass backwards through at least a pair of links, it seems like the "coins" stop counting backwards. Hope I'm making some sense here. All I can tell for sure is that something messed up a bit with my story "Girls of Jack". ; )
I just wanted to add, that i posted a similar description of this issue as well: http://forum.chyoa.com/threads/post-suggestions-here.7/page-13#post-9947 So i obviously agree that this is an issue, and hope that it can be mitigated or fixed somehow in the future ;-)