As of around 17th around 7:53 AM on May 18th, I noticed a sudden regression in story formatting behavior in ChatGPT. This affects both Markdown rendering and story structure consistency, and it appears to have started suddenly around 17th midnight.
First is that it is that the Markdown Header Not Rendering Properly. Before, when I asked for a large title at the beginning of a story or chapter (e.g., # Chapter 1: The Beginning), ChatGPT rendered it correctly using Markdown (large font, H1 header style).
Now, it simply outputs the raw Markdown syntax, like:
Embittered Days
Chapter 1: Embittered Memories
[# Embittered Days].
[ ### Chapter 1: Embittered Memories]
…The tag right next to them included without rendering it as a large header. This breaks the visual structure of multi-chapter stories and was never an issue before May 17-18.
The second issue is the Loss of Chapter Formatting Consistency. I explicitly instruct that there should be a separator line or space between the chapter title and the content, for example:
Chapter 1: Embittered Memories
With the Story begins here after that line. Back then, the chatbot did this voluntarily without any input, and it followed the structure across chapters. Now, after the first chapter, the separator line is ignored or omitted altogether in following chapters, even AFTER I specifically request it. And not only that, the narrative took an completely broken and jarring narrative, often disregarding an entire segment in the story prompt, thus invalidated all of my effort I put in refining it.
Both issues began simultaneously and have never occurred before in this way, at least for me. I often use ChatGPT for writing long-form structured content for fun. These formatting tools—Markdown headers, separator lines, structural consistency—made it enjoyable. Their absence—and the long term consequences that followed them, such as breaking the narrative, broken segments, paragraphs that loses all of its subtlety and personalities, details and creativity significantly impacts my experience. And not in a good way.
Please investigate this issue. It occurred roughly around May 17-18 in May. Or even 16-18. Please, I’m getting desperate and honestly exhausted trying to figure this out on my own.