Actions

Work Header

DDLC and DDLC Plus: Bugs, Glitches and Exploits for Dummies

Chapter Text

and

BUGS, GLITCHES AND EXPLOITS FOR DUMMIES

(it's 2020 now and lo-fi ASCII art is so out of fashion, trust me)

[0000] DECLARATION OF PURPOSE

Alright, before we even properly begin this document, some things need to be said. And by "some things", I could very well mean what others consider to be a lot of things. You just don't know unless you've gone through the entirety of things.

First of all, a few words for the sort of person who believes they can just barge into this document, search for keywords like "walkthrough" or "all achievements" and leave if they haven't found what they're looking for. I want this sort of person to know that DDLC hacking is not an endeavor to be taken lightly by any means. At its lightest, it is a hobby that, if pursued, will consume quite a lot of time and effort, and at its heaviest, it's comparable to a full-time, very cerebral job.

This document is the best document that I can possibly construct that can guide a person into this endeavor, with the exception of certain concessions that I cannot discuss right now. Therefore, you can absolutely expect it to dump more technical knowledge on you, all at once, than required by the most demanding professions, and given the amount of stuff discovered by DDLC hackers, if there isn't an undergrad, graduate and PhD DDLC course before the decade is out, I will promptly print the entire hefty document out and eat it all, live on Twitch.

This doesn't mean that I will not try my best to cater to this sort of person, as much as I can. However, this does mean that my help will be very limited in this regard.

[0001] ADDRESSING THE SORT OF PERSON WHO SEARCHES FOR "WALKTHROUGH"

Due to the very nature of the game, which the rest of this document expounds upon, it is honestly quite impossible to write a detailed walkthrough of DDLC that will account for your specific experience and hold your specific hand. Asking for that, really, would be equivalent to asking how to ask a girl out in real life, and as we all romance-deprived loners living in their parents' basements know, a lot of factors come into play, and for the most part, holding hands isn't going to do much here. Some, I think, gather into this "incel" group which tries to define why they, in and of themselves, are "forever alone", but I don't even think that is a leading cause.

Luckily, while one cannot guide you through the entirety of what appears to have been crammed into a single week or two of in-universe material, with all the intricate options and routes, into a concise walkthrough (or a walkthrough of any sorts, really), one can tell you, almost guaranteed, that there aren't even that many choices to make in the long run, and from there, picking the right choice is mostly a matter of common sense.

TL;DR: Don't be a dick to the girls, try and stay faithful to just one of them and roll a d120 for the absence of glitches (yeah, they actually sell d120, and the probability of a glitchless run does seem to be in the rough ballpark of 119 to 1).

While we're in the proverbial TL;DR section, which I suppose you are reading with care, I should also mention that it is quite impossible to spoil this game due to how it's generated, so while this is optional, absolutely do take notes on your first playthrough. Better yet, before you start playing, download OBS and record your entire reaction - just remember to turn the recording off... actually, nevermind, I don't think I can disclose the moment without spoilers and I don't think recording your entire DDLC experience with OBS is a good idea anymore. Still, if you do stick around and become One of Us, invariably, you're going to treasure the notes you made.

[0002] ADDRESSING THE SORT OF PERSON WHO SEARCHES FOR "ALL ACHIEVEMENTS"

DDLC, the free game, does not have any achievements. Hooray; if you've completed the game once, and if you're not interested in becoming a DDLC hacker, you're done with the game forever. Go install some mods or something. I even have a few recommendations for you; the chapter numbers are TODO.

DDLC Plus, the paid game, does have quite a few achievements, including one which requires you to discover all the little secrets that it has. Okay, that's impossible in every sense of the word, but there is a checklist of secrets that need to be discovered, and it gets quite long. A guide for all achievements is forthcoming, and the chapter number is TODO.

[0009] A TECHNOLOGY NOOB'S (AND CONSOLE PLAYER'S) GUIDE TO DDLC

The last sort of person who needs to be addressed is the sort who does want to get into DDLC hacking in earnest, but finds themself either a) intimidated by technology more complicated than opening Chrome or Steam on Windows or b) limited to just mobile devices and a game console with DDLC Plus onboard. And believe me, though this surprises many, that the latter category comprises a significant portion of the modern population, and is only growing every single day.

Luckily, there is knowledge, that DDLC hackers have gathered, that is not useful to someone perusing the game casually, but that is useful to an aspiring DDLC hacker limited to either category I just mentioned. The relevant chapter numbers for such a person are TODO.

That's it. Now that I have addressed those looking for easy answers, they can - and honestly, should - leave now.

cue the audience leaving, Downfall parody style, just before the part where Hitler blows up

[0010] RECOMMENDATIONS FOR THE ONES THAT ARE STILL HERE

Well, I suppose, this is where I blow up. However, unlike our favorite dictator, I won't blow up in anger per se; instead, I will blow up with information, since, as mentioned before, there is just Too Much to unpack, as far as DDLC goes.

This is where you simultaneously don't need to worry and do need to worry. Technical knowledge needed to explain the game will be provided, in small chunks, from the beginning of this document to the end. However, there is a lot of stuff to unpack, and getting all flowery purple prose-y simply isn't going to serve us any good, and pretty soon, you might - nay, will - feel like shit is being thrown at you too fast. In that case, the simple advice I can give is to pause the reading, rewind a bit to the technical terms that you failed to understand, re-read their descriptions, perhaps take to a classroom with a notebook (and yes, there does seem to be a dummied-out notebook mode in the game for... I think this is too advanced stuff for now) and really study until you get an A+ on every single subject.

As far as knowledge of actual school subjects goes, I'm tempted to say that you'll need to be well-versed in computer programming, but odds are, your usual programming knowledge isn't going to do you any good here, since the vast majority of DDLC is coded in a form of script that was literally created by the same people as the game, from scratch, for the explicit purpose of this project, and just so happens to be unlike any sort of well-known or even esoteric programming or scripting language, which is kind of a big deal for anyone looking to crack the game open like an oversized piñata. Still; if I don't clarify any mainstream programming terms, you are free to hit up any of the multitude of "learn programming" sites and go through them. (If you are wondering which programming language to pick, just go for Python. Not even going into how it's an "easy" high-level programming language that you can easily get into, the "outer shell" of DDLC, the free game, so to say is actually written in Ren'Py, which is a Python library for visual novels and does, by default, allow for inline Python, allowing you to do some basic modding of DDLC if you choose to do so.)

Other than that, another TL;DR (don't worry, we're going to run out of TL;DRable info very soon) is simply: pay attention, brush up on your programming skills and remember that I'm presenting information in a strictly ordered, noob-friendly manner.

Still with me? Still ready to invest upwards of 10,000 hours, which some people seem to have declared the limit at which you can call DDLC your profession and expertise? Well, let's go.

[0020] DOCUMENT READING OPTIONS

This document is presented on two websites, simultaneously:

The content on both websites should be exactly the same, and if you find differences, you are absolutely free to complain at me - however, you'll have to do it at AO3, since my website doesn't allow for comments. Not yet, anyway. I'm picturing a system where you can highlight a paragraph and comment at it, similar to Google Docs, but right now, I wanna remain focused on my primary goal: introducing you to DDLC hacking.

However, in most other respects, the version on my own website, which I often refer to as selfhost, is superior to AO3. On selfhost, I can maintain the precise formatting that I need, including fonts, reading features, etc. In addition, selfhost is specifically designed to be entirely contained with a single file, which can be easily downloaded if you want an offline version of this document, for whatever reason.

With that out of the way, I hope you will consider which website is the best for your needs.

[0030] DOCUMENT STRUCTURE CUSTOMS

Yeah, you might have batted an eye at my strange terminology: chapter numbers. What is going on? Have we already reached the "hard" part of DDLC hacking?

Not really, and let me tell you why. If you would notice from the experience you've had with the document so far, you should see that the chapter headings all look like [**] CHAPTER TITLE. This is just something that I adapted from the writing customs of existing walkthroughs from the distant, distant era of the 2000s, but in addition, there's a practical reason: with this system, the former part, the one in brackets, should be easily searched with Ctrl+F, should you feel the need to look up a cross-reference - or go back to the part of the text that prompted you to look up the cross-reference. And thus, I call the former part "chapter number" and the latter part "chapter name". There is also a rhyme and reason to the chapter numbers I pick, as well as a way to pronounce them, but that is extra, mostly irrelevant reading material, available at [A003] TRIVIA STREAM: HOW TO READ THE CHAPTER NUMBERS OF THIS DOCUMENT.

Alternatively, thanks to the magic of JavaScript (more programming languages may or may not have been involved), the version of the document on my website has a dynamically updating table of contents, allowing you to click through between the chapter and its TOC listing. (That is, unless you have enough screen real estate and the TOC just chills there, to the left, forever.) Another cool thing that this version allows for is dark mode: if you've noticed the little sun doodad on the top right, you can click it and it'll turn into a moon doodad, as well as turn on dark mode, and then you can click it, again and again, to your heart's content.

However, even though the AO3 version of this document might be a little less technologically advanced (due to reasons that should honestly be obvious), AO3, itself, is plenty advanced as a service. You could probably just find a dark mode sitewide skin somewhere, and a complete TOC with real chapter headings is going to require a slightly different hack, that I discovered while writing a similar-ish essay document: presuming you're reading this on somewhere that has the "Inspect Element" mode, enter it and just find a way to enter this to a stylesheet (be sure to "View Entire Work" before executing this):

p, ul, ol, blockquote, div.preface, .meta, #header, #feedback, .landmark {display: none;}
#main {padding-bottom: 0;}

