Continue work on my map-based WW2 Pacific submarine sim Silent Shark https://silentshark.app - I just added lifeguarding missions and am going to do my first ever "developer broadcast" on Steam tonight for the Steam Next Fest and hoping I don't screw things up...
I've been pleasantly surprised at the community beginning to get excited about the game.
If you look at the trajectory of your stance, do you think you might reach "Uh-oh this is doing just as good a job as I can do in a much shorter time?" within the next year? I feel like that's what happened to pure coding for me, something I never ever thought would be possible.
The unreliability is something that seems like it might be a temporary early stage.
My teenage son has held multiple LAN parties this past year at our house. They are far from dead, just maybe not quite as widespread as they used to be when I was his age.
It's taken about 3 months of my spare time (some evenings and a few weekend afternoons) so far.
> Is any of it vibe-coded?
I actually started the project back in February as an experiment to train myself in prompting and to see how far I could get using Codex and letting it do literally all the coding for me. It turned out, I could go all the way. I have not touched a single line of code myself (I have only tweaked some CSS from time to time).
This project has led me to realizing my 20+ years of professional experience in coding are clearly worth far less than they were just a couple years ago...
> As you already stated, the browser version is a Vite/TypeScript app, but what programming language is the actual game in?
The actual game is written in TypeScript. For the Windows/Mac/Linux/Steam Deck/iOS/iPadOS/Android builds I'm using Electron to package it (which has surprised me for how well it's working even though I always kind of hated Electron...)
I super appreciate this feedback and don't at all take it as overly negative.
I have gone back and forth on whether to describe how to use the tools or instead to explain goals. I get what you're saying and will give this more thought.
(And the fact remains that with this many tools, it's simply really challenging to explain it in a clear and elegant way on a small device.)
Once you "get it" and know how everything works, then I think it can work well...but for something this complex, the issue is definitely going to be onboarding.
Thanks - yeah this is a tricky problem since on the one hand I don't want to frustrate users not being able to pause/unpause but on the other hand I need to not let them unpause too soon and have the ship be in the wrong position.
Currently it should be blocking unpausing until step 7 or so... and it also should auto-pause once the ship reaches step 8(?). I did both of these things for the reason you're saying, but maybe I need to do it even more "locked down", at least for the Basic Tutorial.