My playthrough (in conversation with the work of Riwhi Kenny),
Imagine a square, place a skull and the rest of a person in the middle of the square, in a throne, elevated to height the word satisfying sits with. You should have bones and throne in frame. Asset strip npc pathing code and train a model on that. Seed the model with a prompt by ...naming the prompt field something people will understand (e.g. the breath of life); ...seeding this field a demeanor, ...and harvest what you recognize from your result. Each season, you should have one new pathing code. Create new seasons for parallelizing path generation. Give each path an entity, name this something people will understand (e.g. River), and give River the pathing.
Make a bunch of rivers. See this example:
[hydrological map of turtle island]
See how the spaces between are everywhere River is not? Let this receive the light of the skull throne. Set Skull throne luminosity to some amount between 0 and 1 (see hands for details), and give ray tracing one of the paths you generate, and then populate that an arbitrary amount of time. Distribute this across all of space river isn't by setting this space into a sphere:
[naïve spheriod filter of the previous hydrology projected all to hell on a sphere with settings provided]
Let where River paths cross thrown carry aways one of the generated paths of light - you should have two paths: the light path and the water path. Water faggots have demeanors that start with special characters (e.g.: ҉faggot), light faggots have demeanors that start with alphanumeric characters (e.g.: Sky).
Until skull throne collapses, watch how light faggots stab the skull throne. Feel free to say the light has formed games for it, such as:
Knife Throne
You have two stats, etc.
Say, light paths like the Righteous feel the way to stab the treatrous correctly is: through. We may understand that bones only glow when you stab them with light, transfixing other light paths, which might give their light elsewhere, to give their light, instead to stabbing the bones as the elipsis in the sphere of 0.99...9 illumination grows and grows, letting there be light. As light passes through this sphere and radiates out, it falls in random directions. Let's call this direction something we will remember (e.g. straight "|" not cishet), and is a function.
Functions, you well understand, a refresher: fuctions are the directions of fields of view. Each field is made up of points of light. These are called by their name, like Sky, above. As River illumination grows from the path of light, it forms stone. Stone settle to River's bottom. Name each stone as it forms (e.g. Word "⌒" not what). As an aligning of a name is inherently a longer process than the direct path of light, some stones are still to be named by a River as is made evident by all of the ripples in a River. To each stone refer to what is the word.
Continue in this way until all Rivers are stone. The next section will cover known bugs. These arise in times such as the shadow of a name, where a River is displaced, forming a shape like cupped hands. Where this shadow is cast in a loop, name the loop something memorable (e.g. moss "🦠" not mitochodria) and get back to throwing stones names. Loops that harmonize are known to form. Name this something memorable and move on (e.g.: spit "ꜛ" not dead). Untl harmonic loops die, they will be animated, describe their pattern, name them something that recognizes them all (e.g.: discovery "ʔ" not capture) and hopefully the way we allow ourselves to be discovered leaves your attention wild, free to do something other than stare at what attention sumLight has destroyed.
Other known bugs may be found in any comments below. Thank you for being
-c.
/end playthrough -- thank you for the lovely game!
← Return to memory protocol
Comments
Log in with itch.io to leave a comment.
Been looking for something like this. It's now high on my wishlist.
This is so hot. I would kill to play this with somebody. Great job!
Nice 🥺
My playthrough (in conversation with the work of Riwhi Kenny),
Imagine a square, place a skull and the rest of a person in the middle of the square, in a throne, elevated to height the word satisfying sits with. You should have bones and throne in frame. Asset strip npc pathing code and train a model on that. Seed the model with a prompt by ...naming the prompt field something people will understand (e.g. the breath of life); ...seeding this field a demeanor, ...and harvest what you recognize from your result. Each season, you should have one new pathing code. Create new seasons for parallelizing path generation. Give each path an entity, name this something people will understand (e.g. River), and give River the pathing.
Make a bunch of rivers. See this example:
[hydrological map of turtle island]
See how the spaces between are everywhere River is not? Let this receive the light of the skull throne. Set Skull throne luminosity to some amount between 0 and 1 (see hands for details), and give ray tracing one of the paths you generate, and then populate that an arbitrary amount of time. Distribute this across all of space river isn't by setting this space into a sphere:
[naïve spheriod filter of the previous hydrology projected all to hell on a sphere with settings provided]
Let where River paths cross thrown carry aways one of the generated paths of light - you should have two paths: the light path and the water path. Water faggots have demeanors that start with special characters (e.g.: ҉faggot), light faggots have demeanors that start with alphanumeric characters (e.g.: Sky).
Until skull throne collapses, watch how light faggots stab the skull throne. Feel free to say the light has formed games for it, such as:
Knife Throne
You have two stats, etc.
Say, light paths like the Righteous feel the way to stab the treatrous correctly is: through. We may understand that bones only glow when you stab them with light, transfixing other light paths, which might give their light elsewhere, to give their light, instead to stabbing the bones as the elipsis in the sphere of 0.99...9 illumination grows and grows, letting there be light. As light passes through this sphere and radiates out, it falls in random directions. Let's call this direction something we will remember (e.g. straight "|" not cishet), and is a function.
Functions, you well understand, a refresher: fuctions are the directions of fields of view. Each field is made up of points of light. These are called by their name, like Sky, above. As River illumination grows from the path of light, it forms stone. Stone settle to River's bottom. Name each stone as it forms (e.g. Word "⌒" not what). As an aligning of a name is inherently a longer process than the direct path of light, some stones are still to be named by a River as is made evident by all of the ripples in a River. To each stone refer to what is the word.
Continue in this way until all Rivers are stone. The next section will cover known bugs. These arise in times such as the shadow of a name, where a River is displaced, forming a shape like cupped hands. Where this shadow is cast in a loop, name the loop something memorable (e.g. moss "🦠" not mitochodria) and get back to throwing stones names. Loops that harmonize are known to form. Name this something memorable and move on (e.g.: spit "ꜛ" not dead). Untl harmonic loops die, they will be animated, describe their pattern, name them something that recognizes them all (e.g.: discovery "ʔ" not capture) and hopefully the way we allow ourselves to be discovered leaves your attention wild, free to do something other than stare at what attention sumLight has destroyed.
Other known bugs may be found in any comments below. Thank you for being
-c.
/end playthrough -- thank you for the lovely game!
Been so excited for this release. This one's for the hypno freaks