ConfuSomu

one of the many twilight sparkles

gender is a mess, maybe something like (genderfluid) transfem enby, but like: horse! gay! girl!!

:eggbug: 🏳️‍⚧️

name-color: purple


my website (with contact links)
twilightsparkle.space/

Corncycle
@Corncycle
coquest!
firefox and chrome only (desktop recommended)
Welcome to my post! Pretty neat, huh? Press A again to close signs!
This thing is so ridiculously hacked together! I'm surprised it's functional at all!
Everything in this post is raw HTML with inline css!
That means I can put anything I want in here! On this last screen I'm going to put the Eraserhead baby and turn you into eggbug!
That's it! Thanks for playing my game :D
Controls:
Use  dpad to move the hero and collect items
Press  A when below a sign to start/stop reading it
INFORMATION
HOW DO YOU MAKE SOMETHING LIKE THIS?
The "smallest" post I found on this site that I had no idea how to replicate at first was this post made by @blackle. If you're able to dissect that post on your own, you'll find that they use the width of a diplay:inline-flex element to "store" a variable that we can access from other elements using calc()!
This is an incredibly clever idea which is the basis of this post. If you understand the css from that post and know how to generate HTML in a programming language, you can probably make a post like this one (not to say that it will be easy, though!)
If you like this post and somehow aren't following blackle yet, you should! It has made various mindblowing posts since then that I can't even begin to understand the creation of.
WHY FIREFOX/CHROME ONLY?
I don't know much about how css is implemented, but in my experience Chrome and Firefox have the most similar implementations and are both widely used. Safari is kind of annoying and requires some special care for some css styling, but this post could work on safari for all I know. I'm just not going to go out of my way to support it. If you are on an iOS device and using "Chrome" or "Firefox" but this post doesn't work on your device, I encourage you to read this article!
BEHIND THE SCENES
I used Python and the xml.etree API to make this post. If you want to see the code that generated this post, you can find it here This code is extremely brittle and I would heavily recommend not using it but you might find it interesting.
You can also see a debug version of this post which (somewhat) shows how it works here.
RESOURCES USED
Hovering animation taken from this post by @oatmealine because I haven't learned how to do css animations yet!
Most sprites from The Legend of Zelda, found at spriters-resource.com
Sign sprite is a recolor of the sign sprite from A Link to the Past
NES controller image taken from this Amazon listing lol (not sponsored, it's just what I found on google)
Eraserhead baby image taken from the "Villains Wiki"


You must log in to comment.

in reply to @Corncycle's post:

I get the strangest bug on the last screen and I have no clue why. In that room the right key just starts becoming harder and harder to press (I have to almost pixel hunt for the button) until flat out unable to hit the right key button on that controller entirely when about ~3 spaces away from the final sign

Oh funny, that was it! For who knows how long, I had cohost zoomed out to 90% and never realized. I must have done that on accident at some point and didn't notice because it was such a slight zoom change.

yep, being zoomed at certain percentages seems completely fine (50%, 150%, 200%) but something like 90% or 110% can break it pretty hard. it must be something about compounded rounding errors since this post has a shitload of calc() calls and percentages like 90% or 110% can't be expressed exactly in binary. glad it wasn't something new i didn't know how to fix :)

I think the strangest thing about it, to me, is the fact that it works perfectly fine until that last screen. That's when specifically the right button goes weird. The area to click it seems to shrink with each press, until finally it is completely gone and unclickable.

i thought inline css was too limited to make one of those css turing machines in. now i'm not so sure. it needs to have state and to be able to choose the next step to apply based on state and that's maybe possible? i still don't know how this post works yet so idk

not sure. when staff rolls out the archival tools I'll look into archiving the posts on my page. if it's not too much work I'll probably put them on my website, corncycle.com.

also the source code that generates this post has been and will continue to be available on my github, though the image links will presumably need to be fixed when cohost's cdns go down

the only other social media I'm at all active on is tumblr but I just reblog stupid posts and never post anything myself. if you use tumblr and want to follow it's @transparent-oprah but it's really nothing like my cohost account

i only created in small spurts here, but this is the only site I've felt encouraged to create my own posts on at all. going to miss it a lot :( thanks for reaching out, I'm a dedicated lurker online but I loved seeing your posts!

in reply to @blackle's post: