Inspiration

I grew up on monster-taming games like Pokémon: exploring tall grass, finding a rare creature, and building a team that felt like mine. But when I looked for that experience on mobile, and especially on Reddit, there was almost nothing. Reddit already has what those games always tried to fake: a real community. So I wanted to build a creature collector where the subreddit itself is part of the world, with daily challenges, rare sightings and Community Hunts where everyone fights a legendary together.

What it does

Orivale is a pixel-art creature-collecting RPG that runs inside a Reddit post. You make your own tamer, pick a starter Ori, explore towns and routes, and bind 100+ Ori. Each one has hidden Potential and a Temperament, and they ascend in different ways: by level, time of day, weather, bond or trade. You earn the marks of 8 Wardens, climb a weekly Tower, trade with other players and team up with your subreddit in Community Hunts.

How I built it

  • Reddit Devvit for hosting, posts, scheduling and payments, with a Hono + tRPC server and Redis for all game state.
  • React + Tailwind for menus and the Camp, with Phaser 3 for the overworld and battles.
  • A deterministic battle engine in pure TypeScript with a seeded RNG, so the server is authoritative and the client just animates the event log.
  • Battles use a shared energy pool instead of per-move limits:

$$E_{t+1} = \min(E_t + 2,\ 10), \quad E_0 = 3$$

so every turn is a choice between a cheap quick move now or saving up for a heavy one.

  • An AI-vs-AI simulator ran thousands of battles to flag any Ori that won more than 60% of the time, which guided balancing.
  • I drew the art myself and converted it to clean pixel art with my own tool.

Challenges

  • Fitting an RPG into a feed post. Reddit doesn't allow scrolling inside inline posts, so every menu and the new-player setup had to move into a full-screen view, while the post itself stays one clean Camp screen.
  • Mobile controls. Held arrows stopped when a second finger lifted, and dialogue closed itself when the A button sat under the text box. Fixing touch input took real-device testing.
  • Fair multiplayer. Trades use escrow with Redis transactions, and a 200-trade stress test proved nothing could be duplicated or lost.
  • Balancing 100 creatures without making any one of them mandatory.

What I learned

How to design for a platform's limits instead of against them, how much a deterministic engine simplifies multiplayer, and that small touch-input details can make or break a mobile game.

What's next

New regions with about 100 more Ori each, more weekly Tower twists, seasonal events, and cosmetics. Nothing paid will ever affect stats or odds.

Built With

Share this project:

Updates

Submission history