Career progress, improving mental health, finding a life partner, traveling, upgrading your home or vehicle.  These seem like the usual go-tos.  I don't see why you need to have a goal though.

I'd settle for beating Scorpion who freaking cheats

The Iguana designer menu is really cute looking.

Nice umbrella

That was fun!  One of those keys was real mean.

The game reminded me a lot of Ittle Dew, since the paths you can take branch depending on the spells you unlock.  I finished in 49 minutes, though didn't get the true ending.  I have some guesses as to how that might be done, but I'd need to play around more.  I'm a little worried that I need to beat it deathless based on the ending message... but that's probably not going to happen.

Cool game!  I think it's real nifty that you're still releasing freeware projects after all these years, chuchu.

Funny, the backlog burner event that I created this bingo card generator for just wrapped up today.  I expect we'll bring it back in November for the next one.

You could've added your bingo-related games to the bingo card.

I finally played through Hollow Knight some months back and really enjoyed it.  Just a marvellous game.  I do enjoy metroidvanias but they can also be a bit of an investment sometimes, so I'm always a bit hesitant to start a new one.

I'm not sure if Maddy's older games are harder than Souls titles or not.  They're very precise and that would be difficult for a lot of people.  On the other hand, Souls games (at least the more recent ones) are more reaction-based, and that presents its own difficulties.  I think either could be difficult for people with low motor control, but both skills can also be improved through practice.

I've played so much of both that I really don't have that beginner's context necessary to evaluate it fairly anymore.

I played through Celeste 64 after finishing the C-Sides in the regular game.  I really liked the Mario Sunshine-esque stages.  Overall though I was content to put it down after the hour or two I spent with it.

I saw one of your SM64 runs on my Youtoobs.  I recognized some of the tricks, like the backwards bomb carrying.  It seems like a tricky but very fun game to learn speed tech on.

I like writing ES6, but have basically been a curmudgeon about learning the new school way of doing things with frameworks, build steps and bundlers.  I'm not completely new to them since I used preprocessors back in the day (remember LESS/SASS, gulp/grunt, Bower, and Browserify?  No?), but I basically fell off after things moved in the direction of Webpack.  I didn't like how much "magic" it did versus the clearly defined build steps of gulp.  And the fight over CommonJS vs AMD didn't have a clear victor yet, so I was hesitant to invest in either world (turns out they both lost).

Anyway I was working on a side project, and found I was needing to dedicate a lot of code to managing state and keeping the page in sync with local memory.  It was getting messy.  On top of that I had a few different modules that were effectively pages each needing to share information, each with a UI setup function, and with a switcher function to swap between them.



Rather than try to refactor that mess into something more elegant, I decided it was time to start learning Vue.  Any of these state management libraries probably would have worked, but Vue offers an easier start and two-way data bindings.

So far Vue is pretty cool.  It's nice to have more declarative logic to the template, and definitely makes things easier to reason about.  Instead of defining a bunch of dynamic elements in JavaScript, just create them in HTML and slap on some magic attributes.  It's often less code, but more importantly it's easier to parse at a glance.  I was already making use of modules but Vue single-file components feel like a nice extension of that concept.

I still need to rewrite my app, but I think I've got enough of the foundations down now that it shouldn't be a problem.  I'm still keeping the stack pretty slim with just Vue 3 + Vite.  Might introduce Vue Router if I can find a way to make it work with GitHub pages (hijacking the 404.html maybe?).

I expect the experience should be relatively transferrable to React or other frameworks.  Especially if I start picking up the Composition API.  So far I've mostly stuck to the Options API since it's used in the documentation I've been following, but I'm thinking that's mostly just a difference in syntax.

Anyway there's still over 9,000 other JS tools I haven't learned yet, but this seems like a good start.  Pray for my hard drive as it bears the brunt of node_modules.

I started it last night actually.  Played the first three chapters then was too sleepy to continue.  Enjoying it so far!

Finished it now!  Game gets tough in the final chapter and the C Sides.  Lots of fun though, and super polished.

Also, are you seeing what I'm seeing?