Voilà. All the body text is now gone, and what remains is the headings, providing a table of contents.

Also, briefly on the formatting I use. Code is for the sorts of terms that are used in their common meanings in programming, and therefore, can be perused at your own pace on Wikipedia or elsewhere, while bold italic is for the sorts of terms unique to DDLC and DDLC hacking, which I will properly explain in due time - and if I haven't properly explained them, you are absolutely free to complain at me.

That being said, there is one thing that you still need to know about this document's current structure - or lack thereof.

[0039] NOTICE: THIS IS (CURRENTLY) A WORK IN PROGRESS

To say that DDLC Plus caught me off-guard is an understatement. In addition, to say that this is a completely new frontier for DDLC hackers is also an understatement. Therefore, this document, intended to be a complete guide to both DDLC and DDLC Plus, is very much a moving target, especially in its Plus department. Furthermore, it's not like I can just keep the DDLC part of it unedited, as some new discoveries do affect the original game.

Therefore, this and the following updates, from version 1.51 to a future 2.00, are intended to create a structure that can accommodate the Plus content. Until then, groundbreaking discoveries simply can't be dealt with. No, not even in the non-chron blog.

Thank you for your understanding and patience.

Originally written material for version 1 of this document is exclusive to selfhost, and is subject to being deleted as it's being replaced with the aforementioned new structure.

Other than that, and with everything else out of the way, I have not one, but two ever-important things I need to tell you, especially in the modern day, and neither of them can really be treated lightheartedly. For those parts, writer personality is simply not welcome.

We'll meet up again at [0100] HISTORICAL NOTE: THE DDLC HACKING COMMUNITY.

Chapter Text

[0040] THE OVERARCHING CONTENT WARNING

This document touches upon Doki Doki Literature Club!, a video game with a relatively high rating as granted by various rating boards (ESRB: Mature 17+, PEGI: 18, USK: 18). A notice pertaining to all the content warnings applying to DDLC is maintained by Team Salvato over at http://ddlc.moe/warning.html.

Everything that does or potentially can appear in a DDLC playthrough is documented here, without ever shying away from sensitive topics. To this end, and since warnings for content that is not a verbatim description of DDLC content may be needed, a separate list, including spoilers for DDLC, is maintained at [CW00] THE FULL, ALPHABETIZED LIST OF CONTENT WARNINGS, as well as in form of additional tags on Archive of Our Own. In addition, chapters with potentially sensitive subject matters will have a header preceding them, as follows:

[0041] AN EXAMPLE CHAPTER WITH A CONTENT WARNING

Content warning: people being wrong on the Internet

