I have been occasionally building indie games since the 90's, so a bit of experience mixed with AI coding Assistant. Some things AI really struggled on, others it blitz.
yeah, quite a few people have made the same comment. I should normalise the damage across the different elements so a single element does stop it from being destroyed.
I got stuck on the "push a car into a pool" quest, even with the car directly on top of a pool it didn't go in. The car-pushing physics seem buggy, the rotation direction seems opposite to what it should be.
Cute! But the car challenges in Tier 8 feel undoable -- they're a bear to "steer" and can't seem to go more than a short distance before bursting into flames.
I played on desktop and it seemed pretty impossible tbh. They veer around unpredictably when bumped, and explode long before you can plausibly bump them into a pool. Limiting that to slams would definitely help though!
In the 1990's and early 2000's I loved building web and flash games, people had lower expectations, getting notice was easy (StumbleUpon etc) and there wasn't a lot other choices.
Even worse is I am Australian, I spent a lot of time and concentrating on the left, discussed it with my wife and kids, yet somehow I still got it wrong.
I have been building games since the late 90's, this is the first one I used AI Assisted coding, I wouldn't call it vibe coded as I am in control of the code, the implementation, the decisions, and approval.
I wanted to like it but found it immediately frustrating on mobile:
* The joystick is too sensitive, so it’s hard to keep a straight line, wobbling everywhere instead. The camera makes it worse. I felt that if I kept going I might get motion sickness.
* Despite moving both cars out of the way and getting through, it always marked just one. Took me three resets and had to move Neil back to properly push them and get that done.
* I have played other browser 3D games on mobile but this was the fastest my phone has ever heat up. I didn’t even know it could become this hot this fast, to the point it’s uncomfortable to hold.
Joystick has been improved, I just dampened it down a little.
I will look at the cars, I deliberately added the back and front sensitivity in an early version, it is okay on desktop horrible on mobile.
Battery improvements implemented dropping the load by 90% with a minor change :)
On my desktop, On Firefox, I just got a uniform blue screen. On Chrome, I could turn left or right, but that was all. The W, S, and C keys didn't work.
three.js and Vite, very basic, I set out originally to make a game where Neil knocks over cones and grew it from there. If I was to start again I would use a game engine as it has scaled further than I intended.
76 comments
[ 2.4 ms ] story [ 91.2 ms ] threadAlso glad that Neil is getting the protection he needs (and the public as well) despite the media attention.
In the 1990's and early 2000's I loved building web and flash games, people had lower expectations, getting notice was easy (StumbleUpon etc) and there wasn't a lot other choices.
Even worse is I am Australian, I spent a lot of time and concentrating on the left, discussed it with my wife and kids, yet somehow I still got it wrong.
I am using Codex GPT-5.5 $20p/m.
* The joystick is too sensitive, so it’s hard to keep a straight line, wobbling everywhere instead. The camera makes it worse. I felt that if I kept going I might get motion sickness.
* Despite moving both cars out of the way and getting through, it always marked just one. Took me three resets and had to move Neil back to properly push them and get that done.
* I have played other browser 3D games on mobile but this was the fastest my phone has ever heat up. I didn’t even know it could become this hot this fast, to the point it’s uncomfortable to hold.
https://projects.raspberrypi.org/en/projects/neil-the-seal/0
I started thumping cars but then got into an infinite spiral I couldn’t get out of.
What do you mean by "infinite spiral"?