Godot

I'm curious what happens if you use await for a signal, but the signal is never received? Does this cause some kind of hangup?

For example if I have a function structured like so:

func foo():
    do something
    await signal.finished
    do something else

And the "finished" signal never comes, does the await call just hang indefinitely?

Originally posted about by the godot mastodon account https://mastodon.gamedev.place/@godotengine/111766272068532862

Link: https://github.com/anthonyec/godot_little_camera_preview

Source code: https://github.com/TKperson/badapplenn

It's my first time using Godot, so source code is kinda messy

This project took two weeks of my life. Hope y'all like this

Hey, I am planning on building a co-op multi-player deck builder as a side project, nothing fancy or grand of sorts.

I'm kinda new to this Godot thing, but I kinda get the gist of it. Was always interested in it.

I have prior experience with Game Maker and Unity, so picking up the basics was rather simple, given that I also do programming as a job. So don't simply dismiss this as too ambitious a project to start with when learning Godot.

I just want to ask it out there, are there any advise on how I should structure the code or any advise in general? Just want to be prepared for issues in the future and plan for it.

Basically, my initial idea of the game is think of multiplayer Slay the Spire. But I want a more elaborate upgrade system to the cards, closer to Wild Frost.

For now, my head space for the design is to have:

• Card details, ie names + descriptions + image are resources since they are data that are "loaded in".
• Actual cards that exists throughout the run would be actual nodes, with modifiers as child nodes + Multiplayer spawners to syncrhonise them. Base cards will pull details from the resource and have an empty modifier
  • I previously tried to build it using Multiplayer Synchronizer, but then suddenly realized I can only sync simple properties. It didn't let me create a custom node and synchronize it. Then I had to resort to some ID system for the object which became rather messy.
  • Based on my current testing, Multiplayer Spawner seems to do its job better.
  • Should I use a "modifier node" + children to indicate the list of effects, or an array variable? I'm not too sure when to use the node to organize data vs using an array variable
• The actual cards are stored as a global node, which would be moved to the "playfield deck node" during the gameplay portion

Lemme know if there is some obvious flaw in my approach or if there's a better way to do things. Or if such a project may be too ambitious with the current multiplayer library for Godot.

Especially the multiplayer aspects, since there is not "a lot" of tutorials on it, I feel like there's a few pitfalls that is waiting for me.

TL;DR from the official Mastodon:

Have a TL;DR as well:

• major render pipeline optimization
• improvements in the animation area
• a quality of life change for C# users
• common Nvdia issue solved
• Node & OS documentations overhauled

https://mastodon.gamedev.place/@godotengine/111737132477158649

Hi everybody! What you see behind me in the background of this video is the result of several algorithms commonly used in creating shader effects. Specifically, it involves the Voronoi diagram, a pseudorandom vector generator, and a custom color palette. If you like this effect and would like to use it in your Godot game, keep watching. I will demonstrate and explain how to create it from scratch.

https://mastodon.gamedev.place/@godotengine/111733131695258677

Links: https://nitter.net/godotengine/status/1745100180087546294 | https://mastodon.gamedev.place/@godotengine/111732379516724461

Godot Foundation: https://nitter.net/godotfoundation | https://mastodon.gamedev.place/@godotfoundation

Godot Asset Store: https://nitter.net/godotasset_ | https://mastodon.gamedev.place/@godotassetstore

Godot Conference: https://nitter.net/godotcon | https://mastodon.gamedev.place/@godotcon

Hey folks, I just released my fake OS project after around 2.5 months of working on it. Any feedback is greatly appreciated, thanks!

Get it here: https://popcar2.itch.io/godotos

Source code here: https://github.com/popcar2/GodotOS

Is there something like a node ID which is specific to that node and will be the same no matter how often I execute the game? That would be super useful for saving and loading games.

Hello everybody! In this video, I would like to demonstrate how we can create custom nodes for the visual shader editor in Godot 4. It's a very useful functionality because, despite being a powerful tool, the visual shader editor contains only a finite number of built-in nodes. Sometimes, we'd like to add more nodes that we want to use frequently. It's easy, and I'll show you how to do it right away.

This repository contains a basic project setup along with CI/CD. By default it will build for windows, linux and the web and upload their artifacts, along with deploying a build to GitHub Pages.

Not mine, but this sounds really useful for anyone looking for easy builds and deployment.

TLDW: To have g, r, and s blender hot keys in godot 4.2 click Editor --> Editor settings --> search for "begin" --> use the Plus symbol to set "Begin Rotate Transform" hot key to r, then "Begin Scale Transform" to s, and "Begin Translate Transform" to g. My favorite thing not mentioned in the video is that constraining also works. So you can press r then x and rotate in the x axis or g shift y and translate on the x and z axis.

Hi everybody! It is January 2024, I wish everyone a happy new year, and I'm back with new videos from the world of Godot, shaders, and I'm also planning to record something about modeling in Blender. Anyways, the first video of this year is dedicated to a shader that can be used for interesting post-processing effects and uses the Sobel operator along with other algorithms, such as Gaussian blur. Let's dive into it.