Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

State of the 'styke Q1 2026 Sticky

A topic by Divorce Jonze created 84 days ago Views: 46 Replies: 1
Viewing posts 1 to 2
Developer (3 edits)

Harpy New Year

i've made some clever adjustments that i'm proud of

i have one of the main components [enfilades] like 96% done, working, compiles in C... but i'm struggling getting it to cross-breed with (small embedded (s7)) Scheme so that i can use an interpreter... this has been the missing component that'll complete a huge portion of the work

once enfilades are running, then i can enter cells into memory in the new direction i've been working on since last year

this will enable me to have an entirely new 'file system' on gnu/linux which is actually an 'enfilade cell system' >:D

it would be much, much easier, better, and faster-going if i had some (ie any) income

food stamps are going away and i do not have income enough to match that. i am going to need to eat and sustain my basic needs off of income generated from my work. i've posted quarterly updates for over a year to indicate that i am continuing work on this, and several other projects. i've gotten 0 interaction. i will continue anyway.

consider,
my main competitor still gets over $100,000 / month while i'm languishing in poverty
[arena]

also consider that,
voids aGrift (perform a websearch for 'voids adrift patreon')
is making 130/mo to ship absolutely nothing, has not even made a forum post in over a year

spending more time putting work in on [other] projects... a VN is in the works, and i'm fantasizing about a 'what if TES, but public domain' fantasy commons thing for an mmo type of game... spent some time poking around gnunet which i've mentioned here as a design goal for zipstyke...

making slow progress. i'm a creative genius. share this, pay me. 

thanks,
jonze 

business email 
serious inquiries only,  418 (@) cryspace (dot) space
if thou cans't support in full, consider monthly donations: patreon / studio56
i'm still homeless [https://www.gofundme.com/f/i-need-access-to-housing]

Developer (2 edits)

I did it! I got passed the part I was stuck on!

I wanted a different way of managing memory rather than simply ` malloc(ZZCell) free(ZZCell) I am big brained C 'coder' that took the first tutorial they saw. `

I can now place zzcells into POSIX shared memory... getting to the point where I understand what I'm doing enough to make this happen reliably was a 2 year journey, turns out... but now I have a solid base to work around so that all the 'vapour' has a ground in reality to exist around. there is A LOT of INCREDIBLY COOL STUFF that i've been SUPER EXCITED FOR that has just been enabled... there's still a ton of stuff to fix and add, but the most basic functionality is there, the way i want, the way i have wanted it for it to be just right, THIS WEEK I'm going to nail down the base system, baybee 8D

Like, there are a million 'easy' ways to do this... But there are only a few 'hyperthogonal' ways to do it 'right'... That's what takes the most time, is honoring and revering the spirit of the task at hand rather than put up drywall. Everything is already there in this document but in actually implementing it, it is literally a different computer cosmology, it is a new way of thinking, so most people will get a 'head ache'.

I now have it separate (in my head at least, after coming back to the codebase) between the cli tools that run things behind the scenes, the scripting that calls those tools, and the opcodes that are behind progcells in the zzvim... there was some cross-pollenation in convention... all that to say, now things are a little better organized in my head as far as all the moving parts are concerned, and in the actual repo as well.


As far as 'software direction' I am making this in the style of a decent program, so I am doing the decent thing of keeping logs, debugging, unit testing each function, keeping up with documentation closely alongside and informing development.


the next steps are to add encryption because the goal is to place cells into secure shared memory, having dabbled into GNUNET recently may have paid off as it's libraries may provide what's needed. i will try first with nacl.

then urgent on the backburner queue is mapping KBLANG to NCKEYS, making some simple cell primitives and a dimension viewer, getting my tui up and running... that's what we're aiming for here

then i was #showerthoughts about encoding (as in actual encoding, information theory) sound information using this system... 

so anyway yeah got over that hurdle onto the next one