guillotine | URL shortening hobby kit

We are going to make a custom Node which I'm calling FauxBody2D. It will work a RigidBody2D with a CollisionShape and as an Area2D with the same CollisionShape. And to archive this, we will use Physics2DServer.

Even though the first common ancestor class of RigidBody2D and Area2D is CollisionObject2D, it is not convenient to extend CollisionObject2D. So FauxBody2D will be of type Node2D.

So create a new script faux_body.gd. However, it is not intended to be used directly in the scene tree (you can, but you won't be able to extend its code), instead to use it add a Node2D with a new script and set it extends FauxBody2D.

You would be able to the variables of FauxBody2D and mess with it in undesirable ways. In fact, even though I'm declaring setters, your script would bypass them if you don't use self. For example, don't set applied_force, set self.applied_force instead. By the way, some methods are left empty for you to override in your script (they are "virtual").

These are our firsts lines of code in faux_body.gd:

From your comments, it sounds like you're looking for a generalized way to loop through nested objects and arrays. You'd do that with recursion. If you want to make it possible to collect information, or to stop the operation, in different ways for different places you use it, you can pass in a callback function.

Here's an example:

The .play method returns a Promise, so you can await it to catch the error.

Solved! This was happening because vue-router's createWebHistory() can't hanlde the navigation if the app is not being served. It works on dev mode because vite serves the app but when you build and open the file in a browser it doesn't. So you may say: It is pretty basic, well no... The actual problem was being caused because by the drastical change that vite had at vite@2 and the way the starter-code-templates had to adapt to it. I was using vite with electron, so migrating the starter I'm using was kinda a blinded run. I found that the starter is not serving the file anymore but loading the file directly on the electron main.js, so because I don't know why this is for, I did not serve the file again, instead changed to createWebHashHistory() at my router config and then it worked!