Hello) Haven't seen nice videos exploring hierarchical state machines, so I decided to share my tutorial here. In the video I break down one of Dark Souls III bosses and then use Godot to recreate it.

Originally posted by [email protected] and posted here with permission from them

https://mstdn.games/@doomski/112820238014617819

Hey, just wondering if anyone had any particular recommendations for specific channels they especially liked?

I've recently been watching some Inkscape tutorials by the channel Logos by Nick and I really like his presentation style. Instead of going into detail about how to do something in particular he'll just make something and on the way you're introduced to multiple features and techniques you didn't even know existed. Very useful especially if you aren't familiar with the software at all ( me )

So if you know of anyone like that for Godot, or any channels that you particularly like, or any particular videos, please post them, I'd be interested in having a look.

Going to start doing some daily Godot tips, both to force me to look for cool things the editor does so I can use it myself and to help out anyone else

Also posting these on my account on https://bytes.programming.dev

If youve got any tips I can put for a future day feel free to give me it and I can queue it up if I havent already

Hi everybody! This time I would like to try something really simple. It is one of the simplest fractals that you have probably seen before, and it is called the Sierpiński triangle. This code can demonstrate simple transformations and also model the resulting effect by removing pixels in each iteration. So let's get started.

• Kolokol
• JumpMap
• Bosca Ceoil
• Bloodthief
• Yarn Guardians

Exactly what the title says. It's under MIT lisence and currently being approved by the moderators of the AssetLib. The project is currently very simple and contributions are very welcome! !image of the tool window

Hi everyone! This time I would try something in 3D. It will be quite a simple thing, namely creating a tunnel from a texture, but even something as basic as that can sometimes be useful. And who knows, maybe I'll like it and next time I'll make something more sophisticated. So let's get started.

cross-posted from: https://programming.dev/post/16870410

> > However, despite all the attention Godot has been receiving, the switch from Godot 3 to Godot 4 called for the removal of Godot’s visual scripting system. This presented us with an amazing opportunity. We knew we needed to provide more to our users, and now Godot was lacking in a function that we know really well! And that’s how the current plan was kicked off. > > Makes me wonder if they'll do something similar for RPG Maker if AGM does well enough commercially, since the RPG Maker Unite, which was supposed to work with Unity, died thanks to that charge the devs per-install kerfuffle.

The fediverse canvas event is starting in a couple hours (event similar to r/place) and similar to last year I figured we can place the godot logo on it!

Canvas is an event where everyone can place a pixel every so often on a shared canvas. This can overwrite previously placed pixels which can lead to communities fighting for space on the canvas

You can find the link to it here: https://canvas.fediverse.events

I set up a template beside the main programming.dev area that you can find from the below links. This can be edited if theres another godot design people like more but figured it was a good start. For real time chatting im active on the programming.dev discord and matrix

one to one template: https://canvas.fediverse.events/#x=423&y=472&zoom=5&tu=https%3A%2F%2Fbytes.programming.dev%2Ffiles%2F4ce62a78-1476-4842-a2df-fcb84049a52a&tw=44&tx=386&ty=429&ts=ONE_TO_ONE

dotted template: https://canvas.fediverse.events/#x=423&y=472&zoom=5&tu=https%3A%2F%2Fbytes.programming.dev%2Ffiles%2F4ce62a78-1476-4842-a2df-fcb84049a52a&tw=44&tx=386&ty=429&ts=DOTTED_BIG

Hi everybody! During the development of our point-and-click adventure game Whispers of Prague, we played around with the idea of creating some scenes in complete darkness, so the main character would need to acquire night vision goggles to navigate the scene. This idea was eventually discarded, but the effect itself isn't entirely bad, as you can see right now. Let's take a look at how such a shader works.

Hi everyone! Do you remember the Sobel operator that I used in one of the previous videos for edge detection? The shader that I will demonstrate today will be based on a similar principle, and its result will be an equally interesting effect. Let's take a look at how the algorithm for the emboss filter works and how to implement it as a shader.

Hi everybody. This is the second part of the mini-tutorial on creating 3D asteroids or other rocks in Blender and using them in Godot Engine. This time, I will focus on the Godot Engine, namely importing an already finished model into Godot and resolving subsequent issues. If you're interested in the modeling itself, I recommend watching the first part first. Now, let's dive into Godot.

Just learned about this today :D

Hi everybody! Would you like to know how to easily create a screenshot in your game using the Godot Engine, whether it's a 2D or 3D game? In this short video, I'll show you how.

> A screenshot of some of the current Godot gold level supporters. The one supporter highlighted has chosen the name "TaraSophieDev (pls fix #43093)"

The issue is still open! The merge request seems to be almost ready. Though there hasn't been any new development since May.

That intro though.

Hi everybody! I know I often say "Let's make a quick video about a simple effect" and then I usually end up talking about it for over 20 minutes. But this time I hope I'll finally manage to make a shorter video because today's effect is really easy, as you can see in the background.

I'm curious because GDScript sounds like a very high and good abstraction for the engine.

> ### Dynamic nature > > Pros & cons of dynamic typing > > GDScript is a Dynamically Typed language. As such, its main advantages are that: > - The language is easy to get started with. > - Most code can be written and changed quickly and without hassle. > - Less code written means less errors & mistakes to fix. > - The code is easy to read (little clutter). > - No compilation is required to test. > - Runtime is tiny. > - It has duck-typing and polymorphism by nature. > > While the main disadvantages are: > - Less performance than statically typed languages. > - More difficult to refactor (symbols can't be traced). > - Some errors that would typically be detected at compile time in statically typed languages only appear while running the code (because expression parsing is more > strict). > - Less flexibility for code-completion (some variable types are only known at run-time).

Additionally, the interesting thing for me, it resembles Python > It uses an indentation-based syntax similar to languages like Python. GDScript is entirely independent from Python and is not based on it.

and because I come from Rust, this is mind-boggling for me:

Memory management

> Godot implements reference counting to free certain instances that are no longer used, instead of a garbage collector, or requiring purely manual management. Any instance of the RefCounted class (or any class that inherits it, such as Resource) will be freed automatically when no longer in use. For an instance of any class that is not a RefCounted (such as Node or the base Object type), it will remain in memory until it is deleted with free() (or queue_free() for Nodes).

The mine is Dome Keeper. I linked what's coming soon to this fun game!

Hi everyone! I always wanted to create this kind of effect with running lines, but I didn't know how to do it before. Now I finally know, and since it's a relatively simple algorithm, this video won't be extremely long either. Let's start with the tutorial.

For character abilities that have a certain trigger condition, eg. "OnAttack", "OnJump", "OnDamaged" etc..

Currently each of these triggers is a signal. When a signal fires, the character loops through all of its abilities and activates each one with that specific condition, so it just runs an if statement for every ability, regardless of whether it has that condition or not:

if ability.trigger_condition == Triggers.OnAttack: ability.activate()

My issue is that this could get a little unscalable with many characters on-screen each having many abilities of their own. A character could have 1 OnDamaged ability and 19 OnAttack abilities, but when an "OnDamaged" signal is received, it will still loop through all 19 OnAttack abilities.

Any advice on this is appreciated, thank you all.

I'm learning as I go. Proud of getting some interaction with the environment working. Still lots of bugs to sort out, especially player and camera movement!