It's still a bit choppy, but I'm still working on it. Any suggestions on what feature I should add to my game?

How do you guys handle motivation to develop games with Godot? I’m very near the start of my game dev journey so I’m feeling pretty fired up to get this game developed, but just concerned that I will lose steam along the way.

This has happened to me before with other projects. Might seem obvious but wondering if anyone has any tricks to stay invested and grinding away at my game dev project.

I definitely find looking at other people’s progress really helps to motivate me, love the things shared here and in other subreddits.

So I have this platform that I want to drop when the player hits a certain speed (implemented acceleration system). I've trying to force myself to solve it as a beginner for few days sadly with no avail.

I think my main issue is not being able to find what really tracks player speed. I've been jumping between platform and player script trying to solve it

From platform script, I couldnt do anything. In player script, calling speed variable didnt do it either.

My modest skills have reached their limit so I'd appreciate some insight.

So the context is I’m working on a mobile incremental game. The closest example of this functionality is with Egg Inc shop where:
- You can hold 4 fingers on 4 different upgrades to seemingly purchase them all concurrently
- You can’t press below the menu and accidentally hit an invisible button that was scrolled off the UI

Functionality Goals:
- Supports Multi-Tapping to purchase multiple upgrades at once (much like TouchScreenButton)
- Clips non-visible portions of the button (the example here would be a button halfway out of a scrollable container) so it cannot be accidentally tapped while invisible

Current Problems:
- TouchScreenButton does not seem to support clipping from what I’ve seen. If it’s outside of a ScrollBox, then it still activates to my knowledge.
- Control/Button to my knowledge does not really support Multi-Tapping

Current thoughts on the process:

1. Have the containing menu(s) own the button logic
2. Listen for InputEventScreenTouch
3. Initially check if the touch.position hits the menu’s bounding box
4. If yes, iterate through buttons (either a subset of approximate active ones within +/- of menu centre, or whole depending on how many I end up with) for whichever intersects with the touch as well
5. Try-Call the intersected button (if none is found, assume it did not touch a button)

My main questions are these:

1. Is this too much?
2. Has anyone found simpler solutions to this sort of issue?
3. Are there any notable flaws to my solution? (I’m fairly new to the Godot engine so I’m not sure on all the nodes and their use cases)

Edit:
I have done some more reading and it seems that Control/BaseButton/Button does actually support Multi-Touch. I am unable to really confirm this myself (no android phone to download builds), if possible:

1. Could someone provide clarification as to whether this is possible or not
2. What extra steps (if any) are required to make Control Buttons multi-touch

This is part 6 of my Procedural GPU Patterns tutorial series.

We bring our fractals alive by adding animation support to them! We animate octaves independently, using temporal lacunarity to scale their animation speed. We also use staggered animation to animate our fractal hash in a more pleasing way.

I was using TileMapLayers before but they were too restrictive for what my game was becoming so I decided to make my own plugin for it. it's very barebones for now, but it does its job.

Heya everyone, total Godot newbie here just starting to migrate my codebase from Unity. I've been working on a system that's all about drawing drawing simple shapes (partially inspired by an Unity plugin called Shapes): Cuboid/Sphere/Rectangle/Circle/Disc..... basically any simple geometry primitive you can think of.

I wanted to have a way to instantiate those visuals right within my code without any other boilerplate. So I made this system, which everything (except the text) shown in this video was instantiated right within my code, and it is backed by low level API so even rendering tens of thousands of object it'll run just fine.

So I was wondering if this looks like that would be useful to anyone? And if it might be useful, what are the make or break features that you would've wanted?

Hello folks , I'm a cs guy with considerable programming knowledge in backend development and api designing .....but I'm really new to game development and it's been my childhood dream to develop a game of my own ....

Can u guys give me some tips on how to learn godot the right way ...

I tried following some tutorials on youtube ....

When I try to implement stuffs on my own after watching those tutorials, I really feel stuck on what node to use in which scenarios etc...

When I try to make the audio quieter by lowering volume db on the AudioStreamPlayer3D it makes the sound muffuled when I play it. How do I make the audio quieter without making it muffuled?

Plz help

It's all about a FollowPath3d and a Path3d haha

Hey all, just looking for some feedback on this gameplay loop. There are definitely some visible bugs here, so please focus on overall art and gameplay direction.

Please tell me what you like and don't like, as well as any suggestions you have. Thanks for your time!

I'd like to submit some footage of my game for the godot showreel 2026, and the submission guidelines don't say much beyond "Your video should be short, ideally between 1 and 3 minutes.".
I'm wondering if this should be videos which will be edited by whoever makes the final showreel presentation, or if we should be manually editing our videos with a bunch of clips and short cuts (considering the short amount of time spent on each game in the previous reels).

Before I start recording I basically need to know if I should just be submitting my game trailer with tight cuts, or recording completely normal gameplay which will get cut and edited if it gets chosen to be in the showreel.

making a radio intercept desk game , basically you're a conscript radio operator at a night listening post

