Day 1 of My First Game Ever. I Asked r/Unity2D What I Was Getting Wrong.
Build in Public — Devlog #01. I'm building my first game ever for Shipaton 2026. I asked the internet what I was getting wrong before I wrote a line of code, and the answers changed the plan on day one. I have never opened a game engine That's the honest starting line. I'm an Flutter developer. I know Backend/ bit of Kotlin, I know Gradle, I know the shape of a mobile app. Last week I knew…
On the first day of his first game development journey, a Flutter developer named Karthick turned to the online community for guidance before writing a single line of code. After posting his query on X and the r/Unity2D forum, he discovered that his initial vision of a six-player online arena game needed to be simplified.
The result of his research was a pared-down concept called "One Bullet Arena," where up to six players control a single bullet each, with the goal of firing, retrieving missed shots, and avoiding collisions. Karthick chose Unity 6 with 2D Universal Render Pipeline (URP) for its Unity SDK compatibility and Unity's RevenueCat integration for the hackathon. The 2D URP was selected to ensure lightweight graphics on mid-range Android devices.
His initial goal was to achieve four key milestones: 1) create a 2D level-based single-player experience with sticky bullets and hand-designed rooms, 2) implement local same-WiFi multiplayer for real opponents without hosting or NAT traversal, and 3) develop an online version of the game, which would only be pursued if the previous two phases were successful. Phase 1 was intended for the Shipaton hackathon submission, while subsequent phases would focus on refining the gameplay and adding content.
Karthick positioned game feel as his weakest point, acknowledging that he had no prior experience in game development and would need to master acceleration curves, screen shake, hit delays, and other essential mechanics for an enjoyable gaming experience. He vowed to document every step of the development process, including mistakes, to share the authenticity of his Build in Public approach.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
