I'm Pal Leksan. I left finance to build games full-time. Today, I run AnimaByte, a one-person studio exploring what makes a game worth coming back to.
01 Selected work
Two projects from my studio. Different scales, different stages, the same curiosity about how systems become play.
Playable prototype
01 / Priority project
Small squad. Big responsibility.
Compact tactical action with short missions and unified squad control. Built to get players into the action quickly, with the character of the games I grew up with.
The browser prototype is playable. I'm now stabilizing the core missions and preparing structured tests with tactical and retro-action players.
Play the prototype
Technical exploration
02 / Research & experiments
A small creature.
An enormous system.
An exploration of ant movement, colony behavior, and scale. The current build is a technical simulation, with the possibility of a game still to be tested.
It remains a potential next project while Operation Red Hour takes priority.
Explore the simulation02 Background
I changed what I build.
I kept how I take responsibility.
Before games, I spent eight years in finance. That work taught me to understand people, earn trust, and take responsibility for the result.
During five years selling mortgage services, I spent three on full commission. More than 90% of my clients came through channels I built myself: my network, website, blog, YouTube, Facebook groups, and partners.
It was a career that worked. I chose to leave because I wanted to spend my working life making games.
Today I handle the development, testing, communication, and decisions at AnimaByte. The studio is small, and I intend to keep its projects focused enough to finish.
Working in finance
Clients from channels I built
03 Practice
I like building. I also know how easily a promising project can become too large. This is how I keep the work grounded.
I work with TypeScript, Phaser, Unity, and AI-supported tools. Prototyping, debugging, playtesting, and product decisions all belong to the same job.
I'm happy to do the work around the work, too. Research, outreach, documentation, or repetitive fixes matter when they help a project move forward.
Make the smallest build that lets someone experience the idea.
Test with people who already enjoy the kind of game I'm making.
Look at what players do, hear what they say, and fix the most important problem.
Continue, reshape, reduce, or stop. Set limits before expanding.
Expand a tested idea into a finished game, then learn from its release.
04 Beyond the work
I'm a husband, a father of two boys, and someone who has been curious about technology since childhood. Family gives me a reason to build something that lasts.
I'm calm, optimistic, and comfortable with direct feedback. I enjoy learning, helping people, and seeing a difficult thing get a little better. Progress makes me happy.
I've made YouTube content before, and I'm bringing that experience into devlogs and conversations with other game developers.
05 On my desk
What I'm concentrating on at the studio.
Stabilizing Operation Red Hour's core missions and recruiting adult PC players for a focused external playtest.
Interested in testing?A Polish interview series about what gets built, what breaks, and what it takes to finish. It's in preparation; my earlier videos are on the channel.
Visit my YouTube channel06 Say hello
Feedback on a build, a playtest, a developer conversation, or a project worth discussing. I'd like to hear from you.
palll@pm.me