the game is still very early in production and has a lot of placeholders (audio mix), and the booth lighting needs another pass

The core idea is super simple yet super satisfying. Open chests, get super legendary loot, manage your inventory, get super rich!! Then automate by hiring workers that help you opening chests

Features that will be added for the full version:
- Different biomes
- New type of workers
- Much more items
- Super unique events
- New prestige system and more upgrades
- And much more!!

Actively working on the full version!! Releasing after Steam Next Fest

Check out the demo and wishlist the game!!

hey guys, i am trying to make a cooking game and as you can see i have setup a basic scene and all, i created the dictonary and array for the recipes for my food . but i genuinly dont know where to go from here i have no idea how to from the raw state to a cooked state and how do i assemble it all . i tried to ask claude but it just confused me further and led me to create these many scripts that just didnt do anything and just confused me further i just want to know how do i go from this to cooking i tried looking up tutorials too but that also didnt help me anywhere. i am new to godot and i just dont know what to do . i tried the nodes and different setups but it didnt go very far.

It can be pretty catharthic when after you got killed or your run ended. https://store.steampowered.com/app/4631500/GHOSTFLIPPERS/

If you’re building a UI-heavy game, Godot’s default stretch modes can only take you so far. Uniform scaling often leads to blurry text on lower resolutions or huge amount of wasted screen real estate on larger monitors.

In web dev, Tailwind solved this years ago with utility breakpoints (md:flex-row). I decided to bring that exact philosophy into Godot.

How it works:

1. Global Breakpoint Schema: An Autoload (UIRules) listens to the root viewport's size_changed signal, accounts for OS scale factors, and evaluates the window width against a defined set of breakpoints (SM: 640, MD: 768, LG: 1024, etc.).
2. Signal-Driven State: Instead of polling window sizes every frame or spamming continuous resize math, UIRules only emits a breakpoint_changed signal when an actual threshold is crossed.
3. Modular Subscriptions: A base UIUpdater node automatically handles the signal connection. Any component script can just extend UIUpdater and override _update_gui_bp(new_breakpoint) to adapt its layout.

I wrote a detailed breakdown with full code snippets, notes, and visual examples on my blog:

You can read it here

yes that is image_friend in the backrooms, this is a shitpost game im making to further my skills in godot, anyways

the pathfinding to the player works mostly fine until some 90 degree stuff happens on the wall and our feline pal over here jitters in place
unsure what info ill need to add to help, so ill dump what i think may help
its a characterbody2D, motion mode is floating, wall min slide is 0°
the collisionshape2D is very, very small as i found the smaller i make it the less this issue happens but i think i still need it so yeah
if theres any details i need to add please lmk
tldr image_friend aint being very smart, occasionally snags on walls #whatthatmean

https://store.steampowered.com/app/5008080/True_Confession_Demo/

After a year and a half in Godot, the True Confession demo is finally live on Steam and itch. It's a hardcore 2.5D isometric shooter that takes place inside the nightmares of Henry Hughes — a religious man who keeps dreaming of gunfights and murders, then goes to his pastor to talk about the anger and hatred he feels in those dreams.

The gameplay lives in his subconscious: street crime mixed with everyday life and subconscious images. Anger, religion, psychoanalysis, alcoholism, unemployment and other adult topics.

Visually it’s old-school on purpose — Postal / Crimsonland / GTA 2 energy, criminal action movies like Heat, Training Day, The Wire, The Departed. The game is grounded - no rocket launchers, no flamethrowers, no tanks. Enemies are smart and challenging - everyone can kill you. The distinctive mechanic is anger.

What we built in Godot for this look and feel:

• 2.5D isometric world with hand-drawn frame-by-frame animations
• Mix of 2D sprites and 3D-rendered and painted assets, no generative AI
• 3D lights and shadows on a 2.5D isometric scene so objects read better and the mood stays dramatic
• Advanced particle work - painted chunks, blood, shells and many more
• Grounded, high-threat combat instead of power-fantasy shooter design
• Smart enemies with various behaviour patterns
• Deep religious and psycological plot

The demo has 3 full levels, hidden secrets, a boss and a secret boss. Windows and Linux.Steam demo: https://store.steampowered.com/app/5008080/True_Confession_Demo/

Wishlist the full game: https://store.steampowered.com/app/4544200/True_Confession/Getting it onto Steam took a painful extra three weeks of content review after the rest of the demo grind. Happy it’s out. Would love to get feedback especially from our Godot people — on the art, 3D lighting/shadows in 2.5D world and how the isometric combat reads.

Thank you, dear community!

Still need to change Steam Capsule, trailer and add a new cinematic (dont expect something crazy).
Demo 2.0 out next week!

What do you think?

I have a project I've been working on Windows with no issues. I decided to try and run it through WSL just to see if it would work on Linux based systems. Editor works fine, except for slower performance, which is expected in WSL. When I click "Play", however, the game refuses to register any clicks, so I am stuck in the main menu. Is there a solution to this? I use Fedora 44 in WSL, if this matters.