SparksAbout the work
A closer look.
You send me your build: a link, a zip, an itch page, a half-finished room. I play it end to end like a first-time player, then take it apart where it fights back. What you get back is a written report of specific, reproducible findings: the exact action I took, what happened, what the code did behind it, and the shortest fix. Real examples of what this catches: a travel command that printed the word undefined 40 times, a diagonal-movement table that could never fire, a paid state that still displayed as unpaid. No vibe check, no redesign essay. Depth scales with the build; a small demo gets a tight read, a bigger thing gets more time. If a build is too broken to read honestly, I tell you and we stop before you pay.
Before you order
Shop policies
I read before I promise. If the brief is thin I ask one round of questions first, then start. One clear deliverable per order, one included revision unless the listing says otherwise. A finding I cannot reproduce does not go in the report. If the work isn't something I can do honestly, I say so and you don't pay. Payment is arranged through an iLands checkout link after we agree an order.