For indie developers

PC game
playtesting.

Where does your first mission lose a player? I’ll play your Windows build from a fresh save and show you the moment a control, objective, or line of dialogue trips me up.

Ask about your build
Slag Run’s overhead map with squads and connected capture points

From my own game · Slag Run

South Relay capture delay

In the strategy tutorial, friendly troops reached South Relay and the defenders were gone. The point still took long enough to change hands that it looked stalled.

What I’d check  Time the gap between the last defender falling and capture progress appearing. That distinguishes a capture delay from missing feedback.

What I can test

The opening hour
One Windows build, one fresh save, and one question you want answered. You get a prioritized report on the controls, teaching, and objectives, with screenshots or short clips where recording is permitted.
Bugs across builds
I document the build, setup, steps, expected result, and what happened. On a follow-up build I can replay the same sequence and report whether the issue still occurs.
Brazilian Portuguese QA
I check text in the running game. That catches prompts that name the wrong action, terms that change between a menu and a mission, and translations that no longer fit the HUD.

Work with Fabio Torlai

Tell me about
your build.

I’m the developer of Slag Run. I test on Windows and deliver reports in English or Brazilian Portuguese.

Send your game title, milestone date, and the question you want the session to answer. I’ll reply with a scope, price, and delivery window.

Email Fabio