itch.io

Hi! I’m looking for a few Windows players to test Dots of Terror, a free first-person atmospheric horror alpha made in Godot.

You arrive to film an abandoned house, but the winter street and its residents lead into a living labyrinth. The main mechanic is connecting numbered dots on strange canvases while surviving encounters that interfere with the camera and the maze.

The current build is a substantial vertical-slice alpha rather than a finished game. It has been checked on macOS, but I especially need independent Windows testing. I worked on the game and its test setup with an AI coding assistant, then reviewed the changes, builds, and visual captures myself.

I mainly need to know:

• Does the Windows build launch and run correctly?

• Can you finish the current demo?

• Where did you feel scared, bored, confused, or stuck?

• Did any camera, chase, canvas, dialogue, or audio sequence break?

Playtime is roughly 20–40 minutes. Easy has a shorter four-canvas route; Hardcore has the full seven-canvas route and additional encounters. A screen recording is especially useful, but a short written report is completely fine.

Game page: https://ndnceb.itch.io/dots-of-terror

If you test it, please mention your Windows version, difficulty, and what happened immediately before any bug. Content warning: sudden scares, loud sounds, flashing effects, and body horror.

Thank you — honest criticism is more useful to me than polite praise.

Hi, my name is Ivan. I am building a focused debugging service for Godot 3.x and 4.x projects, and I am looking for three developers who have one specific reproducible bug they have not been able to solve. This first pass is completely free because I want to validate the workflow on real outside projects.

I have already completed ten behaviorally verified fixes across different public Godot projects. Nine solutions have been submitted publicly, and three fixes have now been merged by project maintainers. The work includes runtime state bugs, editor freezes, input and camera conflicts, resource UID problems, SVG parsing, UI focus, object lifetime, and production logic.

Public evidence:

• Merged — stale world tiles texture UID fix and maintainer response: https://github.com/Daniele-Cangi/civic-nightmare/pull/113

• Merged — timer pause state reset fix: https://github.com/Mad-Cookies-Studio/mad-productivity/pull/42

• Merged — production lifecycle and factory-loss fix, 11,528/11,528 checks: https://github.com/ReSun-Developers/ReSun/pull/489

• Under review — editor freeze fix: https://github.com/DigitallyTailored/Godot-Open-World-Database/pull/23

• Under review — object lifetime fix, 919/919 tests: https://github.com/weavly-lang/weavly-godot-addon/pull/280

How the free pass works:

1. We agree on one reproducible bug.

2. You provide the exact Godot version, expected and actual behavior, numbered reproduction steps, relevant logs, and a sanitized project copy or repository.

3. I preserve the original and work only in a separate isolated copy.

4. I reproduce the bug before changing code.

5. You receive a reviewable patch or changed files, a plain-language explanation, verification evidence, and transfer and rollback instructions.

I use an AI coding assistant during investigation and implementation, and I personally review the project context, changes, and test results. A fix is not promised until I can reproduce the problem.

Please do not send passwords, API keys, signing certificates, personal data, paid assets you cannot share, or unrelated private files. You must own the project or have permission to share and modify it. If the full project cannot be shared safely, a minimal reproduction is better.

If you are interested, reply with a short description of the bug, your exact Godot version and operating system, and whether it happens consistently. Please do not upload the project publicly before we confirm the scope.