Underscores appear to be broken: https://forum.chyoa.com/threads/rich-editor-errors.6301/, the <u> tags get escaped. I've confirmed it also happens when you use ____Markdown____
so im trying to comment on a story in chyoa and for some reason its saying i cant post spam which doesnt make any sense since im not spamming
This sometimes happens when you continue writing directly after a period (like done.it was...), because then it thinks that "done.it" is a domain.
I'm not sure what its considering spam. I was able to post the second half of my comment but not the first half, I'm just discussing the characters in the story so what does it consider spam? there are no periods with a word right after
sure the problematic part is "So there's Layla, Lucifrena, Moira, potentially Fianna, and now Lyndell as potential new haremettes. I definitely want Moira and Lyndell in the harem, Lucifrena would be interesting to have so that the whole Christ being real part can be a sub plot and Layla would be a direct connection to the fae world; Momo is technically a connection but she didn't start out as fae; I am super curious about how the elemental islands did, and how the fae did, and I'm curious about where Tilgun is" thats the part it wont let me post minus the quotation marks as well, and I am trying to post it to chapter 1895 of the Gamer series
Thanks! It was because of "ow ly". A spammer used that in the past and we blocked that phrase. It's the ow.ly domain without the dot. I disabled this rule and you can now post the comment.
Collapsing on the storymap has issues. If you collapse all, then expand just a level or 2, as soon as you hit a load, it starts the whole story over in fully expanded format from the first level. This also means anything on the level you were looking at that didn't fit on the first screen is all the way off the bottom. Basically, whenever a load happens, it seems that it always tries to load everything in full expansion, and that it can't track the collapsed levels before the load, so always tries to start from the beginning of the level. Additionally, if you collapse, scroll, expand, re-collapse... all kinds of weird loading errors start happening, like the same chapters showing multiple times, chapters seeming to load in random orders, etc. For an example, try collapsing all on the story map for Sexual Privilege (https://chyoa.com/story/Sexual-Privilege.13397), open level 2, then without doing anything else, scroll downward (there are over 80 level 2 chapters for this story, but on collapse all then opening only level 2, only 25 fit on the first screen, so you can't even get them all before this happens).
The map should always load 1000 or so chapters and add them at the bottom of the list. The added structure is fully expanded. If you expand the latest collapsed chapter and collapse it, the additional structure should collapse as well. I don't get it... If you click "collapse all" and then open level 2, you will see 26 second-level chapters. If you scroll down to the end, it will load the next 1000 chapters. (This only works if it is actually possible to scroll a bit. If the height of your browser/device is too high, it doesn't load the additional chapters.) If you click "collapse all" and then open level 2, you will see 25 additional second-level chapters. The next time, you get another 25 additional second-level chapters. The next time, you get another 56 additional second-level chapters. The next time, you get another 80 additional second-level chapters. The numbering restarts with each batch, so you get 1 to 26, 1 to 25, 1 to 25, 1 to 56, and 1 to 80.
If you collapse all, open to level 2, and scroll without doing anything else, this is what happens. 2.26 is the end of the first screen loaded, and then it throws some random chapters, and then starts over with fully expanded from a misnumbered 2.1 as you scroll down and do nothing else. You never get the rest of level 2 as collapsed blocks, and everything after the first screen worth is fully expanded and numbered incorrectly.
They aren't really random. The last chapter in the collapsed part is The child chapter of that is The structure is identical to when you open the story map and scroll all the way down until everything is loaded. So it is "only" a mixed state of collapsing/expanding. If you expand all -> collapse all -> open level 2, all (loaded) level 2 chapters will be shown. That's a known issue. It might also happen in between. E.g. if there was a sibling chapter above the shown 6.1 that belongs to the first batch, the chapter "Try something small" from the second batch would still be numbered 6.1. I think the numbering is done backend and as it only gets 1000 chapters from the database, it might not be known what numbers are before that, especially beyond chapter level 2. Maybe that could be fixed when done frontend, so that it "remembers" the last number of each level and then continues from there. The other thing might need to be fixed on frontend as well or it would be necessary to send the current status of the story map to backend.
We go from 2.26 'Anyone - coincidence ring - favor" to 6.1 'try something small." That is not in the first branch below that header, and it's not clear why it picks up at level 6 in that particular branch. It then shows the entire rest of the subbranch, then resumes loading the whole story at the next level 2 branch fully expanded again, and continues from there fully expanded. As it stands, this effectively means for any longer story, 'collapse all' is functionally broken, and that anyone encountering this issue thinks everything is behaving randomly. The point of 'collapse all' would to be able to see all branches at each level and only expand what you want, which it apparently cannot do because of the odd loading behavior. Exaneed is forced in a very confusing way that certainly appears as a bug to the user. I remember why the sequential loading was originally put in, but I think it might be creating more issues than it fixes at this point. Things have gotten far longer and more involved than they ever did on the previous website. If the storymap were collapsed by default, there is only the need to load in further levels as people expand, which could reduce stress on the server and avoid having it bogged down by excessive state data. I don't know about other users, but I usually just infinite scroll down to force full loading immediately anyway most of the time, so the partial load isn't really saying the server that much. Having everything start collapsed could address the loading issues; the server would only need to load things as a person explicitly expands them. There would need to be some markers for how deep each collapsed branch is, which branches have new things, etc. Even so, I think it would end up being more usable and more performant than the partial loading, and would avoid unexpected behavior as things get longer and deeper.
I don't think there's a need to overhaul the whole mechanism. There are two minor issues, and both can be solved pretty easily: For each newly loaded chapter, check if its parent is collapsed, and if so, add it hidden. And check how many children its parent already has, and set the chapter number accordingly: if the parent chapter is 2.1, and it already has 3 children, then this chapter should be 3.4.