synopsis & status

STATUS: ingame art. ENGINE: Ren'py. RATING: Mature (13+). STARTED: 2020-ish. "What do the NPCs in CYOA games do? what do they want? They have more power over your story than you'd think. Inspired by games like DDLC. // You finally arrive back at your small but cozy apartment, only to boot up your PC and realize you have a new executable on your desktop- curious and dumb, you click on it and it turns out to be a dating simulator, made by a secret admirer that is! Will you be able to find out where the game came from, who made it, and why? Or will you leave with more questions than answers from the ingame story? // GAMEPLAY TYPE1 (only in full game): sleuth through the games files, decipher binary, go to mysterious (safe) links, listen out for morse code in each ending, and look into the symbolism- great replay value, its guranteed you won't figure out the entire story in one playthrough, or even three! Infact, the true ending is open ended to be decided by the player! There is no correct way to view the true story- the only requirement is that you must do Command's route. // GAMEPLAY TYPE2 (only in full game): pursue the digital girl (or boy) of your dreams! Whether it's the chronically tired and recently demoted Antivirus, the bubbly and popular Command (who also has a seemingly timid little sister, Prompt! Prompt is NOT a romance option, as she's a minor, but she's still a main character platonically!), the laidback and mischievous Firewall, or the retiring and dad-friend Ethernet (each has their own route in full version)- be careful though, Command isn't keen on sharing. // GAMEPLAY TYPE3: don't romance anyone, and instead take Prompt under your wing- she's always so quiet and skittish, it makes you wonder, was she always like that or is there something more?"

Using this abomination (incase i forget ^^")

Is this annoyingly complex? Yes. Is it still easier to parse than a real Tumblr theme? Also yes.

Adding blocks

There is a very specific element wrapping pattern you need to follow for the styling to look correct. Usually, you'll probably be splitting your page into sections, so use the <section> tag with the "post: class with the following structure:

<section class="post">
<div class="article-content">
THIS IS WHERE YOUR TEXT ACTUALLY GOES
</div>
<footer class="article-footer"><div class="date">Optional footer line, you can put a date here. Delete if not using</div></footer>
</section>

There are two scenarios where you don't want to use section: if you're doing an actual list of blog posts, each post should be wrapped in an article tag, so use <article class="post"> instead. If you're just using the boxes for stylistic purposes, use <div class="post">. (If you're not sure whether that's the case, you should most likely use a regular div if there's no header at the beginning of the section.)

Image posts

You can add a main image to a section by putting it in front of the article-content element. It will separate the image from the rest of the "post" content like in a Tumblr image post. If you want inline images (i.e. the image is inside the box), you can just add them normally.

<section class="post">
<img src="IMAGE PATH" alt="ALT TEXT" class="postimage" />
<div class="article-content">
THIS IS WHERE YOUR TEXT ACTUALLY GOES
</div>
<footer class="article-footer"><div class="date">FOOTER</div></footer>
</section>

synopsis & status

Using this abomination (incase i forget ^^")

Adding blocks

Tags

Image posts