Here lie some bits that were cut from the game, and a few words about how it was made.

Mid July, strangest io go “yo, what if videogame”, i go “aye”. Then I enter into a big cartoon tumbledryer and emerge roughed up around mid October. By that point the design and pre production are done and i just do production during reading week in college while getting intoxicated. Then i hand off the files to strio, and they do the rest of the visual magic!👉👉

Initial designering!

There were a bunch of things which were planned but never done! Some ideas that didn't make the initial cut were:

Then i was trying various ideas that were not made, one of which was the video sokpop made on the fake 3d in gamemaker, i thought “oh hey, leaving a trail behind you is easy to do in code and then later interacting with that trail is kinda fun”. So i tried jumping over it for a bit and that didn’t go anywhere, the diagrams got weird. It’s kinda obvious with the answer spelled out right there what would end up being
the game but I had  to think about the options that didn’t work out too :(

I thought that i could generate some points near your previous body path for you to interact with your past movements but that smelled a bit jank after testing it out on paper. (which hey, when you re making a game that looks like this and plays like that it’s super easy and fun to test on paper actually!)

At some point Counterclockwise was brought to my attention https://www.youtube.com/watch?v=Bl-82znkRc0 and by association https://archive.org/details/zx_Knot_in_3D_1983_New_Generation_Software, which i salivated over plagiarizing for a bit before reconsidering.

So anyway, the third dimension was cut due to not adding much to the game but being harder to do. Also most of the interactions would be hard to detect consistently or didn’t have fun discrete results.

I thought about what to do with 3d for a bit, considered doing it swooshy so you weren’t tied to one surface and could choose between 2 but didn’t know how to show clearly where you are or what you'd collide with on playdate type 2 tone graphics.

Intermediate designering!

Thought about design and various ways to spin this specific version of it and had to cut a bunch more stuff
Some rejected futures:

Research? not really

Anyway after messing around with design more i talked to strio again, read the census, did some research on what games were already out there and decided that some optional other things i might wanna do are:

• small play sessions & ability to jump right in
• instructions immediately present but not intrusive 
• self directed difficulty  (fun design challenge, kid friendly(turns out playdate parents are common) without sacrificing wider gamer appeal)

By that point the design was pretty much nailed down and just needed the edges filed down. Played around with the graphics a lot during development, had to tone them down when i got my hands on a real console cuz it was not up to the task. 2X mode to the rescue! + had to do tons of optimizations. 

Cool tech!

The whole game saves your trail to a bitmap and then you collide with the bitmap when you move, but theres 2 of em, 1 per layer (there were 4 of em but then shadows were removed). Actually theres not one but a fuckton of bitmaps, like a whole table of them and every time you move the game only checks your collisions with the nearest ones and only uses them to display the game! Or thats how it would’ve worked in a good world where i actually optimized the game right!The way it works now is still pretty cool tho! I’m pretty sure you can go up to ridiculous map sizes and your movement on them will be linear complexity, but the zooming in itself will get exponentially longer as the game has to rerender the entire past snake in 2x of what it was saved at.