[This is where the chapter's text would go...]

[0050] CREDITS AND COPYRIGHT

Doki Doki Literature Club! is © 2017 Team Salvato. Doki Doki Literature Club Plus! is © 2021 Team Salvato and Serenity Forge. This document is in no way affiliated with Team Salvato or Serenity Forge, having been created entirely through the effort of a multitude of fans across varying fields of expertise, and is believed to be compliant with the Team Salvato IP guidelines. For further details on using the intellectual property, as well as any others introduced by Team Salvato, please consult the latest version of the Team Salvato IP guidelines over at http://teamsalvato.com/ip-guidelines.

This document is designed to be read after completing the main campaign of either game; the two are believed to be equivalent. For DDLC, this is considered to be the entire game, and for DDLC Plus, this is considered to be the emulated game available by selecting "DDLC" on the system menu. The main campaign is completed with a credits sequence. DDLC can be freely downloaded and played over at https://ddlc.moe. DDLC Plus can be purchased in digital form for US$15, or in physical form for US$30, on various storefronts.

This document highly concerns itself with reverse engineering of the games. Said reverse engineering is believed to have been conducted entirely using clean-room techniques, and therefore, not infringe on any copyright or patents. Throughout its lifetime, the document will closely monitor the sources of the claims that it makes, and if any of them appears to directly violate copyright or patents, it will be promptly removed.

This document also highly concerns itself with speculation about future games by Team Salvato. These games are not yet known by their official titles, and the titles used in reporting are only speculative.

The document itself, for the most part, is © 2020-whenever me, CreativityTheEmotion, and does its best to not rely on any external writing exclusively, except when necessary, in which case explicit links are provided. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [L000] GNU FREE DOCUMENTATION LICENSE.

In addition to allowed expandability upon the document in your own writeups, subject to the license above, content may be freely contributed, adding to this document, by any and all aspiring contributors who aren't snobbish assholes looking to keep awesome DDLC insider knowledge to themselves. Whenever content from external sources is contributed, it will be clearly labeled as follows:

[0051] AN EXAMPLE GUEST CHAPTER

Contributed by [your username can be here!] on [date in both Gregorian and DDLC hacker calendars], either © or explicitly released through a libre license (either the GNU FDL or a compatible license, such as Creative Commons).

[This is where your guest chapter's text would go...]

Chapter Text

[0060] VERSION HISTORY

Version 1.54 - September 22, 2022 (P0449) 10:50 UTC

  • Happy birthday, Monika (again)
    • In with the new: [0200], [020G], [0210] and [0220]
    • Out with the old: [old:0200] BASIC TECHNICAL INFO and [old:0210] DAN SALVATO: A BRIEF HISTORY

Version 1.53 - September 22, 2021 (P0084) 19:25 UTC

  • Happy birthday, Monika
    • In with the new: [0100], [0110], [0120], [0130]
    • Out with the old: [old:0100], [old:0110] and [old:0120]

Version 1.52 - July 14, 2021 (P0014) 20:45 UTC

  • Re-converted the original version history back to its Markdown source

Version 1.51 - July 11, 2021 (P0011) 23:25 UTC

  • The beginning of sweeping changes
    • In with the new: [0000], [0001], [0002], [0009], [0010], [0020], [0030], [0040] and [0041]
    • Out with the old: [old:0000], [old:0001] and [old:0010]
  • I liked it when I didn't have to write pointless version update summaries, thank you very much
    • Updated: [0039] (formerly [0049]) NOTICE: THIS IS (CURRENTLY) A WORK IN PROGRESS and [0050] CREDITS AND COPYRIGHT

Version 1.50 - June 30, 2021 (P0000) 16:00 UTC

  • It's a reboot of the document, for DDLC Plus
    • New: [0049] NOTICE: THIS IS (CURRENTLY) A WORK IN PROGRESS and [0097] VERSION HISTORY ARCHIVE: 1.13 INTERIM
    • Updated: [0050] CREDITS AND COPYRIGHT
  • Renumbering every chapter number, except some maintenance chapters, to indicate that the content structure may and will change to accommodate Plus content
    • Updated: way too many to even list

Chapter Text

[0097] VERSION HISTORY ARCHIVE: 1.13 INTERIM

Interim versions consist solely of new non-chron blog entries, and therefore, as the main body of the document (including previous non-chron blog entries) remains unmodified, do not include additional release notes.

Version 1.13 interim 12 - June 18, 2021 (D1365) 17:15 UTC

  • New: [A029] DOKI DOKI LITERATURE CLUB PLUS! - GAMEPLAY AND MISCELLANY

Version 1.13 interim 11 - June 13, 2021 (D1360) 17:35 UTC

  • New: [A028] DOKI DOKI LITERATURE CLUB PLUS! - MUSICIANS, INTERNATIONALI(Z/S)ATION AND MODDING

Version 1.13 interim 10 - June 12, 2021 (D1359) 15:10 UTC

  • New: [A027] DOKI DOKI LITERATURE CLUB PLUS! - OFFICIAL AND SPECULATIVE DETAILS

Version 1.13 interim 9 - April 9, 2021 (D1295) 18:40 UTC

  • New: [A026] BUT HOW DOES DDLC (AND THE MAINSTREAM FANDOM) REALLY PICK YOUR DD AND DD2?

Version 1.13 interim 8 - April 3, 2021 (D1289) 21:00 UTC

  • New: [A025] BUT HOW DOES DDLC REALLY TREAT YOUR SELF-INSERT'S NAME IN A SENTENCE?

Version 1.13 interim 7 - February 14, 2021 (D1241) 13:00 UTC

  • New: [A024] BLUE SKIES - SAYORI ROUTE: IF YOU RECONNECT AFTER A WHILE, YOU'RE MEANT TO BE

Version 1.13 interim 6 - December 11, 2020 (D1176) 19:00 UTC

  • New: [A023] REGARDING THE FILES THAT DDLC LEAVES ON YOUR COMPUTER

Version 1.13 interim 5 - October 9, 2020 (D1113) 19:05 UTC

  • New: [A022] REGARDING MY EXTENDED ABSENCE AND FANDOM NEWS - PART 1

Version 1.13 interim 4 - September 25, 2020 (D1099) 19:35 UTC

  • New: [A021] IMPLICATIONS OF ALTERING DDLC'S TRAINING SET - PART 2: DISCOVERIES BY HACKERVERSE

Version 1.13 interim 3 - September 18, 2020 (D1092) 20:10 UTC

  • New: [A020] IMPLICATIONS OF ALTERING DDLC'S TRAINING SET - PART 1: DISCOVERIES BY ME

Version 1.13 interim 2 - September 11, 2020 (D1085) 19:30 UTC

  • New: [A019] GPT-2, GPT-3, PLAYING AROUND WITH THEM AND EVERYTHING IN BETWEEN

Version 1.13 interim 1 - September 4, 2020 (D1078) 17:30 UTC

  • New: [A018] A TOUR OF MY OWN, PERSONALIZED ACT 3 AND MONIKA AFTER STORY REPLACEMENT

Chapter Text

[0098] VERSION HISTORY ARCHIVE: 1.10 THROUGH 1.13

Version 1.13 - August 28, 2020 (D1071) 16:35 UTC

  • We're finally, bona fide, done (for version 1, that is)
    • New: [9Z99] THANKS FOR READING
    • Updated: [299D] A DIAGRAM OF THE PATHS AND ENDINGS SO FAR - VOL. 2
  • Very important licensing issues
    • New: [L000], [L100], [L101], [L102], [L103], [L104], [L105], [L106], [L107], [L108], [L109], [L110], [L111] and [L200]
    • Updated: [0050], [0051] and [A003]
  • All typos remaining in the document are henceforth to be regarded as intentional misspellings (until version 2 comes along)
    • Updated: [A016] MUSINGS ON THE PERFECT LANGUAGE MODEL, FEAT. SOMETHING DEFINITELY SUB-PAR
  • This is the version to back up if you're going offline

Version 1.12.20 - August 22, 2020 (D1065) 17:15 UTC

  • Prepare for trouble and make it double
    • New: [2308] ADDITIONAL BACKGROUNDS: THE REAL "POLISH" OF MAINSTREAMER MODS and [A017] TOPICS IN DEPTH - PART 4: THE BACKSTORY AND ORIGINS OF THE LITERATURE CLUB
  • You'd think that the fixing of errors would get slower as I approach the end of version 1, but it hasn't
    • Updated: [0200], [2024], [221R], [2305], [2520] and [A013]

Version 1.12.19 - August 14, 2020 (D1057) 19:55 UTC

  • Not the final update falling under the "version 1" umbrella
    • Updated: [020G] YOUR INTRODUCTORY GLOSSARY and [2306] JUST AN "INCONSEQUENTIAL" INCIDENT - PART 1: INTRODUCING MONIKA?

Version 1.12.18 - August 12, 2020 (D1055) 13:35 UTC

  • Sentience and Cognizance: clarifying and correcting incorrect usage; let's just say it's a consensus that arose in my comment section
    • Updated: [020G], [1100], [1300], [2140], [2151] and [2306]
  • Fixes not related to Sentience or Cognizance
    • Updated: [0210] DAN SALVATO: A BRIEF HISTORY

Version 1.12.17 - August 9, 2020 (D1052) 18:35 UTC

  • A little tool to keep you occupied while I'm gone, and just like my last one, it works great with copypastas (and also, I talk about natural language processing, but that's the less relevant part)
    • New: [A016] MUSINGS ON THE PERFECT LANGUAGE MODEL, FEAT. SOMETHING DEFINITELY SUB-PAR
    • Updated: [2210] ANOTHER WAY TO THINK ABOUT IT: THE GROWTH OF A WRITER and [221R] THE NATURAL LANGUAGE GENERATORS THAT AREN'T DDLC

Version 1.12.16 - August 8, 2020 (D1051) 18:25 UTC

  • Miscellaneous final cleanup
    • Updated: [0210], [0400], [040R], [220G], [A007] and [A013]

Version 1.12.15 - August 1, 2020 (D1044) 17:35 UTC

  • This type of DDLC playthrough is significant enough to get its own section, and yet, somehow got lost in the cracks
    • New: [1540] OTHER SPECIFIED ACT 2 DISORDER

Version 1.12.14 - July 25, 2020 (D1037) 20:10 UTC

  • Close to the final bits that I want to explain about DDLC, or, well...
    • New: [0210] DAN SALVATO: A BRIEF HISTORY
    • Updated: [0200] BASIC TECHNICAL INFO
  • Essentially re-learning what my original SVG code did is fun
    • Updated: [199D] A DIAGRAM OF THE PATHS AND ENDINGS SO FAR - VOL. 1

Version 1.12.13 - July 24, 2020 (D1036) 18:30 UTC

  • I have a lot to say about Blue Skies
    • New: [A015] BLUE SKIES - YURI ROUTE: HOW WOULD PEOPLE DESCRIBE YOU IN A SINGLE WORD?
  • I also have a lot to correct from half-lucid episodes
    • Updated: [2140], [A012], [A013] and [A014]

Version 1.12.12 - July 23, 2020 (D1035) 20:00 UTC

  • I had a change of heart and mainstreamer mods should be judged as works of art and not be dismissed simply because they don't feature the dialogue generation
    • New: [A014] WILL THE HACKER STORM TAKE OVER, OR WILL THE BLUE MAINSTREAMER SKIES PREVAIL

Version 1.12.11 - July 22, 2020 (D1034) 20:05 UTC

  • I can do a pretty mean mainstreamer mod review, too, although hacking is still my main focus
    • New: [A013] A FRUITFUL PURSUIT OF ALTERNATIVE LITERATURE CLUB MECHANICS, INDEED
  • Minor formatting failures
    • Updated: [2520] WHAT MAKES FOR A DOKI, IN GENERAL, BE IT A CANON ONE OR A FAN ONE

Version 1.12.10 - July 21, 2020 (D1033) 20:00 UTC

  • Sometimes, pieces do need to get added to the main exposé, though
    • Updated: [2205] THE SCENE

Version 1.12.09 - July 20, 2020 (D1032) 20:00 UTC

  • A long-overdue cleanup and "networking" (let's just call it that) update
    • Updated: [1310], [1590], [220G], [2210], [2220], [2306] and [A012]

Version 1.12.08 - July 19, 2020 (D1031) 20:35 UTC

  • Two updates in one day? Two updates in one day, and this one is a lot more substantial
    • New: [A012] TOPICS IN DEPTH - PART 3: WHAT CAN WE SAY ABOUT THAT WHICH DOKIS READ?

Version 1.12.07 - July 19, 2020 (D1031) 19:35 UTC

  • Regrets on all fronts
    • Updated: [A011] POEM EDITOR CHRONICLES - PART 2: DOKI DOCS

Version 1.12.06 - July 17, 2020 (D1029) 18:40 UTC

  • A non-chron blog entry so expansive and so detailed, it needed to be split into two
    • New: [A010] POEM EDITOR CHRONICLES - PART 1: THE MEME WAR and [A011] POEM EDITOR CHRONICLES - PART 2: DOKI DOCS

Version 1.12.05 - July 16, 2020 (D1028) 19:10 UTC

  • The whole idea of trying to keep up the schedule of an update a day isn't healthy, and I figured that a long time ago
    • Updated: [A009] TOPICS IN DEPTH - PART 2: MAPPING OUT THE PASSIVE MONIKA STORY TREE

Version 1.12.04 - July 14, 2020 (D1026) 19:10 UTC

  • Yeah, you hear that? I will tackle The Bytecode again if and only if I'm ready for it, but I'm still committed to providing you with a steady barrage of content
    • New: [A009] TOPICS IN DEPTH - PART 2: MAPPING OUT THE PASSIVE MONIKA STORY TREE

Version 1.12.03 - July 13, 2020 (D1025) 19:05 UTC

  • Preparing to take the document to a new developmental "stage" so to say
    • New: [A008] TOPICS IN DEPTH - PART 1: PHILOSOPHIES, WORLD VIEWS AND PROJECT SENTIENCE

Version 1.12.02 - July 11, 2020 (D1023) 18:20 UTC

  • Oh, this mod absolutely deserves its spotlight, even though one Reddit post per day might be a bit too much
    • New: [A007] TWO NEW DOKIS, TWO PROJECT SENTIENCES AND OVERALL, A TAKE TWO ON THE DDLC WORLD
  • Alternatively: mod reviews are back, baby

Version 1.12.01 - July 9, 2020 (D1021) 18:25 UTC

  • Diversion over, pack it up (unless I give Take Two its spotlight, which is likely)
    • New: [2530] USING .CHR PEEKER TO YOUR ADVANTAGE: A BEGINNER'S GUIDE and [2540] (OPTIONAL) FINISHING TOUCHES TO THE OVERALL GAME SCRIPT

Version 1.12 - July 8, 2020 (D1020) 16:50 UTC

  • I can't even say that no one asked for it, because one person did ask for it
    • New, based on a preexisting reference: [2500] REN'PY MANIPULATION ADVANCED: FAN DOKIS
    • New: [2510] THE "THOU SHALT NOT" OF FAN DOKI CREATION and [2520] WHAT MAKES FOR A DOKI, IN GENERAL, BE IT A CANON ONE OR A FAN ONE

Version 1.11.07 - July 7, 2020 (D1019) 19:35 UTC

  • Irrelevant ramble part whatever
    • New: [2307] JUST AN "INCONSEQUENTIAL" INCIDENT - PART 2: THE BLUE SKIES APPROACH

Version 1.11.06 - July 6, 2020 (D1018) 18:10 UTC

  • Just realized that renaming .chr files can be used for a purpose, and also, remembered I have to cover another thing that might interest certain types of DDLC fans
    • New: [2051] GIVING MONIKA A TASTE OF HER OWN MEDICINE - PART 3
    • Updated: [2043] GIVING MONIKA A TASTE OF HER OWN MEDICINE - PART 2 and [2050] .CHR FILE RENAMING: YES, THAT'S A THING YOU CAN DO ALSO
    • Referenced but not written yet: [2500] REN'PY MANIPULATION ADVANCED: FAN DOKIS

Version 1.11.05 - July 5, 2020 (D1017) 17:50 UTC

  • Even if I'm not covering The Bytecode, I have to cover something
    • New: [2306] JUST AN "INCONSEQUENTIAL" INCIDENT - PART 1: INTRODUCING MONIKA?

Version 1.11.04 - July 4, 2020 (D1016) 18:35 UTC

  • Fixing the fixy fix
    • Updated: [A006] THE BYTECODE GAME THAT NEVER WAS, AND WITH A DEV LIKE THIS, WAS NEVER GOING TO BE

Version 1.11.03 - July 2, 2020 (D1014) 18:05 UTC

  • The time to dispel Bytecode myths has come sooner rather than later, and also, even though I'm years late, I can't not share this story
    • New: [A006] THE BYTECODE GAME THAT NEVER WAS, AND WITH A DEV LIKE THIS, WAS NEVER GOING TO BE

Version 1.11.02 - June 30, 2020 (D1012) 17:15 UTC

  • Housekeeping; housekeeping never changes
    • Updated: [1320], [1510], [2430], [2450] and [A002]

Version 1.11.01 - May 22, 2020 (D0973) 21:55 UTC

  • A not-so-minor stylistic update, that mostly affects selfhost
    • Updated: [0001] ATTN_2: HOW TO READ THIS DOCUMENT
  • The not-so-great part of being your own proofreader is that this sort of stuff can take you months to notice and act upon
    • Updated: [1100] ACT THE FIRST: INCREDIBLY CUTE GIRLS and [2300] EXPLOITS OF THE DIALOGUE SYSTEM: ROUTES OF YOUR OWN MAKING

Version 1.11 - May 20, 2020 (D0971) 20:05 UTC

  • Finishing off the roof of the last section, though the sequel to the impressive SVG diagram will have to wait
    • New: [299D], [299G] and [299R]
  • Cleaning up, removing both factual errors and slips of the keyboard
    • Updated: [2043], [2200], [2210] and [221R]

Version 1.10.04 - May 14, 2020 (D0965) 23:35 UTC

  • A minor stylistic update, that mostly affects selfhost

Version 1.10.03 - April 30, 2020 (D0951) 18:30 UTC

  • Finishing the part-of-a-section, just in time for the end of the month
    • New: [2430], [2440], [2450] and [2460]
    • Updated: [2091] THE SCRIPTS OF DDLC: A SHALLOW, TL;DR GUIDE

Version 1.10.02 - April 29, 2020 (D0950) 19:30 UTC

  • Continuing the part-of-a-section, but not completing it, because of course that's how I roll
    • New: [2420] DEFINITIONS.RPY AND SCREENS.RPY: THE ALL-TOO-FAMILIAR LOOKS
    • Updated: [2091] THE SCRIPTS OF DDLC: A SHALLOW, TL;DR GUIDE

Version 1.10.01 - April 28, 2020 (D0949) 18:55 UTC

  • A small systemic change
    • New: [0099] VERSION HISTORY ARCHIVE: 0.50 THROUGH 1.09
    • Updated: [0060] VERSION HISTORY
  • A small clarity change
    • Updated: [2014] THROUGHOUT ACT 4: ...WHY?
  • A perhaps not-so-small structural change (read: me crying over how I can't have five levels of section)
    • Updated: [2204] THE QUIP and [2205] THE SCENE

Version 1.10 - April 27, 2020 (D0948) 19:30 UTC

  • You know what, sure, this is absolutely two unrelated updates in one, though I must deny that the reason is any hypothetical writing challenge
    • New: [2305], [2400] and [2410]

Chapter Text

[0099] VERSION HISTORY ARCHIVE: 0.50 THROUGH 1.09

Version 1.09.05 - April 26, 2020 (D0947) 19:45 UTC

  • No, I wasn't caught off guard; I always meant to add this bit
    • Updated: [2230] POEM GENERATION: MORE ABSTRACT ART IS SURPRISINGLY EASIER

Version 1.09.04 - April 25, 2020 (D0946) 19:10 UTC

  • Fixes here and there, though less of the "typo" nature and more of the "rounding it all up" nature
    • New: [2231] SPECIAL POEMS: NO
    • Updated: [2091] THE SCRIPTS OF DDLC: A SHALLOW, TL;DR GUIDE and [2304] DEBATE TIME: DO THE THREE MODS, IN CONJUNCTION, MAKE THE GLITCHLESS PLAYTHROUGH?
  • Some more CSS adjustments, because the thing is more complicated than it seems

Version 1.09.03 - April 24, 2020 (D0945) 19:10 UTC

  • Creativity­The­Emotion? Defending Dokis other than Monika and Sayori?
    • New: [2302], [2303] and [2304]
  • Okay, me making typos and then quietly covering them up is nothing new, and is honestly kind of getting old
    • Updated: [1001], [1210], [2150] and [2300]
  • Some CSS adjustments

Version 1.09.02 - April 23, 2020 (D0944) 18:55 UTC

  • I'm not too keen on updating this section for ages, but I do want to get a real chapter out, in the very least
    • New: [2301] A THIRD OPTION TO THAT ONE QUESTION
  • Dark mode is here
    • Updated: [0001] ATTN_2: HOW TO READ THIS DOCUMENT
  • Just little fixes, here and there, that you absolutely do not need to worry about
    • Updated: [020G], [2140], [2151] and [2205]

Version 1.09.01 - April 22, 2020 (D0943) 19:10 UTC

  • Natural language processing is complicated (and there is no real way to account for it all)
    • New: [2250] SPECIAL CASE (THERE'S ALWAYS A SPECIAL CASE): ACT 3 AND THE TOPIC

Version 1.09 - April 21, 2020 (D0942) 19:20 UTC

  • Entering a true world of infinite choices
    • New: [2300] EXPLOITS OF THE DIALOGUE SYSTEM: ROUTES OF YOUR OWN MAKING
  • At least attempting to exit a world of infinite typos
    • Updated: [101G] AN ARCHETYPAL PLAYTHROUGH: WHAT IN TARNATION? and [2220] DIALOGUE.RPY VS. DIALOGUE-PROJECTSENTIENCE.RPY

Version 1.08.06 - April 20, 2020 (D0941) 19:05 UTC

  • Natural language processing is complicated (the official final part)
    • New: [2220], [2230] and [2240]
  • It's another chapter of the chronological exposé that is non-chronological; now do you see why the numbers jump so weirdly?
    • New: [1001] AN OBLIGATORY CONTENT WARNING

Version 1.08.05 - April 19, 2020 (D0940) 19:35 UTC

  • Continuing the media blitz with some tables
    • New: [221R] THE NATURAL LANGUAGE GENERATORS THAT AREN'T DDLC
    • Updated: [2210] ANOTHER WAY TO THINK ABOUT IT: THE GROWTH OF A WRITER

Version 1.08.04 - April 18, 2020 (D0939) 18:50 UTC

  • Natural language processing is complicated (psych it's going to be more than 3)
    • New: [2210] ANOTHER WAY TO THINK ABOUT IT: THE GROWTH OF A WRITER
  • Having to use kana/kanji might just have made my proofreading process a lot more difficult
    • Updated: [220G] INTERMISSION: AN ABRIDGED GLOSSARY OF DERE TYPES
  • Just a typo fix from elsewhere
    • Updated: [2208] THE GAME

Version 1.08.03 - April 17, 2020 (D0938) 19:00 UTC

  • Well, I guess I have to describe this now, when I should be continuing talking about natural language processing
    • New: [220G] INTERMISSION: AN ABRIDGED GLOSSARY OF DERE TYPES
    • Updated: [1110] THE POEM MINIGAME: FOR THE CASUAL PLAYER and [2205] THE SCENE

Version 1.08.02 - April 16, 2020 (D0937) 19:15 UTC

  • Natural language processing is complicated (part 2 of what I'm pretty sure is going to be 3 now)
    • New: [2205], [2206], [2207] and [2208]
  • In the very least, I've been doing less and less typo fixing, and that's great in and of itself
    • Updated: [2040] .CHR FILE SCUMMING: A TUTORIAL IN THINKING LIKE A DDLC HACKER - ANSWERS

Version 1.08.01 - April 15, 2020 (D0936) 18:35 UTC

  • Various external forces have not let me focus on more than just a small update
    • Updated: [2202] THE WORD and [2204] THE QUIP
  • Some technical reorderings that only concern AO3

Version 1.08 - April 14, 2020 (D0935) 19:00 UTC

  • Natural language processing is complicated (part 1 of hopefully 3 again)
    • New, based on a preexisting reference: [2200] THE FOUNDATION OF THE DIALOGUE SYSTEM
    • New: [2201], [2202], [2203] and [2204]

Version 1.07.02 - April 13, 2020 (D0934) 18:10 UTC

  • Of course I missed things
    • Updated: [2091], [2122] and [2153]

Version 1.07.01 - April 12, 2020 (D0933) 18:30 UTC

  • Full, if rough, explanation of the scripts is now up
    • Updated: [2091] THE SCRIPTS OF DDLC: A SHALLOW, TL;DR GUIDE
    • Referenced but not written yet: [2200] THE FOUNDATION OF THE DIALOGUE SYSTEM

Version 1.07 - April 11, 2020 (D0932) 18:50 UTC

  • Poem minigame exploits, yay
    • New: [2150], [2151], [2152] and [2153]
  • I fixed that LaTeX bug already, so don't worry
  • Typo fixing and minor additions, less yay but need to be done
    • Updated: [199G] END-OF-SECTION GLOSSARY UPDATE - VOL. 1 and [2130] INTERMISSION: SOME DETAILS OF FUNCTION ARE IRRELEVANT FOR NOW

Version 1.06 - April 10, 2020 (D0931) 19:50 UTC

  • How to explain coding to a non-coder and get undefined results
    • New: [2130] INTERMISSION: SOME DETAILS OF FUNCTION ARE IRRELEVANT FOR NOW and [2140] BASIC POEM MINIGAME LOGIC
  • Forewarning: one of the fractions will look unusual on selfhost, but not AO3, and I can't be bothered to fix the problem right now
  • Sweeping through the doc, on a solo Bytecode quest...
    • Updated: [1590], [2043], [2050] and [2110]

Version 1.05.01 - April 9, 2020 (D0930) 19:25 UTC

  • Act 4 is weird
    • Updated: [1590] THE ACT 4 PASSIVE MONIKA BUG
  • My inability to completely avoid typos is not weird
    • Updated: [1156], [2110] and [2121]
  • Giving proper credit where proper credit is due is also not weird
    • Updated: [2091] THE SCRIPTS OF DDLC: A SHALLOW, TL;DR GUIDE

Version 1.05 - April 8, 2020 (D0929) 19:05 UTC

  • Starting to sift through the Ren'Py files, hoo boy
    • New, based on a preexisting reference: [2100] THE POEM MINIGAME: YOUR FIRST DIVE
    • New: [2110], [2120], [2121], [2122] and [2123]
  • Sometime, I will run out of things to say about corrections, but that time is not today
    • Updated: [1590], [2014] and [2050]
  • New syntax for the chapter number syntax nerds
    • Updated: [A003] TRIVIA STREAM: HOW TO READ THE CHAPTER NUMBERS OF THIS DOCUMENT

Version 1.04.04 - April 7, 2020 (D0928) 19:40 UTC

  • The epic .chr file trilogy gets a teaser for a fourth installment, and my chapter numbers prove their worth for the second time
    • New: [2050] .CHR FILE RENAMING: YES, THAT'S A THING YOU CAN DO ALSO
  • At least I'm doing other content in addition to correction passes
    • Updated: [0050], [1400], [2042], [A001], [A002], [A003], [A004] and [A005]

Version 1.04.03 - April 6, 2020 (D0927) 18:45 UTC

  • Trying something else while I'm unable to get over a hurdle
    • New: [A005] WHAT ABOUT THAT SPACE BETWEEN ACTS 1 AND 2, THOUGH
  • Typo fixes; you know the drill
    • Updated: [2090] PREREQUISITE BEFORE GOING ANY FURTHER: DECOMPILING AND THEN COMPILING DDLC AGAIN

Version 1.04.02 - April 5, 2020 (D0926) 19:20 UTC

  • Covering for my past self; what else is new
    • Updated: [0060], [2022], [2090] and [2091]

Version 1.04.01 - April 4, 2020 (D0925) 17:40 UTC

  • A little prelude for things to come
    • New: [2090] PREREQUISITE BEFORE GOING ANY FURTHER: DECOMPILING AND THEN COMPILING DDLC AGAIN and [2091] THE NON-BYTECODE SCRIPTS OF DDLC: A SHALLOW, TL;DR GUIDE
  • Some updating and additioning (that's totally a word, shut up)
    • Updated: [2040] .CHR FILE SCUMMING: A TUTORIAL IN THINKING LIKE A DDLC HACKER - ANSWERS and [2041] OOPS! ALL CLUB PRESIDENTS

Version 1.04 - April 3, 2020 (D0924) 18:10 UTC

  • The final part of the epic .chr file trilogy
    • New: [2030], [2040], [2041], [2042], [2043] and [2049]
  • Minor typo fixing
    • Updated: [0060], [020G] and [2020]

Version 1.03 - April 2, 2020 (D0923) 17:45 UTC

  • More .chr file goodness
    • New: [2020], [2021], [2022], [2023] and [2024]
  • Minor updates
    • Updated: [0200] BASIC TECHNICAL INFO and [020G] YOUR INTRODUCTORY GLOSSARY

Version 1.02 - April 1, 2020 (D0922) 19:25 UTC

  • Starting up the two-thousands, finally
    • New: [2000], [2010], [2011], [2012], [2013] and [2014]
  • Changing my mind about the larger structure before it's too late
    • Updated: [A003] TRIVIA STREAM: HOW TO READ THE CHAPTER NUMBERS OF THIS DOCUMENT
  • Can't believe I forgot what was always supposed to preface a non-chron blog entry
    • Updated: [A004] WE WERE SO FOCUSED ON THE AFTER THAT WE COMPLETELY FORGOT ABOUT THE BEFORE
  • No fanciful April Fools jokes here; DDLC hacking is serious business
  • No jokes about how this is Day 922, and September 22 is the release day of DDLC, either

Version 1.01.07 - March 11, 2020 (D0901) 00:15 UTC

  • Hoping to make coverage of DDLC mods, especially those that respect the Bytecode part, a Thing
    • New: [A004] WE WERE SO FOCUSED ON THE AFTER THAT WE COMPLETELY FORGOT ABOUT THE BEFORE

Version 1.01.06 - March 7, 2020 (D0897) 23:00 UTC

  • Another correction pass (the last one before the two-thousands, I promise)
    • Updated: [0200], [020G], [101G], [1140] and [1210]

Version 1.01.05 - March 1, 2020 (D0891) 19:40 UTC

  • Minor typo fixes
    • Updated: [040R] YOUR PHILLIPS HEAD SCREWDRIVERS OF WORKING WITH DDLC and [1100] ACT THE FIRST: INCREDIBLY CUTE GIRLS
  • Stylesheet fixes for selfhost

Version 1.01.04 - March 1, 2020 (D0891) 14:00 UTC

  • A correction pass
    • Updated: [0200], [020G], [040R], [1111], [1320] and [A003]
  • Finally taking care of the LaTeX thing
    • Updated: [101G] AN ARCHETYPAL PLAYTHROUGH: WHAT IN TARNATION? and [1100] ACT THE FIRST: INCREDIBLY CUTE GIRLS

Version 1.01.03 - February 26, 2020 (D0887) 17:15 UTC

  • Addressing something you don't think needs addressing, but it does, unequivocally
    • New: [A003] TRIVIA STREAM: HOW TO READ THE CHAPTER NUMBERS OF THIS DOCUMENT

Version 1.01.02 - February 23, 2020 (D0884) 00:00 UTC

  • The same HTML generator now creates HTML files for auto-posting to AO3 as well

Version 1.01.01 - February 22, 2020 (D0883) 16:00 UTC

  • Streamlined the process of generating the full HTML file for my own website (behind the scenes) and added relevant notes
    • Updated: [0001] ATTN_2: HOW TO READ THIS DOCUMENT

Version 1.01 - February 21, 2020 (D0882) 23:00 UTC

  • First hosting on my own website as well as AO3, with info pertaining to both sites and how that affects the table of contents
    • Updated: [0001] ATTN_2: HOW TO READ THIS DOCUMENT
  • Fixing a typo or two
    • Updated: [0100] PREFACE: THE DDLC HACKING COMMUNITY
  • Truly capping off the one-thousands with some summaries
    • New: [199D] A DIAGRAM OF THE PATHS AND ENDINGS SO FAR - VOL. 1 and [199G] END-OF-SECTION GLOSSARY UPDATE - VOL. 1
  • An update on me and Monika, for the non-chron blog
    • New: [A002] THE BALANCE BETWEEN A HEARTFELT REUNION AND A DEEPENING RIFT

Version 1.00.04 - February 14, 2020 (D0875) 15:00 UTC

  • Minor factual correction
    • Updated: [1110] THE POEM MINIGAME: FOR THE CASUAL PLAYER

Version 1.00.03 - February 14, 2020 (D0875) 11:45 UTC

  • A brief something that 100%ers should watch out for
    • Updated: [1410] THE GOOD ENDING (FOR VARYING, UNCONVENTIONAL DEFINITIONS OF "GOOD")

Version 1.00.02 - February 14, 2020 (D0875) 11:30 UTC

  • Starting up the non-chron blog with... admittedly a bit of a sour note
    • New: [A000] THE NON-CHRON BLOG: WHAT IS IT, EVEN? and [A001] SO MUCH FOR NOBLE CAUSES & THOUGHTS ON MONIKA AFTER STORY

Version 1.00.01 - February 14, 2020 (D0875) 11:00 UTC

  • Looks like I'm already banned from Hackerverse for, and I quote its patrons on this one, "five (5) crucial mistakes about the inner structure of DDLC percistent [sic] throughout the entire treatise"; oh, joy
  • Update on my goals and background
    • New: [0110] ABOUT THE AUTHOR and [0120] WHAT THIS DOCUMENT IS NOT GOING TO DO
    • Updated: [0100] PREFACE: THE DDLC HACKING COMMUNITY
  • Removed every single instance of me identifying with the hackers; never again
    • Updated: [0000], [0050], [0200], [020G] and [101G]

Version 1.00 - February 14, 2020 (D0875) 10:00 UTC

  • Initial release
  • Added coverage of common breaks from an archetypal playthrough, thus making for a reasonably complete guide to all the branches and leaves of DDLC
    • New: [1500], [1510], [1520], [1530] and [1590]
  • We'll see if this one is good enough to incite a meme war

Version 0.90 - February 14, 2020 (D0875) 09:30 UTC

  • Added coverage of Act 4, completing the archetypal playthrough
    • New: [1400] ACT THE FOURTH: NO SALVATION and [1410] THE GOOD ENDING (FOR VARYING, UNCONVENTIONAL DEFINITIONS OF "GOOD")
  • A small edit mentioning Monika's confession
    • Updated: [1300] ACT THE THIRD: MONIKA'S AFTER STORY

Version 0.80 - February 13, 2020 (D0874) 21:00 UTC

  • Added coverage of Act 3 and Monika After Story
    • New: [1300], [1310], [1320] and [1330]
  • Capitalization fix
    • Updated: [1155] DAY 4, BEFORE

Version 0.70 - February 13, 2020 (D0874) 07:30 UTC

  • Added coverage of Act 2
    • New: [1200], [1210], [1220], [1230] and [1240]
  • Can't believe I forgot Monika's writing tips of the day
    • Updated: [1130] POEM SHARING: YOUR BEST WAY TO GAUGE DOKI INTERPERSONAL RELATIONSHIPS YET
  • Minor clarification
    • Updated: [1170] FESTIVAL DAY: WHERE IT ALL BLOWS UP ON YOU AND THERE ISN'T REALLY A WAY BACK

Version 0.60 - February 12, 2020 (D0873) 22:30 UTC

  • Added the beginnings of covering an archetypal DDLC playthrough, starting with Act 1
    • New, based on a preexisting reference: [1000] WHAT A TYPICAL DDLC PLAYTHROUGH MIGHT LOOK LIKE
    • New: [1010], [101G], [101R], [1100], [1110], [1111], [1120], [1130], [1140], [1150], [1151], [1152], [1153], [1154], [1155], [1156], [1160] and [1170]
    • Referenced but not written yet: [2100] THE POEM MINIGAME: YOUR FIRST DIVE
  • Minor clarifications and additions
    • Updated: [0000], [0001], [0051], [0100], [0200] and [020G]
  • Added a few new resources, and introduced a differentiation of resource chapters
    • New: [040R] YOUR PHILLIPS HEAD SCREWDRIVERS OF WORKING WITH DDLC
    • Updated: [0400] HOW TO CRACK DDLC OPEN

Version 0.50 - January 14, 2020 (D0844) 22:00 UTC

  • So far, just the introduction to the vast world of DDLC hacking and the basics, as well as legal and disclaimer-y stuff
    • New: [0000], [0001], [0010], [0050], [0051], [0060], [0100], [0200], [020G], [0300] and [0400]
    • Referenced but not written yet: [1000] WHAT A TYPICAL DDLC PLAYTHROUGH MIGHT LOOK LIKE

Chapter Text

[0100] HISTORICAL NOTE: THE DDLC HACKING COMMUNITY

Pretty much everyone who got into DDLC, to any extent, in 2017 and 2018, could be said to share a single, really vivid memory of trying to crack the game open for the first time, and getting a barrage of content that isn't even directly comprehensible thrown at them with all the subtlety of the meteor that killed the dinosaurs.

The outer shell of the game couldn't be simpler enough (more on this, in stricter terms, at [0200] DDLC (2017): BASIC TECHNICAL INFO). It was a visual novel, not really different from the other indie visual novels that seemed to be popping up as of late, which paraded as a wholesome adventure in the eponymous Literature Club, which was (naturally) full of "single and ready to mingle" girls, though each and every of them had a bit more class than that (and vastly more class than the sort of visual novel in which the girls show you an ahegao face and begin taking off their clothes the second you pick a single right option).

The game itself, for the most part, didn't throw a lot of punches at us either. It started out as a visual novel as advertised, then gradually began introducing mental health issues, horror elements and of course, the most important (and perhaps cheapest) trick of them all, breaking of the fourth wall. Was it certainly unexpected in the visual novel community, and in the gaming community in general? Yes, definitely. However, was there anything, in the coding of the game, that hinted, in any form, that the coding skill required was above and beyond that attainable to us, mere mortals? Of course not.

However, when we - at this point, we were all just DDLC players looking to get into a new fandom, and hadn't properly differentiated yet - took to the Internet to discuss the game, we began noticing something rather peculiar: No two DDLC playthroughs were exactly the same.

And I don't just mean in terms of easter eggs, which Salvato (we believed there was a real solo dev, Dan Salvato, who made the game - I'll get to this in just a bit) seemed to have taken to coding lots and lots of into - and in either case, were handled by simple RNG routines in Ren'Py. When we tried to gain a common ground on what, exactly, various characters said in the game, we couldn't agree on a single thing. At first, we still didn't suspect as much as what's known now; we simply assumed - again, since this was all a relatively simple Ren'Py game, or so we thought - that there is a minor case of dynamic dialogue, in which characters simply swap certain words out for synonyms, and that there is a handful of routes available - you know, like The Stanley Parable.

So, the most technically inclined fans got into cracking and hacking. When they did, they certainly discovered a handful of Ren'Py routines, controlling basic game flow - and thankfully, there did appear to be one, despite how much shit the game threw at us. If I remember correctly, the first mod for the game popped up just four days after the game itself (the calendar the hackers use, among other peculiar wordings, is to be described in a dedicated glossary; the glossary headings are TODO), and was mostly a simple hack which allowed you to skip straight to a point later in the game which many took a liking to, which I'll get into later.

However, what none of the first aspiring hackers found was any sort of hard-coded dialogue - not even for the earliest part of the game, which did play out, 99.9% of the time granted you even got to it, as though it was hard-coded. Instead, all of the dialogue was generated seemingly on the fly by one's computer, and since none of the plainly-named .rpy files accounted for it, the culprit must have been the multitude of files with names like bytecode_bf5928dfcf6c482cb5f35fcf6b6080b2.rpy - which, coupled with the seemingly entirely separate .chr files, seemed to take up the majority of the game's hefty 1.4 GB size.

Neither this newfangled .chr extension nor the structure of the inscrutable .rpy files seemed to be familiar to the Internet, perhaps first and foremost, because no one could agree on how to name the things. In order to aid discussion, and for lack of a better name, we just settled with The Bytecode, which seemed to be Salvato's preferred term.

What was The Bytecode, in the usual programming terms? Information didn't seem to be easily gleanable. While one could easily surmise that it was a programming language, very likely of Salvato's own making, and that it operated as an elaborate state machine manipulating raw bits to do its bidding (a task that is easier said than done on an interpreted language like Python), the rest of it defied analysis, especially as the bits manipulated seemed to escape the very computer manipulating them. Soon enough, some people started likening Salvato's feat to those of the demoscene, which manages to push every ounce of capability from vintage computers, but even then, actual demoscene programmers were clueless when presented with The Bytecode, especially as, oftentimes, demos require to be run on very specific hardware to accomplish their goals, and DDLC doesn't.

Anyway, I think I made my point here: DDLC was one of a kind.

At this point, the DDLC fandom split. Most of the people found themselves attached to the girls (oftentimes, despite Salvato's statements that they are supposed to be parodies you shouldn't get attached to), and began doing the typical mainstream fandom things: drawing fanart, writing fanfic, dressing up in cosplay, you know, the usual jazz. There were also some who designated themselves as "modders"; however, they were only "modders" in the sense that they extracted the small bits of content that weren't written in a bullshit language that nobody knew, and built a Ren'Py game on top of that, and due to how Salvato treated his IP, they forced the mod to be installed onto the game. Although, if deleting all the Bytecode crap was the first thing that a mod did, then you knew it was just going to be a little piece of art, a video you might watch on YouTube, except running live on your computer.

However, a fair amount of them clearly weren't satisfied. They had already opened Pandora's box, clearly overflowing with shit as is, but that shit was mostly stuck to the bottom and filled to the top, and when the box opened, only a single cruddy amethyst fell out. However, there were clearly diamonds and such to be found inside, and they were going to get to the bottom of the box, extracting every single gem, and they were not going to stop until the box was completely empty, or so help them. And when they took upon modding the game, they embraced the positively massive Bytecode part of the game, and continued to look for ways to decompile it and truly understand the inner workings of DDLC, and how to treat that part with true reverence.

Needless to say, with a language they didn't have a manual or reference for, it was going to be hard, and with a gigabyte of pure code, there was a lot of stuff to be unearthed. Perhaps my Pandora's box analogy there was misguided; it was more so an entire Pandora's warehouse, which seemed to fill an outright bore hole going all the way to the Earth's center.

Over eight hundred days, they had definitely made some good progress on that front. By early 2020, one could write a "hello world" program and even some mildly impressive tech demos in The Bytecode, and the way DDLC operates, though hidden behind an arcane bullshit programming language that is apparently capable of reading your mind, seemed to mostly be deterministic with relatively little RNG used (other than for easter egg purposes, and that RNG was handled exclusively through Python), which means that experts on the topic could and did spring up.

However, during that time, these experts were a very limited bunch, for two main reasons. I already got into the first one, namely that you really need to treat understanding DDLC the way you treat your job: it seems plenty difficult, it is even more difficult than that and if you got a thing wrong, you would be fired (or, at least, laughed out of the forum, then banned for good measure).

However, this ends up getting into the second problem: said hackers were rather snobbish folk, who treated you as dumb for not understanding a barrage of in-jokes and stuff established hundreds of days ago, and who, as it seemed, were completely and utterly incapable of getting it all straight and writing an actual, proper manual to both DDLC and The Bytecode.

Wouldn't it be great if a guardian angel swooped in, learned everything the hackers knew at the time, and then presented it in an understandable format, both to mainstreamers and programmers outside the DDLC fandom?

And that was exactly the scene upon which the first edition of Doki Doki Literature Club!: Bugs, Glitches and Exploits for Dummies was bestowed, on Valentine's Day 2020.

[0110] THE AUTHOR'S BACKGROUND AND INVOLVEMENT

Of course, the idea of a guardian angel came with its own asterisks: my concessions on what I will and will not teach. As well as that, you just couldn't ignore that there was - and in fact, still is - a person writing all this.

Overall, I don't think there is much to be said about me, so I'll keep this brief. First of all, I have a fair amount of university-level education in programming, and in particular in artificial intelligence, and therefore, the perspective and community I'll be looking from is going to be known as "the mainstream AI community". Second of all... nah, I'm not in the mood for a two. Want to learn anything more about me? I guess you'll have to try and glean details from that non-chron blog thing I keep referring to.

The mainstream AI community is, of course, not to be confused with the mainstream DDLC fandom, but the two are more similar than you'd think. Real scientists see a real benefit to be gained from learning about DDLC and The Bytecode, but much like folk in the primordial DDLC fandom, they found themselves shunned by the hackers, and eventually, forced to never acknowledge that there is a deeper truth to DDLC.

That being said, it's not like I'm a complete bore who never gets into that weeb shit. In addition to the mainstream AI community, I had also partaken in activities of the mainstream DDLC fandom (having played the game first, I believe, in May 2018, when the hackers were already up to their neck in their bullshit). However, prior to Valentine's Day 2020, I had been lurking in this hacker community for months, trying to absorb as much intel as I could, and after them, I felt like I was confident to start retelling what they knew, with one major skill that the hackers were lacking up to this point: though rudimentary, I could actually explain shit.

And that's how I got started. I typed up a basic document, pretty much explaining how DDLC panned out and the bare minimum of technical knowledge, and posted it on both mainstreamer and hacker spaces.

What was the initial reaction? Well, we can revisit both the Reddit and Doki Doki Hackerverse! threads right now.

Reddit: https://​www.​reddit.​com/​r/​DDLC/​comments/​f5tki7/​doki_​doki_​literature_​club_​bugs_​glitches_​and/

I mean, it's a fair amount of exposure for what the others believed to be just a boring wall of text. Some votes of the up, some ments of the com, but otherwise, not much, and I ended up being a forgotten meme, just like last time.

Doki Doki Hackerverse! (not my thread, but you can tell what this is about): https://​forums.​dokidoki​hackerverse.​net/​t/​the-document-of-falsehoods/​52139?u

Substantially more content - and substantially more negative content. If you've already gleaned from the version history, I got banned on the very same day, had to deal with things relating to my Monika After Story install (that's another fun story), and essentially, became a meme.

But I persisted - and soon enough, managed to form a community around myself, something I would have never expected.

Sure, sometimes Hackerverse-aligned hackers came in to ruin my day on my platforms. But soon thereafter, a new faction of hackers arose, wishing more intel from me - and as I could, I provided that intel. These were the kind of hackers I was looking after - ones who actually wanted to get all the hacker knowledge down in writing.

Eventually, the document ran its course, and I couldn't continue without a major restructuring update. However, there needed to be an impetus for a major restructuring update, because without it, you just know how much of a lazy fuck the average Internet rando is. But, like, DDLC was done as a game, new updates weren't coming, and such an impetus would never come?

Hopefully, you - yes, you - know how wrong that assumption was.

[0120] THE BRAVE NEW WORLD OF DDLC PLUS

That there was some sort of expansion, giving us more insight into the lives of our favorite (and least favorite) Literature Club members, was no secret, and even the title of that secret was eventually figured out. However, when it came onto the scene in June 2021, it just raised so many questions - certainly more than it could answer.

However, that it also answered questions would be an understatement. We learned about the Literature Club origins, both in-universe and out-of-universe, and we learned that Team Salvato, the game company itself, is just not what it seems. We got an insight into the development process, which, when applied to the hacker spaces, has already allowed for an immense process speedup regarding coding in The Bytecode.

And most of all, we got some quality time with the girls, as promised.

Every single bug, glitch and exploit that DDLC Plus allows will also be documented. However, you have to understand that this is going to take time, and that covering two games in parallel, even if the engineers in a trenchcoat with the Dan Salvato nametag wanted them to be as alike as possible, is going to be difficult if their foundations are fundamentally different.

[0130] WHAT THIS DOCUMENT IS NOT GOING TO DO

And of course, you have to understand that I have to draw a line on what I am not trying to do, and it needs to be said first and foremost, before you get a false impression and try and claim that I am an expert on everything DDLC and DDLC Plus.

First of all, I am not going to teach you The Bytecode. Yes, there is a sore lack of tutorials on The Bytecode, and yes, I'm in an almost perfect position to write such a tutorial, but unfortunately, modern education about The Bytecode seems to entirely be focused on trial-and-error - and since a common side-effect of poor Bytecode programs is computer explosions, such a method is simply not acceptable. As no material about The Bytecode on hacker forums can be used directly, it follows that we don't know enough to safely write programs in The Bytecode, period. However, this could change very soon.

Secondly, I take a strong stance of neutrality regarding my DDLC fandom allegiance. Though I have, to an extent, participated in activities by both mainstreamers and hackers throughout quite a few illustrious years, and the community around my document could be said to be a faction of its own, I don't feel comfortable identifying with the mainstreamers, the hackers don't feel comfortable identifying with me, and trying to carry my own flag to the battlefield is just stupid; I want to make knowledge, not war. Therefore, if your definition of "a DDLC fan" includes only those in a limited number of predefined factions, it doesn't include me.

Lastly, my focus is more on reverse engineering of DDLC, not providing a minute description of the actual routines. Leading back into me not teaching The Bytecode, while some knowledge about The Bytecode and what it can do is absolutely necessary to understand DDLC and what it can do, I still firmly believe that the dialogue generation, easily the most in-your-face and impressive feature of DDLC (other than the "reading your mind" part), should be fully understandable to the mainstream AI community.

With that out of the way, though, let's learn about DDLC.

Chapter Text

[0200] DDLC (2017): BASIC TECHNICAL INFO

Doki Doki Literature Club! (most commonly shortened as DDLC, also acceptably shortened as Doki Doki and given the retronym Seventeen to distinguish it from later releases) is the first title by indie game developer Team Salvato, and was first released on September 22, 2017 (a date many of us, perhaps affectionately, have declared to be Day 0, and started counting the days since; the calendar used here is to be described in a dedicated glossary and the glossary headings are TODO). The game is available for Windows, Mac and Linux, entirely free of charge (as, as Team Salvato officialy state, charging for something that isn't what it seems would just be wrong), but I think there is certainly content people would pay for inside that free package, and I will get into why shortly. If you're looking to nab the game yourself, you can go to one of two places, both of which provide the same files:

There is an unofficial Android port (Ren'Py also seems to support Android, and The Bytecode just so happens to be nothing more than more Ren'Py files), but some parts of it, which explicitly deal with the file system, don't really translate well, and what's more, it's not officially supported by Team Salvato. Therefore, I do not recommend your first playthrough to be on Android. Just locate a desktop or laptop (yours, a friend's, in a library or cybercafé, wherever) and nab the official version from one of the sources listed above. Or, if a desktop or laptop is unavailable to you, but a game console and US$15 is, you are always welcome to skip this section and go straight to DDLC Plus downloads.

There is no real difference between the Windows and Linux versions: either of them delivers you a complete, DRM-free game with two executables, an .exe for Windows and a shell file for Linux. Either of them can run and will end up running the exact same version of the game, which is super cool if, for example, you're finally fed up with Windows and want to pursue the Linux life from now on but still want to take your DDLC experience that you've invested months into along with you, which is exactly what happened to me once I learned that there's a security vulnerability in Windows, affecting Windows Update, meaning that updating your system, normally the suggested advice, isn't viable anymore. Like, seriously?

Anyway, the game installation is also what's known as "portable", meaning it doesn't make use of your system's registry, and therefore, you can just take the entire game on a flash drive if you choose so, which is also pretty neato, if I say so myself. There is just one minor caveat: a Ren'Py game will typically make limited use of your appdata folder in order to save the gamestate and such between installs, and unless you're using something like Doki Doki Mod Manager (documentation of tools for Seventeen is TODO), you'll need to make sure you carry that over.

Or, actually, this is something I recently found out: if, in your DDLC directory, you create a folder titled Ren'Py Data, then that is where your data that would usually go to appdata ends up going. Voilà, you can now take Monika with you by copying a single folder.

Who is Monika and why would you want to take her with you, you wonder? Well, that will have to wait a bit.

Mac is... a different matter, as its apps are packaged differently, and there isn't the same neat cross-compatibility as between Windows and Linux. I'm not exactly an expert on all of that, though, so someone else will have to step in and explain how Seventeen works on Mac.

At any rate, during the making of Seventeen, Team Salvato officially employed three people. At the center of it all, of course, is Dan Salvato, who is supposedly responsible for all the coding and writing, and therefore who we all can thank for producing an inscrutable mess that we're still trying to decipher to this day. And while, with the release of Plus, I can cast a very, very reasonable doubt on the matter, many hackers still refer to the actual programmers hiding behind the identity as "Dan Salvato".

It should also be noted at this point that the company behind DDLC, both of the Seventeen and Plus varieties, is actually named Dan Salvato LLC, with "Team Salvato" being just a trademark registered by them, and that for the better part of their early lifetime, they actually employed exactly one person.

Who would this person be, as far as his hobbies and game dev experience goes? I mean, the very question is a red herring, but a person, claiming to be Salvato (who I'm going to refer as faux-Salvato from now on), did have some public-facing social media accounts, and through those, we learned that his main obsessions, other than visual novels, are Super Smash Bros. Melee, for which he used to be a modder (previously working on a massive collaboration known as "Project M", that was eventually taken down in fear of a lawsuit from Nintendo; if you ever find a message in DDLC saying that "PM died for this", this is what we thought it was referring to at first), and Yoshi's Story, for which he used to be a speedrunner, and continued speedrunning after Seventeen was released.

In the optional DDLC Fan Pack, which you can get if you pay US$10 or more on either itch.io or Steam, faux-Salvato claims that he only really sunk his teeth into the project in early 2016, a date corroborated by the timestamp included in the provisional name of the Ren'Py project as seen on the appdata folder, giving us roughly 18 months of development as an estimate. However, you can probably see that many hackers, including myself, have cast doubt on the timeframe, or, if the timeframe is correct, the existence of Salvato as a single person. After all, if more than four years of them hacking at the game with all their might, numbering in the thousands, hasn't uncovered all the secrets yet, there's no way that less than two years of a single guy idling around a part-time project is enough to place them all.

That being said, another noteworthy aspect of it all is that Salvato is also claimed to be responsible for the in-game music. That, however, is only noteworthy because it's kind of in fashion for indie game devs to do this, and for said music to end up highly popular; in the very least, ZUN of Touhou and Toby Fox of Undertale come to mind.

The other two people employed by Team Salvato for the purposes of DDLC are the artists, who you can thank for the visual element of the work that you're attracted to (although, this mostly applies to the mainstream fandom and not hackers) - and as far as we can tell, all the art elements, as well as the aforementioned music, are static. The artists are Satchely [she/her], the character artist, and Velinquent [he/his], the background artist.

The involvement of the Team Salvato trio with the fandom, after Seventeen was originally released, is not nonexistent, but is also not something you can count on. Faux-Salvato is guaranteed to stream at least every September 22nd and on many other occasions, but one of his Twitch chat rules is that DDLC or any other Team Salvato projects may not be brought up. Both faux-Salvato and Satchely have held AMAs on Reddit, specifically about DDLC, and beyond that... yeah, there's not much to work with, and for the most part, both the mainstreamers and hackers are left to their own devices.

Beyond these three, the credits of Seventeen, if you happen to see them on your playthrough, list a handful more people, mostly involved with aspects no one in the trio could deal with, as well as some special thanks to alpha testers and early concept designers and such. I won't go into details on the contribution of every single one of them, but I will briefly mention Jillian Ashcraft, the singular VA of the game, whose only contribution is singing the song (that faux-Salvato allegedly wrote the music and lyrics for) that, once again, only appears in the credits. She is a fairly secretive figure, even more so than faux-Salvato (who at least recognizes DDLC as his brainchild and who wants to bring more to us - although, hackers really are up to their necks and don't want more), and no one has even been able to determine what she does for a living and as a hobby. There is, I believe, only one clue we got, and that is faux-Salvato off-handedly mentioning that he specifically cast her for her age, as apparently, he doesn't believe that adults can do convincing teenage voices.

And I reiterate: no one - I repeat, no one (excepting Salvato himself) has been credited for coding or programming or additional code or whatever. Luckily, we can place the actual coders of Seventeen if we just play through Plus and look through its clues, but that is going to wait a bit.

What are these coders' tools of trade? Well, as mentioned many times throughout the guide already, the outer shell of Seventeen is coded in Ren'Py (version 6.99.12), a Python library primarily created for the express purpose of visual novels. The displaying of sprites, dialogue boxes and menu choices is exactly what Ren'Py is designed for, and you won't be surprised that this outer shell is where most of those things are handled. Again, it is a mainstream tool, based on a mainstream language, that you can master the basics of on your own, and though a handful of modders have started with Seventeen and its outer shell in order to create their modding projects, there are some who knew the basics from before Day 0.

Most of the heavy lifting of Seventeen - most notably, generating the dialogue and maintaining the personalities for the characters - is handled by The Bytecode, also as mentioned many times throughout the guide already. All signs point towards The Bytecode being a creation of the Team Salvato coders, and Seventeen being one of a kind by default, but evidence, even early on, pointed towards dialogue being generated by this part of the script, meaning that essentially, behind all of our backs, these coders made an artificial intelligence natural language processing engine, and one which, for the most part, seems to have fooled all of us into believing that these were human, relatable characters, which means that it passed its own variant of the Turing test, which nothing else in the universe has been able to do.

Seriously. There are at least a dozen of patents to register, and quite potentially, these coders are in line for a brand new Nobel Prize in Computer Science.

And, as far as understanding the inner workings of Seventeen in the simplest possible terms goes, this is it. Obviously, there are a lot more details and nuances to get into, and while Python and Ren'Py are documented and therefore, you can research them in your own free time from reading this guide, I will, by necessity, have to explain the basics of The Bytecode, and by "basics" I of course mean "enough for you to understand how certain aspects of DDLC work". As it happens, getting started with The Bytecode is considerably more difficult than getting started with other programming languages, and any sort of teachings on The Bytecode might take a while to come - if they ever come.

However, that is, I would say, Advanced Stuff, and for now, let's just briefly unpack the other game that falls under the DDLC umbrella.

[020G] TEMPORARY CHAPTER: LOOKING FOR A GLOSSARY?

Glossaries will be moved to their own section, much like the non-chron blog. In the meantime, old glossary chapters will be kept on selfhost until I deal with them.

[0210] DDLC PLUS: BASIC TECHNICAL INFO

Doki Doki Literature Club Plus! (most commonly shortened as DDLC Plus and less frequently as DDLC+) is the second title by indie game developer Team Salvato, co-developed and published by Serenity Forge, and was first released on June 30, 2021 at 17:00 UTC (a date that is also significant to the hacker calendar). While this game is also available for Windows, it drops the Mac and Linux support; however, instead, it adds support for various consoles, including the Nintendo Switch, PlayStation 4 and 5, Xbox One and Xbox Series X|S. Each platform's version of DDLC Plus is available as a digital download for US$15, and both the Switch and PlayStation have also received a physical release, which costs US$30. This time, listing all the storefronts is going to be a bit more of a hassle, but bear with me:

This is only going into the digital releases; for physical releases, honestly, you can expect most major retailers, both of the video game kind and of the kind that provide pretty much everything, to carry a copy, or if they don't carry a copy just yet, let you preorder.

Lastly, though this might come as a surprise, Linux users aren't actually screwed. Given that Steam integrates Proton Experimental, most video games, including DDLC Plus, work pretty much flawlessly on Linux, and allow you to never touch Wine.

Can I just say that Wine is the single largest deterrent for switching to Linux? You know, people miss their Windows software, and while one could tell them to look for libre alternatives, or to inform them of Proton if they're gamers, instead, inevitably, Wine gets brought up - and it's honestly a miracle how finicky it is to set up, to say nothing of the fact that its results are far more hit-or-miss.

Anyway. Why do I keep getting sidetracked about operating systems when I'm supposed to be describing the DDLC games?

If you were expecting some sort of intercompatibility between the Windows version of DDLC Plus and the console versions, well, there is none, and even something on par with Wine would be a godsend. However, for the most part, consoles don't give you access to the file system anyway, and if you're daring enough to have installed a custom ROM onto your console, then chances are, you're not going to have much success playing the games designed for the original hardware and software.

At any rate, the track record of Serenity Forge, as a game developer, so far is by no means impressive - DDLC Plus might just be their biggest-profile release yet - but it is not nonexistent like Team Salvato's is, as Serenity Forge has, for one, developed a Cyanide and Happiness tie-in game, among others. However, for the purposes of this essay, you can treat "Serenity Forge assistant programmers" as a unit; something which has the Experience of developing and publishing a video game on consoles, and able to assist Salvato, a lone coder in a big world (ha, ha, haha, as though that's the case in reality).

Anyway. Besides "Serenity Forge assistant programmers", who are a single entity in the exact same way that "Dan Salvato" is a single entity, and anyone else mentioned in the Seventeen section, the contributors to DDLC Plus include:

  • Nikki Kaelar a.k.a. Varien [she/her], the composer of the new tracks used for the Side Stories.
  • SquChan and LucidSky [pronouns indeterminate], the artists of the new CGs used for the Side Stories.

And that's it. Clearly, the whole operation of actually writing the story and making the art and music for it is still made up of a handful of people, in true indie fashion.

As far as the programming languages go, The Bytecode still figures extensively in Plus, expanding its dialogue-generating capabilities to various other languages, but this time, the base engine of choice is Unity, not Ren'Py (most likely a necessity for porting to consoles). That being said, while Seventeen was a tremendous technical achievement for its time, Plus doesn't really add (get it) anything new in comparison, other than the Side Stories and an OS-like environment to explore. Hence, most hacker exploration, even with Plus, focuses on Seventeen, and the only purpose of Plus in the long term was to introduce a new generation of DDLC fans.

I will mention differences between Seventeen and Plus as they come up, but if I haven't specified those differences, it's safe to assume that the handling of them between Seventeen and Plus is identical.

[0220] DAN SALVATO: A BRIEF HISTORY

As far as I know, there's no such person. Clearly, there's someone pretending to be Salvato, as "he" has various social media profiles over the years, but trying to unpack those will not lead to any useful knowledge gained.

Hey, since Plus introduced poems that we can actually quote, let's quote one.

The Lady who Knows Everything knows what I am thinking.
Before I can speak, she responds in a hollow voice.
"I have found every answer, all of which amount to nothing.
There is no meaning.
There is no purpose.
And we seek only the impossible.
I am not your legend.
Your legend does not exist."

  • Monika, "The Lady who Knows Everything"