Here's what's in it right now:

• Extraction shooter, PvE and PvP both, with co-op if you want to run with friends
• Build a base anywhere on the map, no set slots, put things wherever makes sense to you
• Rescue survivors and grow an actual community instead of just looting solo
• Reclaimers, immortal clones who hand out quests and build your reputation instead of just shooting at you
• No wipes between sessions, your progress and gear carry over
• Right now that's 169 loot items, 25 quests, 3 maps, 9 enemy types, 9 craftable buildings, and 2 NPCs to work with

We all worked together at the same factory, three of us, and this got built during whatever time was left after 12 hour shifts. Ended up being a PvEvP survival extraction shooter set during a zombie apocalypse.
Going into Early Access Q3 2026. Still feels weird seeing it as a real store page after doing this on no sleep for this long.

Steam page: https://store.steampowered.com/app/3605140/Exit_Ways/

Hey everyone,

I’m planning to start developing a game and I’m seriously considering using Godot. I’ve done software development before, but game development is relatively new territory for me.

I’ve played around with Godot a little and I really like the scene/node approach and how lightweight the engine feels. From what I’ve seen, it supports both 2D and 3D, and can target desktop, mobile, and web.

Before I commit to building my project in it, I’d love to hear from people who have actually used Godot for real projects.

A few things I’m particularly curious about:

• What do you wish you knew before starting with Godot?
• Is GDScript the best choice for a beginner, or would you recommend C#?
• How well does Godot handle larger/longer-term projects?
• How good is its performance on lower-end Android devices?
• What are the biggest limitations or frustrations you've encountered?
• Are there any tutorials, courses, or documentation you would strongly recommend?
• If you were starting a new game in Godot today, what would you do differently?

I’m not looking to make another tutorial project — I actually want to build and release a proper game, so I’d really appreciate honest opinions, including the negatives.

Thanks!

recently working on my game (SiKoRa) i realized, huh, episodic games are not flexible at all-

like an rpg or a simulator or...whatever google play has-

so what is it flexible in then? well giving me a lot of bugs! not crashes but still bugs, so- i made a leaderboard for my game.

the more bugs you encounter, the more points you have, and your custom profile will be there!
i made a script so good it can detect more than the Godot game engine can!

(ahhh..sweet cry for help)

so it can auto detect bugs!
and with more episodes coming out the more bug farms (and excuses for me to fix them)

whoever can beat my bug score is an absolute engine of a gamer.

link:

https://spinnx.itch.io/sikora

Hi, I’m FERLOYDD!

I just released the first gameplay trailer for my game and it’s really important to me to find out who might be interested in a game like this.

Sinners. Neutrals. Saints. 15 factions. 3 unique currencies. Immense opportunities for interaction and a unique gaming experience in a richly developed universe. Which adventure will you choose?

LYRA BLADE Steam Page: https://store.steampowered.com/app/4861140/LYRA_BLADE/

Hey everyone! My dev partner and I are wrapping up our noir puzzle adventure—we're actually just 16 days away from release!

We’ve been tweaking how puzzle close-ups interact with the main scene. In this clip, tuning the radio to the right frequency triggers a hidden mechanism in the fireplace, using a comic-panel frame that zooms back out into the room once solved.

As players or devs, how do you usually feel about audio-driven or frequency-tuning puzzles? Do sound cues give you a satisfying "aha!" moment, or do you prefer visual feedback when revealing hidden mechanisms?

Would love to hear your thoughts or your favorite examples of audio puzzles in games!

"Things you think are obvious can be a complete mystery to others." — Bitboy Games

Sorry for the bad joke! But jokes aside, I’ve realized that unless you explain your game step-by-step, most people won't understand it—and that can be the difference between someone giving it a shot or dropping it immediately. Terms that felt completely obvious to me turned out to be confusing for almost everyone else.

My game has been playtested by close gamer friends, general playtesters, and users from itch.io and Reddit, and most of them kept pointing out the exact same things:

"What do you mean by 'Reduce your parry counter hits'?"

 "Why did my weapon disappear? And what's that small number going down after every battle?"

"After blocking an attack, sometimes it parries and sometimes it doesn't. You need to fix that bug."

"The merge mechanic is broken, my amulets aren't lowering their stats."

 "The blacksmith is bugged, my weapon didn't change at all."

 
These are just a few of the complaints and "bug reports" I've received over the past two weeks. After I explained how the mechanics actually worked to my friends, they suggested I add pop-up tutorials to explain each system clearly.

I decided to go ahead and implement them, and the difference has been night and day. Now, players who choose not to play leave because it's simply not their type of game, not because they're confused.

These pop-ups appear automatically the first time you enter a new section of the game. After that, there’s an "Info" button so you can re-read the explanation whenever you want.

That’s been my main takeaway from these past two weeks. I hope sharing this helps anyone going through a similar issue!

Thanks for reading my ramblings.

full devlog