Piero Bosio Social Web Site Personale

@eniko When I was using it, I didn't even know what a compiler was. And if I left the machine on for more than an hour, it would overheat and begin randomly flipping bits.

Enforced breaks, probably should be part of modern machines too.

@eniko Wow, this sure brings back memories. QBasic...

@stylus Ahah, you are 100% right, that works fine.

Maybe that should be part of the "fatal parser error because it will return null and that apparently is a fatal parser error" message.

It is unimaginably stupid, but the only workaround I could find was to have an "export var body:RigidBody3D" and then assign it ITSELF in the inspector.

Can't even assign it in code, not using the techniques I know.

This is sad.

This wouldn't be an issue if Godot had interfaces and I could have Array[ControlInterfaces].

OK, #godot question. I think this was a recent change, I remember it working before.

Since all Godot scripts are layered on top of a node type, it's quite possible to assign a script that descends from "Node3D" to a more specific node - say, "RigidBody3D".

I want to say "if self is RigidBody3D:" and have logic.

However, Godot IMMEDIATELY red-flags it. As a parse error. A PARSE ERROR?! It parses fine, what a whiner.

Anyway, how do I do it?

@eldritch48 Oh, true!

@eldritch48 ingress and egress too!

@eniko That's right! Before you create a player model, you have to create a stupid memeworthy descriptor for your default model. Like... "Steve"... but not "Steve", that one's taken.

@eniko Are you taking a reverse shot with the player in the frame, for basic mirroring? Either way I think this could be a lot of fun, a structure that shows what is behind the viewer allows for a lot of new builds.

I love how every communication from a company these days is "we remain committed to being ethical good guys, so we are introducing a change to our service where fuck you, go die in a fire."