Make sure you get back out before the next storm or all progress is lost. PvE, maybe PvPvE, but combat is secondary.

I'm a #godotengine solo dev myself and you can bet I'll be studying your mechanics to help inspire me. Keep up the awesome work

But it wasn't a total waste of time.

I learned how to create additional viewports (hard to figure out what's wrong with your rotation math from the camera point of view) and how to drawn in only specific view ports. Not to mention a bunch of practice with doing vector math :)

While convenient for pan and zoom, for orbit, I need to precise control to match the position and camera rotation changes. So back to manual calculation of body movement and collisions.

You need LLMs to sound confident, so as to foreshadow the promised AI that these companies are basing all their fundraising on. Otherwise, how can you justify those valuations?

And that authoritative voice is no accident. It is a direct result of AI companies desperately trying to draw a line from LLMs to first, the mythical AGI, and now, with moved goal posts, to SI.

Except people wouldn’t take their searches as authoritative while chat bots will give you their version with an air of full confidence.

You might say this is a semantic quibble, but for right or wrong people will rely on that authority which makes them highly problematic.

AI companies are raising and spending billions, but not on the creation of knowledge but only on consuming it and then passing the result off as their magical thinking box.

No, what bothers me is that the answer #Claude generated did not come out of a vacuum. It is based on training on lots of code and writing that people have expended tremendous energy on and there's absolutely no attribution.

Nor do I feel like I'm working with the enemy that will steal my job in another couple of months. I think AI will change the landscape but just like every "programming without understanding programming" before it, it will end up underdelivering.

What has me conflicted is not that I didn't write it all myself. I would have been just as happy at finding some MIT licensed code and adapted it.

I started to adapt this code to ArrayMesh and got a little lost in the docs so I thought I'd ask Claude to rewrite the code using Godot's ArrayMesh. This code had a number of syntax errors, but still pretty decent. A little clean-up later and my own test scene rigging and it was working.

So I asked about generating me some C# code using Vector3. Also good. How about normals, tangents and UVs? Still very coherent legible code.

I am conflicted about how I arrived at the deformation code. After my normal google-fu let me down, I decided to give #claude a try. First I just asked about an algorithm for lattice deformation of meshes. That came back with a cogent answer.