u/NotXesa

This plugin allows you to expose child properties onto their parents (or grand-parents, or grand-grand-parents...). To do so, you just have to export the properties using custom hints and flag the node that has to show those properties either by declaring a constant in their script or setting up a metadata key in that node.

I use it to have all the important properties of my components in just one place without the need of going through all the nodes in the scene until I find the one I want to modify.

You can find it in the AssetLib and in GitHub.

EDIT: the version from the AssetLib has a bug that causes the plugin to fail when loading. Until they approve the hotfix, you can use the version from GitHub. Thanks to u/Crvsator for pointing out!

I like to add the name of each animation in the spritesheet, so when I have a lot of animations I know which one is each. I manually do this by adding an extra frame before each animation and just add text to it.

But that's not convenient because when I want to preview the animation in aseprite there's that extra frame playing too.

Is there any way to add tag names when exporting the spritesheet?

PD: ignore the repeated sprites, they're just placeholders.

Is this a bug? It kept saying that I couldn't generate more images even if I didn't generate any in the last few days. I then said I didn't reached the plan limit and it just made the image.

I have this character that can control other objects telepatically. At first I implemented the most simple version of this: while the object is being controlled, its position gets modified by the player's position. Easy, right?

Well, that leads to a lot of unwanted effects and it doesn't let the player stack several objects on top of the controlled one. So I started tweaking the system and the more I went into it, the worse the results were.

The main problem was that Godot's physics engine made the boxes to sink when they were going up, and it let a gap when they were going down. As a result, the engine didn't detect that the box on top was colliding with the box underneath, and therefore boxes on top would not move accordingly because there was no movement propagation.

Another problem is that, as you can see at the end of the video, there is a platform that only goes down when a certain amount of weight is put on top of it. That platform asks the objects on top about their weight and at the same time those objects ask the objects on top of them about their weight, and so on. Because of the previous problem, when the platform started moving down, a gap between boxes would appear and the weight propagation would stop, causing the platform to go up until the boxes stacked again. That caused a loop where the platform would go up and down each frame.

I learnt that CharacterBody2D and AnimatableBody2D can be moved "manually" and then update the physics server to let it know that they are actually in another position, so collisions and slides work propery. That would have been perfect because I could just snap their position and that sink/gap would disappear. Guess what: that method just doesn't work except for StaticBody2D.

So I ended up switching everything to StaticBody2Ds and coding all the movement, collision and slides logic by myself.

It's been a painful journey, but at least now I could make a pizza delivery game if I wanted :D