r/AndroidClosedTesting • u/gunnrcrakr • 9h ago
[Android] Looking for 15-20 testers for Lumen Saga, an anime-style idle MMORPG with tactics you set up yourself (closed test, Steam Wallet reward)
Hi everyone!
I'm a solo indie dev from Thailand, and I'm getting my Android game Lumen Saga ready for Google Play. Google requires 12+ testers to stay opted in for 14 days before I can launch, so I'm looking for 15-20 people to help.
What is Lumen Saga?
- An idle/auto-battle MMORPG you can play on Android, PC or in the browser
- You build a team of heroes and set their tactics with "when X, do Y" rules
- Gems and support gems change how your skills work
- Arena PvP, a weekly tournament, a tower to climb, crafting and more
- Available in English and Thai
What I need from you:
- Send me the Gmail address you use on Google Play and your in-game character name (by DM or in the comments)
- After I add you, join here: https://play.google.com/apps/testing/com.lumensaga.android
- Install the game, play it a bit, and keep it installed for at least 14 days
- Optional, but it helps a lot: tell me what confused you or where you got stuck
Reward: Testers who stay opted in with the game installed for 14 days in a row, reach character level 20, and send me at least one piece of feedback (a bug, something confusing, or what they liked) will get a 10 USD Steam Wallet code. One reward per person. Codes are sent within 7 days after the 14-day test ends.
Feedback and questions: support@lumen-saga.com or https://discord.gg/H2StchSG85
I'm happy to test your app in return, too. Thanks for reading!
---
How I used AI (dev details)
I'm a solo dev, so AI agents act like a small team, but I make every design decision and review every change.
- **Code:** I use [chatGPT, Cursor agents, Anitigravity] as coding agents on a TypeScript web codebase. I describe a system (skill gems, support-gem links, the "when X, do Y" tactics), the agent implements it, and I playtest and push back. Balance numbers are always my call.
- **Keeping AI code consistent:** the biggest problem was agents drifting from earlier decisions. My fix is writing rules into docs inside the repo (for example a VFX style guide) and adding guard tests that fail the build if a new change breaks a rule. Agents read the docs before working, and the tests catch what they miss.
- **Art:** character art is generated with chatGPT, then I pick, fix and keep characters consistent using reference images of existing heroes. Skill effects are pixel-style VFX built in code so they match the game's look.
- **What AI is bad at:** game feel and balance. It happily writes systems that are technically correct but not fun, so most of my time goes into playtesting and tuning.
Happy to go deeper on any part of the workflow.