Devlog · Entry 002 · Pulldown Paladin

Building a Hero Who Lives in Your Notification Shade

Idle design, tiny screens and honest numbers — by Vainsteel Studios

Pulldown Paladin started with a strange question: what if an idle RPG respected your time so much that you barely had to open it? The answer became a knight who fights while you live your life, and a loop built around short, satisfying check-ins instead of endless grinding.

Balancing an idle economy

Idle games live or die by their numbers. Too generous and progress feels meaningless; too stingy and players quit on day two. We tuned gold, gear and prestige curves by playing the game ourselves every day for weeks, cutting any upgrade that did not change how a session felt.

Designing for a thumb, not a mouse

Every core action reachable with one thumb in portrait mode.
Readable text across 30+ languages on the smallest phones.
Sessions that feel complete in under a minute.
No forced ads between the player and their progress.

From Play Store to App Store

After launching on Google Play, bringing Pulldown Paladin to iOS meant a new round of device testing, store reviews and polish. It is now live on both stores — and every review we read shapes the next update.

Devlog · Entry 001 · The Forge

The Reality of Handcrafting Stardust Harbor

A candid devlog on indie game development — by Vainsteel Studios

People imagine game development as a montage: a cool synthwave track, a few keystrokes, a finished game. The reality is quieter, slower, and far more stubborn. We are three makers in Turkey building small worlds one commit, one sprite, one bug report at a time. This is the first entry in a devlog series where we talk honestly about that process — what it actually costs to handcraft a game like Stardust Harbor.

Why we call it a forge

A forge is not glamorous. It is heat, repetition, and a lot of scrap. Every mechanic in Stardust Harbor was hammered flat, folded, and reheated dozens of times before it felt right. Our "forge" is not a marketing word — it is a discipline: ship rough, test daily, cut what does not spark, and never mistake motion for progress.

What atmospheric world-building actually takes

Atmosphere is the first thing players feel and the last thing you can fake. For Stardust Harbor we spent weeks on things a player might never consciously notice: the exact hue of the nebula at dusk, the weight of a ship idling in dock, the pause before a merchant speaks. World-building at this scale is not concept art on a moodboard — it is hundreds of tiny decisions that only stop being invisible when one of them is wrong.

The parts nobody films

Rebuilding the save system three times because the fourth idea was the right one.
Localizing to 30+ languages and re-testing every UI string that suddenly overflows.
Play Store review cycles that turn a 2-day feature into a 2-week ship.
Cutting a mechanic you loved because playtesters silently skipped it.
Answering support emails at midnight from a player halfway across the world.

What comes next in this series

Future entries will cover the build pipeline for Pulldown Paladin's notification-shade hero, how we balance an idle economy without spreadsheets eating our week, and the design philosophy behind our upcoming PC project. No hype, no roadmaps we cannot keep — just the work.

If you want to follow the forge in real time, our YouTube channel is the shortest path in.

Follow on YouTube Back to Studio